#4641 NORM Never A: NetworkManager doesn't gateway via mesh to Ethernet

[Zarro Boogs per Child]

#4641: NetworkManager doesn't gateway via mesh to Ethernet
-----------------------------+----------------------------------------------
 Reporter:  gnu              |       Owner:  dcbw                             
     Type:  defect           |      Status:  new                              
 Priority:  normal           |   Milestone:  Never Assigned                   
Component:  network manager  |     Version:  Development build as of this date
 Keywords:                   |    Verified:  0                                
-----------------------------+----------------------------------------------
 B4, Build 623, Q2D03.

 I have a B1 acting as network gateway, using a USB ethernet.  It runs 623.
 It can ping the outside world.  It shows as 169.254.8.139/16 on the mesh.

 I have a B4 trying to be a client of that mesh gateway.  It runs 623.  It
 can't ping the outside world.  (Ping 209.237.225.253 fails, network is
 unreachable.  That addr is on the Ethernet on the B1.)  It has not set up
 a DNS /etc/resolv.conf either.  netstat -nr shows no default route.  The
 B4 can ping the B1 (using both IPv4 and IPv6).

 Not sure if the problem is on the client or the gateway.  I tried
 connecting to a (bad) access point on the B4, then reconnecting to the
 mesh.  Didn't fix the problem.  THere's nothing in /var/log/messages on
 the B1 except for its DHCP lease renewals on the Ethernet; and
 /var/log/messages.1 is an empty file, so I don't know what NetworkManager
 on the B1 was thinking.

 I yanked the Ethernet out of the USB port on the B1.  I waited til the
 network disappeared from the Network display in the developer console.  I
 put it back in.  The network came back.  No improvement in the mesh portal
 function.

 I've attached the /var/log/messages from the B4 (client) and B1 (gateway).

-- 
Ticket URL: <http://dev.laptop.org/ticket/4641>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system