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 14:17:06 +0200 [thread overview]
Message-ID: <gshp43$n4q$1@ger.gmane.org> (raw)
In-Reply-To: <1240227187.6832.9.camel@hammer.suse.cz>
On 20-04-09 13:33, Stanislav Brabec wrote:
> Koen Kooi wrote:
>
>>> 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.
>
> Yes, at least on distro build conf level (but probably also on runtime
> or package selection level) there should a way to select networking
> concept:
>
> - ifup/ifdown with /etc/network/interfaces, udev hotplugging and
> wpa_supplicant handling lost association
>
> - connman handling everything
>
> - NetworkManager handling everything
There's a fourth option:
- connman handling everything that isn't in /etc/network/interfaces,
which is the option I like best :)
> OT: I have no experience with connman. Does it have the same "one
> network active at a time" constraint like NetworkManager has?
Nope :)
> And does connman automatically handle "association lost" case for wireless?
It does seem to do that for me with my wep network.
regards,
Koen
prev parent reply other threads:[~2009-04-20 12:21 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
2009-04-20 11:33 ` Stanislav Brabec
2009-04-20 12:17 ` Koen Kooi [this message]
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='gshp43$n4q$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