[Server-devel] failed to register

Sameer Verma sverma at sfsu.edu
Mon Jun 4 20:48:01 EDT 2012 

On Mon, Jun 4, 2012 at 5:41 PM, John Watlington <wad at laptop.org> wrote:
>
> On Jun 4, 2012, at 8:35 PM, John Watlington wrote:
>
>> I suspect that your ISP is assigning 172.18.196.1 to the
>> XS, which is then confused as to where packets destined
>> for 172.18.xx.xx should be routed.
>> eth0 and the other interfaces on the XS should be in separate
>> subnets.
>
> BTW, if this is actually the problem I don't have a quick fix.
> This is why I chose the relatively unused 172.18.xx.xx unroutable
> addresses originally, instead of the more common 10.xx.xx.xx or
> 192.168.xx.xx private ranges for the internal network.
> Perhaps someone who has worked on the XS networking recently
> can help ?
>
> wad
>
>> On Jun 4, 2012, at 8:04 PM, Holt wrote:
>>
>>> On 6/4/2012 7:32 PM, John Watlington wrote:
>>>> On Jun 4, 2012, at 7:30 PM, John Watlington wrote:
>>>>
>>>>> Adam, something is wrong with those addresses.
>>>>> The 18.nn.nn.nn subnet is owned by MIT.   You shouldn't be
>>>>> using any of them.    Perhaps you meant 172.18.nn.nn ?
>>>
>>> Wad's exactly right -- I spent too many years at MIT and so typed 18.* without thinking.  The correct IPs for the XS (no idea why there are 2) are in fact:
>>>   172.18.0.1  (pingable, ssh, etc)
>>>   172.18.196.1  (schoolserver?)

No, the schoolserver is running at 172.18.96.1

>>>
>>> I remain very concerned that 172.18.196.1 is not pingable from the XO-1.5s, even when this IP's names {schoolserver, schoolserver.providence.uwimona.edu.jm} are pingable, responding with 172.18.196.1
>>>

To clear things up, /sbin/ifconfig on the server says:

