From: Dan Williams <dcbw@redhat.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Pavel Roskin <proski@gnu.org>,
"Thiago F. Tavares" <ttavares@halogica.com>,
linux-wireless@vger.kernel.org
Subject: Re: Issue: iwlist scanning sees the network; dhclient can't connect
Date: Thu, 31 Jul 2008 09:49:19 -0400 [thread overview]
Message-ID: <1217512159.12016.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200807311531.54665.mb@bu3sch.de>
On Thu, 2008-07-31 at 15:31 +0200, Michael Buesch wrote:
> On Thursday 31 July 2008 10:41:05 Johannes Berg wrote:
> > On Wed, 2008-07-30 at 15:51 -0400, Pavel Roskin wrote:
> > > On Wed, 2008-07-30 at 21:41 +0200, Michael Buesch wrote:
> > >
> > > > dhclient works fine for me. Although it's true that it sometimes
> > > > messes with up/down state. But you _can_ use it, if you take some care.
> > >
> > > True. But b43 has the lowest dhclient survival rate of all drivers I
> > > know. That's an empirical observation, of course.
> >
> > I think debian patches out the down/up behaviour. We may be seeing that.
>
> Oh, that might explain why I don't see this behaviour.
We all agreed at the OLS Wireless Summit that the up/down behavior of
dhclient was just f**king stupid and should be patched out. Upstream
doesn't seem to be very responsive.
It just kills mac80211-based drivers, and drivers that do firmware
upload on dev->open() because all settings get lost and the driver would
have to re-load everything, which is ton of code in the driver that
shouldn't have to be there. It's bad for Intel WiMAX devices too
because they do firmware upload in dev->open().
Dan
next prev parent reply other threads:[~2008-07-31 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:13 Issue: iwlist scanning sees the network; dhclient can't connect Thiago F. Tavares
2008-07-30 19:36 ` Pavel Roskin
2008-07-30 19:41 ` Michael Buesch
2008-07-30 19:51 ` Pavel Roskin
2008-07-31 8:41 ` Johannes Berg
2008-07-31 13:31 ` Michael Buesch
2008-07-31 13:49 ` Dan Williams [this message]
2008-07-31 15:01 ` Pavel Roskin
2008-07-31 20:01 ` Dan Williams
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=1217512159.12016.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=proski@gnu.org \
--cc=ttavares@halogica.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.