On Tue, Apr 19, 2011 at 01:53:19PM +0100, Roger Leigh wrote:
> On Tue, Apr 19, 2011 at 12:48:06PM +0200, Marco d'Itri wrote:
> > On Apr 18, Marco d'Itri <m...@linux.it> wrote:
> > 
> > > > As a result, I am still unconvinced that the udev logic is correct.
> > > You can test your theory by rebuilding udev without the use_run_tmpfs
> > > patch, I cannot reproduce your problem and apparently nobody else can.
> > Are there any news?
> > The current status is that 167-2 is known not work correctly only in
> > the following cases:
> > - if /etc/network/run/ is a symlink
> > - when installed your system
> 
> It simply appears it's just not automatically
> obtaining a lease.  Since I have
> 
>   allow-hotplug eth0
>   iface eth0 inet dhcp
> 
> could it be related to not getting a hotplug event from udev?
I switched
  allow-hotplug eth0
to
  auto eth0
and rebooted.  It then gets a dhcp lease without trouble.

So it would appear to be an issue with hotplug.  One things that looks
different is that both eth0 and eth1 are "up" but unconfigured:

eth0      Link encap:Ethernet  HWaddr aa:00:04:00:0a:04
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:fe1b:4d10/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:764 errors:0 dropped:0 overruns:0 frame:0
          TX packets:821 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:125215 (122.2 KiB)  TX bytes:89192 (87.1 KiB)
          Interrupt:17

eth1      Link encap:Ethernet  HWaddr aa:00:04:00:0a:04
          inet6 addr: fe80::a800:4ff:fe00:a04/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:18

(eth0 is configured here after changing the config to force it to use
dhcp).  Since the interface is already "up", maybe that's the reason
the events aren't generated.  So I guess the question now is, what's
bringing up the interface before ifupdown does?  Could it be udev?  Or
something else in early boot or the initramfs?


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Attachment: signature.asc
Description: Digital signature

Reply via email to