[oe] [PATCH] new interface is already up but udev must call ifup anyway

Nicola Mfb nicola.mfb at gmail.com
Fri Mar 6 23:31:39 CET 2009

2009/3/6 Stanislav Brabec <utx at penguin.cz>

> Few weeks ago yet another change happened in the dark, and network did
> not start to work automatically after inserting my WLAN card.
> Debugging this problem, I found that interface is already up but not
> configured when /etc/udev/scripts/network.sh is called. This script
> thinks, that card is already configured and quits. This behavior is
> intentional and was introduced three years ago (and working).
> The fix actually reverts following change:
> Author: Matthias Hentges <oe at hentges.net>
> Date:   Thu Apr 20 16:01:09 2006 +0000
>    udev: network.sh: Do not ifup an already configured network device
> again.
> That is why I am asking:
> Is anybody aware of change, that made new interfaces up without
> configuring them? Was it an intention or not?

I had the same problem with bnep bluetooth networking, and another issue
when spawing dhcp, take a look at:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/devel/attachments/20090306/b48a506a/attachment.htm 

More information about the devel mailing list