tags 298863 = moreinfo
thanks
On Sat, Feb 11, 2006 at 04:43:14PM +0100, Andreas Pakulat wrote:
> On 11.02.06 15:11:47, Reinhard Tartler wrote:
> > can you please check if this bug still applies to you? There have been
> > several new upstream version since you submitted this bug and I'm fairly
> > sure that this bug does not apply anymore. Feel free to close this bug.
>
> This bug is still valid and I don't understand why it is marked as
> fixed-upstream, because it seems it is not.
interesting. I'm using madwifi on my laptop, and I used to use
wpasupplicant somewhat as 'roaming' daemon to roam between unencrypted,
WEP and WPA-EAP secured networks. I had no problems with my chip, so
this seems to be specific to ipw2100.
> Huh, oh. I just see that after establishing a connection withoug
> wpa_supplicant now I also get a connection with it. However removing the
> module and trying "fresh" shows that it again doesn't get an ip.
Hmmm. intersting. Which kernel are you using? and which version of
ipw2100?
Is this applicable to both options -D wext and -D ipw, or 'just'
-D wext?
I don't have an ipw wlan device here right now, I can try to catch my
girlfriends laptop with ipw2200 for some tests, though.
Gruesse,
Reinhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
