Re: [Server-devel] [XSCE] Fwd: [support-gang] XO tablet can not connect to XSCE server

2013-11-10 Thread Tim Moody


-Original Message- 
From: Braddock

Sent: Sunday, November 10, 2013 12:23 AM
To: xsce-de...@googlegroups.com ; XS Devel
Subject: Re: [XSCE] Fwd: [support-gang] XO tablet can not connect to XSCE 
server


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/09/2013 04:53 PM, Samuel Greenfeld wrote:

2. https://github.com/XSCE/xsce/blob/master/vars/default_vars.yml
seems to imply that the default domain suffix is .local

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.


Did some reading and you have made a believer out of me.


Use of schoolserver.lan would avoid these problems.


.lan is a candidate, also .internal.  I have seen .localdomain.

Can anyone point to a 'best practices'? 


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [XSCE] Fwd: [support-gang] XO tablet can not connect to XSCE server

2013-11-09 Thread Samuel Greenfeld
Two comments on this:

   1. 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.

   I will look into this a bit when I get the chance.  The fix if necessary
   would be trivial.

   2. https://github.com/XSCE/xsce/blob/master/vars/default_vars.yml seems
   to imply that the default domain suffix is .local

   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.

   A network I used to use was like this so I've seen random failures to
   resolve things firsthand.

   See http://en.wikipedia.org/wiki/.local 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.




On Sat, Nov 9, 2013 at 6:45 PM, Anna ascho...@gmail.com wrote:

 If I'm having trouble with connectivity on a client, I'll try to go to
 http://172.18.96.1 in the Browse Activity and see if it resolves.  It
 usually does, even if http://schoolserver doesn't because something's
 borked up.  Here's the ifconfig of an ethernet wifi dongle connected to an
 AP:

 eth1: flags=4163UP,BROADCAST,RUNNING,MULTICAST  mtu 1500
 inet 172.18.96.1  netmask 255.255.224.0  broadcast 172.18.127.255
 inet6 fe80::21c:49ff:fe01:427  prefixlen 64  scopeid 0x20link
 ether 00:1c:49:01:04:27  txqueuelen 1000  (Ethernet)
 RX packets 4  bytes 649 (649.0 B)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 0  bytes 6549 (6.3 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 I booted up an XSCE I had been testing with recently and an XO-1 client to
 test with.  Yep, http://schoolserver and http://schoolserver.localresolved 
 from the client.
 http://172.18.96.1 goes to the portal page, too, of course.

 Then I physically unplugged my regular AP so the XSCE wouldn't have any
 internet.  And http://schoolserver and http://schoolserver.local resolved
 on the XO-1 client.  Wanted to just make sure that was the case.

 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 http://schoolserver.  Hmm, page not
 found.  Then tried http://schoolserver.local.  And that worked!  It also
 accesses the Moodle login page at
 http://schoolserver.local/moodle/login/index.php.

 So there appears to be something with the Android browser that doesn't
 want to resolve http://schoolserver.  So as Curt suggested, try it with
 http://schoolserver.local and if that doesn't work, http://172.18.96.1.

 Anna



 On Sat, Nov 9, 2013 at 4:17 PM, Seth Woodworth s...@sethish.com wrote:

 I am pretty sure that 172.18.96.0 is the IP address assigned to the
 network, and not to any particular computer.
 If the network mask is 255.255.255.0 then the .0 address will never point
 to a computer or service.

 If the network mask is anything else, then I don't know what I'm talking
 about.


 On Sat, Nov 9, 2013 at 3:39 PM, Curt Thompson curtathomp...@gmail.comwrote:

  Just making sure.. have you also tried 172.18.96.1 and/or
 http://schoolserver.local ?


 On 11/9/2013 12:31 AM, Adam Holt wrote:

 From: Nathan C. Riddle nathanr...@charter.net
 Date: Sat, Nov 9, 2013 at 3:18 AM
 Subject: [support-gang] XO tablet can not connect to XSCE server
 To: Gang support-g...@laptop.org

 The XO tablet can not reach XSCE server.  Unregistered XO laptop does
 reach XSCE server (http://schoolserver or 172.18.96.0).
 The XO tablet WiFi connects and receives IP address (172.18.100.240)
 from the schoolserver using its browse or Chrome.
 Error message that applies suggest can not find DNS, i.e, can not use
 local lookup.  The XSCE is not connected to internet.

 This seems to be a restriction on the XO tablet, so this may not be an
 appropriate question to ask here.

 Was hoping that  XO tablet(s) could work in MOODLE with created login
 account (which works with PC laptop and presumedly with ipad).

 Nathan Riddle
 ___
 support-gang mailing list
 support-g...@lists.laptop.org
 http://lists.laptop.org/listinfo/support-gang


 --
 Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org !





___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [XSCE] Fwd: [support-gang] XO tablet can not connect to XSCE server

2013-11-09 Thread Braddock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/09/2013 04:53 PM, Samuel Greenfeld wrote:
 2. https://github.com/XSCE/xsce/blob/master/vars/default_vars.yml
 seems to imply that the default domain suffix is .local
 
 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.
 
 A network I used to use was like this so I've seen random failures 
 to resolve things firsthand.

I've been trying to raise the red flag on this (mis)use of .local
since the XSCE sprint in May(?) when I experienced problems using mDNS
with School Server XSCE with both Linux laptops and Internet-in-a-Box
appliances.

Use of schoolserver.lan would avoid these problems.

Ubuntu and Debian disable (aka break) mDNS resolution on the client
when they encounter a misconfigured .local domain being used in the
DHCP response.  This happens if they obtain a DHCP lease from a
schoolserver.local.  If they did not deactivate mDNS resolution, then
schoolserver.local resolution would fail when mDNS couldn't resolve it.

I have a request into de...@laptop.org upstream to activate mDNS name
resolution on the OLPC OS to ease IIAB appliance deployments and any
other local resource discovery.

If/When they turn mDNS resolution on in OLPC OS, then XOs in a
schoolserver network will either fail to resolve the
schoolserver.local name, or mDNS will break for all other devices on
the network (ex, Internet-in-a-Box appliances).  I'm not sure which
will break under Fedora/OLPC OS, but something will give.

For more info see my thread on de...@laptop.org
http://lists.laptop.org/pipermail/devel/2013-July/037559.html
and ticket
http://lists.laptop.org/pipermail/bugs/2013-July/118727.html

See also
http://miketelahun.wordpress.com/2012/09/16/stop-using-local-as-the-top-level-domain-for-your-lan/

- -braddock
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSfxhYAAoJEHWLR/DQzlZu9/oIAMCMwaqCK4hCaOtUMRqczxbg
Nqor0gqIrwdZJjTnWb3k3sdzipSLLBV+FZ/L9d8EOPpm9QgDbTOvsGAF9Yc7jXNj
9Ml5Pb7Cg+KF2PgjaNTx6aZzNxerwN5zyDEZewV2UrwTatymflitlMnUzfxsobJa
0vbydrxvEMG9eLmL8xm5k5a9TLpiN5W/sIaUvVQlPVw+Q16rSJRpPAJV9mdJABH5
INrtuUXZ/qGrIcxIbYOSIQijFJ6/HpxRhigQk8g7KDernY5NC0QX8t+MVONK9zoX
3BbAZvMe0chibwUlSasJjGhkMhiw0FwUE9mlNIfG6m9d4stSZhV6XRaVgpjMxV0=
=TUwf
-END PGP SIGNATURE-
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel