2009/3/6 Stanislav Brabec <span dir="ltr"><<a href="mailto:utx@penguin.cz">utx@penguin.cz</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Few weeks ago yet another change happened in the dark, and network did<br>
not start to work automatically after inserting my WLAN card.<br>
<br>
Debugging this problem, I found that interface is already up but not<br>
configured when /etc/udev/scripts/network.sh is called. This script<br>
thinks, that card is already configured and quits. This behavior is<br>
intentional and was introduced three years ago (and working).<br>
<br>
The fix actually reverts following change:<br>
Author: Matthias Hentges <<a href="mailto:oe@hentges.net">oe@hentges.net</a>><br>
Date: Thu Apr 20 16:01:09 2006 +0000<br>
udev: network.sh: Do not ifup an already configured network device again.<br>
<br>
That is why I am asking:<br>
<br>
Is anybody aware of change, that made new interfaces up without<br>
configuring them? Was it an intention or not?<br>
</blockquote></div><br>I had the same problem with bnep bluetooth networking, and another issue when spawing dhcp, take a look at:<br><a href="http://lists.openmoko.org/pipermail/devel/2009-February/004895.html">http://lists.openmoko.org/pipermail/devel/2009-February/004895.html</a><br>
<br> Nicola<br><br>