Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] new interface is already up but udev must call ifup anyway
Date: Mon, 20 Apr 2009 11:54:02 +0200	[thread overview]
Message-ID: <gshgnr$t3e$1@ger.gmane.org> (raw)
In-Reply-To: <1240220030.14678.5.camel@utx.utx.cz>

On 20-04-09 11:33, Stanislav Brabec wrote:
> Nicola Mfb wrote in Fri 03/06 2009 at 23:31 +0100:
>> 2009/3/6 Stanislav Brabec<utx@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@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:
>> http://lists.openmoko.org/pipermail/devel/2009-February/004895.html
>
> I researched this problem a bit. It seems, that it's caused by
> wpa_supplicant. New wpa_supplicant quickly responds to the device
> addition. It turns the device up and sets up the wireless link, but not
> network.
>
> It causes several problems:
> - link is up ->  no ifup
>
> After applying mentioned patch:
> - AP lookup takes about 20 seconds. Too much for dhcp client =>
>    it fails. Surprisingly avahi succeeds.
>
> Proposed solution:
> Either:
> wpa_wupplicant should perform (or trigger somehow) wlan network hotplug
> completely (i. e. call ifup after network association instead of udev
> device addition)
> or:
> Revert previous behavior - "passive" wpa_supplicant.
> or:
> Apply mentioned patch. Ugly, it fixes only symptom, not the cause.

With my distro hat on: shouldn't something like connman take care of 
wireless? Which would probably mean going back to a passive wpa_supplicant.

regards,

Koen




  reply	other threads:[~2009-04-20  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 20:57 [PATCH] new interface is already up but udev must call ifup anyway Stanislav Brabec
2009-03-06 22:31 ` Nicola Mfb
2009-04-20  9:33   ` Stanislav Brabec
2009-04-20  9:54     ` Koen Kooi [this message]
2009-04-20 11:33       ` Stanislav Brabec
2009-04-20 12:17         ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gshgnr$t3e$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox