From: Dan Williams <dcbw@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Michael Buesch <mb@bu3sch.de>,
Johannes Berg <johannes@sipsolutions.net>,
"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 16:01:29 -0400 [thread overview]
Message-ID: <1217534489.9377.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1217516500.22143.3.camel@dv>
On Thu, 2008-07-31 at 11:01 -0400, Pavel Roskin wrote:
> On Thu, 2008-07-31 at 09:49 -0400, Dan Williams wrote:
> > 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.
>
> Sorry for going offtopic, but somebody picked up dhcpcd, and it's in a
> pretty good shape now, preparing for 4.0 release. It supports dhclient
> scripts, works with NetworkManager, and doesn't bring the interface
> down. It even have a git repository, with the latest commit 79 made
> minutes ago.
Yeah, I'm aware of that. But at the same time, there's a lot of
procedure, knowledge, integration, and custom scripts built up around
dhclient that isn't going to change overnight.
Dan
prev parent reply other threads:[~2008-07-31 20:04 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
2008-07-31 15:01 ` Pavel Roskin
2008-07-31 20:01 ` Dan Williams [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=1217534489.9377.15.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 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).