<div dir="ltr">Two comments on this:<br><ol><li>It is possible that Android is looking for the DNS search path provided by DHCP that tells a client what suffixes to try. Looking at the git repository the XSCE DHCP server may not currently supply this.<br>
<br>I will look into this a bit when I get the chance. The fix if necessary would be trivial.<br><br></li><li><a href="https://github.com/XSCE/xsce/blob/master/vars/default_vars.yml">https://github.com/XSCE/xsce/blob/master/vars/default_vars.yml</a> seems to imply that the default domain suffix is ".local"<br>
<br>That is a definite potential bug. While ".local" is reserved for local use, multicast DNS clients effectively have taken over this domain to the point that older networks which have .local DNS entries have run into a lot of problems.<br>
<br>A network I used to use was like this so I've seen random failures to resolve things firsthand.<br><br>See <a href="http://en.wikipedia.org/wiki/.local">http://en.wikipedia.org/wiki/.local</a> for more information, although I do not know of an alternative good practice besides leasing a public DNS domain name that you know will never be used.</li>
</ol><p><br></p></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 9, 2013 at 6:45 PM, Anna <span dir="ltr"><<a href="mailto:aschoolf@gmail.com" target="_blank">aschoolf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>If I'm having trouble with connectivity on a client, I'll try to go to <a href="http://172.18.96.1" target="_blank">http://172.18.96.1</a> in the Browse Activity and see if it resolves. It usually does, even if <a href="http://schoolserver" target="_blank">http://schoolserver</a> doesn't because something's borked up. Here's the ifconfig of an ethernet wifi dongle connected to an AP:<br>
<br>eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br> inet 172.18.96.1 netmask 255.255.224.0 broadcast 172.18.127.255<br> inet6 fe80::21c:49ff:fe01:427 prefixlen 64 scopeid 0x20<link><br>
ether 00:1c:49:01:04:27 txqueuelen 1000 (Ethernet)<br> RX packets 4 bytes 649 (649.0 B)<br> RX errors 0 dropped 0 overruns 0 frame 0<br> TX packets 0 bytes 6549 (6.3 KiB)<br> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br>
<br></div>I booted up an XSCE I had been testing with recently and an XO-1 client to test with. Yep, <a href="http://schoolserver" target="_blank">http://schoolserver</a> and <a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a> resolved from the client. <a href="http://172.18.96.1" target="_blank">http://172.18.96.1</a> goes to the portal page, too, of course.<br>
<br></div></div><div>Then I physically unplugged my "regular" AP so the XSCE wouldn't have any internet. And <a href="http://schoolserver" target="_blank">http://schoolserver</a> and <a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a> resolved on the XO-1 client. Wanted to just make sure that was the case.<br>
<br></div><div>But what about an Android tablet? I barged into Tyler's office and pried the Kindle Fire out of his hands (literally, he was playing Angry Birds), connected the Fire's wifi to the XSCE, and it got 172.18.100.208. Opened the Fire's browser and tried to go to <a href="http://schoolserver" target="_blank">http://schoolserver</a>. Hmm, page not found. Then tried <a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a>. And that worked! It also accesses the Moodle login page at <a href="http://schoolserver.local/moodle/login/index.php" target="_blank">http://schoolserver.local/moodle/login/index.php</a>.<br>
<br></div><div>So there appears to be something with the Android browser that doesn't want to resolve <a href="http://schoolserver" target="_blank">http://schoolserver</a>. So as Curt suggested, try it with <a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a> and if that doesn't work, <a href="http://172.18.96.1" target="_blank">http://172.18.96.1</a>.<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></div><span class="HOEnZb"><font color="#888888"><div>Anna<br></div><div><div><div><br></div></div></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Nov 9, 2013 at 4:17 PM, Seth Woodworth <span dir="ltr"><<a href="mailto:seth@sethish.com" target="_blank">seth@sethish.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I am pretty sure that <span style="font-family:arial,sans-serif;font-size:12.800000190734863px">172.18.96.0 is the IP address assigned to the network, and not to any particular computer. </span><div>
<span style="font-family:arial,sans-serif;font-size:12.800000190734863px">If the network mask is 255.255.255.0 then the .0 address will never point to a computer or service.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">If the network mask is anything else, then I don't know what I'm talking about.</span></div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 9, 2013 at 3:39 PM, Curt Thompson <span dir="ltr"><<a href="mailto:curtathompson@gmail.com" target="_blank">curtathompson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Just making sure.. have you also tried
172.18.96.1 and/or <a href="http://schoolserver.local" target="_blank">http://schoolserver.local</a> ?<div><div><br>
<br>
On 11/9/2013 12:31 AM, Adam Holt wrote:<br>
</div></div></div><div><div>
<blockquote type="cite">
<div dir="ltr">From: <b class="gmail_sendername">Nathan C. Riddle</b>
<span dir="ltr"><<a href="mailto:nathanr333@charter.net" target="_blank">nathanr333@charter.net</a>></span><br>
<div class="gmail_quote">Date: Sat, Nov 9, 2013 at 3:18 AM<br>
Subject: [support-gang] XO tablet can not connect to XSCE
server<br>
To: Gang <<a href="mailto:support-gang@laptop.org" target="_blank">support-gang@laptop.org</a>><br>
<br>
The XO tablet can not reach XSCE server. Unregistered XO
laptop does reach XSCE server (<a href="http://schoolserver" target="_blank">http://schoolserver</a>
or 172.18.96.0).<br>
The XO tablet WiFi connects and receives IP address
(172.18.100.240) from the schoolserver using its "browse" or
Chrome.<br>
Error message that applies suggest can not find DNS, i.e, can
not use local lookup. The XSCE is not connected to internet.<br>
<br>
This seems to be a restriction on the XO tablet, so this may
not be an appropriate question to ask here.<br>
<br>
Was hoping that XO tablet(s) could work in MOODLE with
created login account (which works with PC laptop and
presumedly with ipad).<br>
<br>
Nathan Riddle<br>
_______________________________________________<br>
support-gang mailing list<br>
<a href="mailto:support-gang@lists.laptop.org" target="_blank">support-gang@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/support-gang" target="_blank">http://lists.laptop.org/listinfo/support-gang</a><br>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr">Unsung Heroes of OLPC, interviewed live @ <a href="http://unleashkids.org" target="_blank">http://unleashkids.org</a> !</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>