From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: ath5k-devel@lists.ath5k.org
Cc: Florian Mickler <florian@mickler.org>,
"Hans-J. Ullrich" <hans.ullrich@loop.de>,
Jiri Slaby <jirislaby@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: [ath5k-devel] Fw: Cannot register at bugzilla (bugreport added) [ ath5k bugreport ]
Date: Mon, 28 Sep 2009 09:42:55 +0200 [thread overview]
Message-ID: <200909280942.55317.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20090925191524.7b2b228c@schatten>
> There are already other reports of this problem in discussion
forums.
> It seems, the old madwifi-driver works better with dhcp - so
people say.
I cannot second that. For me, ath5k works perfectly with DHCP,
with WEXT ("iwconfig") and NL80211 ("iw") and with
wpa_supplicant.
DHCP was NEVER an issue.
--
http://www.holgerschurig.de
prev parent reply other threads:[~2009-09-28 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090925191524.7b2b228c@schatten>
2009-09-26 12:46 ` Fw: Cannot register at bugzilla (bugreport added) [ ath5k bugreport ] Bob Copeland
2009-09-28 7:42 ` Holger Schurig [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=200909280942.55317.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=florian@mickler.org \
--cc=hans.ullrich@loop.de \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).