[sverma at schoolserver ~]$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1F:F2:00:FD:10
          inet addr:172.18.96.1  Bcast:172.18.127.255  Mask:255.255.224.0
          inet6 addr: fe80::abcd:ef02/64 Scope:Link
          inet6 addr: fe80::21f:f2ff:fe00:fd10/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2838 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1617 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:268615 (262.3 KiB)  TX bytes:455477 (444.8 KiB)
          Interrupt:10 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 00:1C:49:01:04:3B
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:49ff:fe01:43b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5128 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6159 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:709454 (692.8 KiB)  TX bytes:634107 (619.2 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:27740 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27740 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3995149 (3.8 MiB)  TX bytes:3995149 (3.8 MiB)

tun0      Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.1.2.22  P-t-P:10.1.2.21  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:10246 (10.0 KiB)  TX bytes:8454 (8.2 KiB)


Where eth0 is LAN, eth1 is WAN (DSL router offers 192.168.1.0/24) and
tun0 is openvpn.

Sameer


>>> In Response to DSD:
>>> There is no server set in My Settings > Network > Server on any of the XO-1.5s
>>>
>>> Hopefully Sameer who helped with the original XS networking config 2 months ago can respond to Wad's WAN/LAN request below??
>>>
>>>> And I never got around to the second part of the comment.
>>>> eth0 (the "WAN" port) on the XS should be in a different subnet
>>>> than the laptops (the "LAN" ports).    If for some reason it is not,
>>>> difficulties will ensue as the routing tables will be screwed up.
>>>>
>>>> Cheers,
>>>> wad
>>>>
>>>>
>>>>> On Jun 4, 2012, at 6:19 PM, Holt wrote:
>>>>>
>>>>>> On 6/4/2012 3:27 PM, Sameer Verma wrote:
>>>>>>> On Sun, Jun 3, 2012 at 3:24 PM, Jerry Vonau<jvonau at shaw.ca>   wrote:
>>>>>>>> On Sat, 2012-06-02 at 13:15 -0700, Sameer Verma wrote:
>>>>>>>>> On Sat, Jun 2, 2012 at 10:10 AM, Sameer Verma<sverma at sfsu.edu>   wrote:
>>>>>>>>>> XS 0.7
>>>>>>>>>> OLPC build 874
>>>>>>>>>> Sugar 0.92.2
>>>>>>>>>>
>>>>>>>>>> The XO fails to register, but a folder is created for the XO on the XS
>>>>>>>>>> under /library/users/
>>>>>>>>>>
>>>>>>>>>> The XO shows no collaboration server under Control Panel | Network
>>>>>>>>>>
>>>>>>>>>> Any ideas? Pointers?
>>>>>>>>>>
>>>>>>>>>> cheers,
>>>>>>>>>> Sameer
>>>>>>>>> On the XS I see the machine as registered via /var/log/messages
>>>>>>>>> (schoolserver olpc_idmgr: Registered user abcdefgh with serial
>>>>>>>>> SHC03345845)
>>>>>>>>>
>>>>>>>>> So, looks like the server end is doing what it should, but the XO end is not?
>>>>>>>> Think you bumped into this: https://dev.laptop.org/ticket/11056
>>>>>>>>
>>>>>>>> Jerry
>>>>>>>>
>>>>>>> Thx. Will investigate. Copying Adam Holt and the Jamaica team on it
>>>>>>> (the trouble in in a school there).
>>>>>>>
>>>>>>> Sameer
>>>>>> One XO-1.5 successfully registered back on Saturday.  It successfully then pushed 36MB to the XS' /library/users/SHC03801C2E (after running /usr/bin/ds-backup.sh on the XO-1.5 and waiting ~30min).  So we went home Saturday night with a false sense of confidence!
>>>>>>
>>>>>> But no XO-1.5s will fully register today (all ~50 of the school's XOs are XO-1.5s).
>>>>>> Clearly, Jamaica's change from XS 0.6 to XS 0.7 two months ago destroyed reliable registration?
>>>>>>
>>>>>> Frustrating as all XO-1.5s do connect to XS, whose /library/users become populated with each XO's serial number, when they 1st attempt to register.  EG. directory /library/users/SHC03801C18 on XS is just 1 of many examples of an XO-1.5 "incompletely" registering -- all similar directories contain:
>>>>>>
>>>>>>  .bash_logout
>>>>>>  .bash_profile
>>>>>>  .bashrc
>>>>>>  .ssh
>>>>>>
>>>>>> Is it normal that XO-1.5s can ping the schoolserver in these 3 ways:
>>>>>>
>>>>>>  ping 18.172.0.1
>>>>>>  ping schoolserver    (responds as 18.172.196.1)
>>>>>>  ping schoolserver.providence.uwimona.edu.jm    (responds as 18.172.196.1)
>>>>>>
>>>>>> But yet CANNOT ping the schoolserver's eth0 IP address:
>>>>>>
>>>>>>  ping 18.172.196.1    (its "inet addr" according to "ifconfig etho" anyway)
>>>>>>
>>>>>> If it matters, a failng-to-register XO-1.5's /etc/resolv.conf reads as follows:
>>>>>>
>>>>>>  # Generated by NetworkManager
>>>>>>  domain providence.uwimona.edu.jm
>>>>>>  search providence.uwimona.edu.jm localdomain
>>>>>>  nameserver 172.18.196.1
>>>>>>
>>>>>> What should I be trying?? :)
>>>>>>
>>>>>> --
>>>>>> Help kids everywhere map their world, at http://olpcMAP.net !
>>>>>>
>>>>>> _______________________________________________
>>>>>> Server-devel mailing list
>>>>>> Server-devel at lists.laptop.org
>>>>>> http://lists.laptop.org/listinfo/server-devel
>>>>>
>>>
>>> --
>>> Help kids everywhere map their world, at http://olpcMAP.net !
>>>
>>
>>
>
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
>
>

More information about the Server-devel mailing list