On Wed, Mar 26, 2008 at 11:27 PM, John Goulah <jgoulah@xxxxxxxxx> wrote:
> On Wed, Mar 26, 2008 at 5:04 PM, Chatre, Reinette
>
> <reinette.chatre@xxxxxxxxx> wrote:
> >
>
> > On Wednesday, March 26, 2008 11:49 AM, John Goulah wrote:
> >
> > >
> > > $ iwconfig
> > > lo no wireless extensions.
> > >
> > > eth1 no wireless extensions.
> > >
> > > sit0 no wireless extensions.
> > >
> > > wmaster0 no wireless extensions.
> > >
> > > Warning: Driver for device wlan0 has been compiled with version 22
> > > of Wireless Extension, while this program supports up to version 20.
> > > Some things may be broken...
> > >
> > > wlan0 IEEE 802.11 ESSID:"goulahnet"
> > > Mode:Managed Frequency:2.412 GHz Access Point:
> > > Not-Associated Tx-Power=0 dBm
> > > Retry min limit:7 RTS thr:off Fragment thr=2352 B
> > > Link Quality:0 Signal level:0 Noise level:0
> > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> > >
> > >
> > >
> > > Is this warning a problem? Does this mean I need to get a newer
> > > iwconfig (I'm on debian etch, Wireless-Tools version 28)
> >
> > I don't know if it is necessary. In the above iwconfig output it does
> > not look as though you are associated though.
> >
>
>
>
> It appears I am still having some issues here with associating. Could
> this be on the driver end of things? It doesn't happen with another
> box (other drivers)
>
> I can disassociate:
> $ sudo iwconfig wlan0 ap off
> $ iwconfig
>
> wlan0 IEEE 802.11 ESSID:"goulahnet"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=14 dBm
>
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
>
> What I was doing before is showing Invalid:
>
>
> $ sudo iwconfig wlan0 ap any (same for auto here)
> $ iwconfig
>
> wlan0 IEEE 802.11 ESSID:"goulahnet"
> Mode:Managed Frequency:2.412 GHz Access Point: Invalid
> Tx-Power=14 dBm
>
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
>
>
> It does seem a bit random, and I did have it working there for a
> while, but it looked like if issue ctrl-C to wpa_supplicant it got
> into this state, or a reboot.
>
> Anything I can try here?
>
>
>
Quick followup, one thing I've found is that I can scan as root and
see my access point in the list:
Cell 09 - Address: 00:15:E9:FA:E2:DB
ESSID:"goulahnet"
Mode:Master
Frequency:2.462 GHz (Channel 11)
Channel:11
Quality=84/100 Signal level=-50 dBm Noise level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000208dd78c752
One time, that even got me associated. But after removing the module
and trying again to be sure, I'm still showing "Invalid"
This seems a bit odd to me- Ideas are appreciated, I'm happy to debug
where appropriate -
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
