#8343 NORM 8.2.1: Wired ethernet not always connecting on startup

[Zarro Boogs per Child]

#8343: Wired ethernet not always connecting on startup
----------------------------+-----------------------------------------------
   Reporter:  mikus         |       Owner:                                   
       Type:  defect        |      Status:  new                              
   Priority:  normal        |   Milestone:  8.2.1                            
  Component:  not assigned  |     Version:  Development build as of this date
 Resolution:                |    Keywords:  relnote                          
Next_action:  never set     |    Verified:  0                                
  Blockedby:                |    Blocking:                                   
----------------------------+-----------------------------------------------

Comment(by mikus):

 Replying to [comment:1 gregorio]:
 > Can you take a look at bug 7785 and let me know if you think what you
 see may be related to that?
 Hard to say if #7785 has a bearing, or not.

 For one, I have a "slim" DHCP server on the ethernet - and in my
 experience, it has always supplied information reliably.  (My other XO
 always gets assigned an IP address; this XO always has, except for a
 couple of recent cases.)  Though it is possible the DHCP server did not
 run quickly enough, that's unlikely.

 [[BR]]My history regarding plugging/unplugging the ethernet is extremely
 variable.  Back in January, if I unplugged, I would have to re-boot the XO
 for it to set up a wired connection again.  Then the telepathy code got
 updated, and plugging/unplugging worked as it should.  Then the included-
 in-build code got updated again, and plugging/unplugging no longer worked.
 Then the included-in-build code got updated again, and re-plugging would
 work one day out of 30.  [Then I think the telepathy code got updated
 again.]  I have seen re-plugging work once in the last 20 days -- but as
 you imagine, I've given up re-plugging as a way to get things working.
 [By the way, since about March, I NEVER recall the act of re-starting
 Sugar to have gotten ethernet to work -- I've always had to re-boot the XO
 instead.]  Haven't tested explicitly, but I've seen in the past that a
 short unplug (maybe as short as two seconds) *has* caused the interface's
 192. address (IPv4) to be replaced by an IPv6 address.

 Because I currently have only seven USB sockets to work with, I
 occasionally *do* need to unplug the ethernet adapter (to plug in some
 other USB device).  So from my viewpoint, I *would* like NM to access DHCP
 again if the ethernet gets plugged in again after a protracted no-wired-
 connection interval.  Also, once upon a time the ethernet connection would
 go crook when the DHCP lease expired.  [I keep my XOs powered up 24/7, and
 reboot only if I MUST.]  But in the last couple of months I've not seen
 any "spontaneous" dropping of the ethernet during continuous running (if I
 remember correctly, my DHCP lease period is around 24 hours).

 [[BR]]
 The way I tell if I have an ethernet or not, I issue 'ifconfig' as root
 from Terminal, and see if I have a 192. address shown for an interface.
 Normally that's good enough, but in the last month I've been hit with
 'Network is unreachable', even when the DHCP server has supplied the
 proper information (as shown, for example, by /etc/resolv.conf being set
 up correctly).  By the way, ever since about February, WHICH interface
 gets the ethernet changes from build to build - for instance, 753 might
 have it on eth0, but 756 on eth1, and so forth.  I've even seen the
 ethernet on eth2.  [Since 'suspend' drops the USB power, I usually have my
 physical ethernet adapter plugged into a self-powered USB hub, which in
 turn is plugged into the XO.  But after 'suspend' the wired connection is
 always permanently ignored by the XO - which is another ticket.]

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