From: Pavel Roskin <proski@gnu.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Thiago F. Tavares" <ttavares@halogica.com>,
linux-wireless@vger.kernel.org
Subject: Re: Issue: iwlist scanning sees the network; dhclient can't connect
Date: Wed, 30 Jul 2008 15:51:03 -0400 [thread overview]
Message-ID: <1217447463.25919.10.camel@dv> (raw)
In-Reply-To: <200807302141.07738.mb@bu3sch.de>
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.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-30 19:51 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 [this message]
2008-07-31 8:41 ` Johannes Berg
2008-07-31 13:31 ` Michael Buesch
2008-07-31 13:49 ` Dan Williams
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=1217447463.25919.10.camel@dv \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).