Re: ipw2200 fatal error and NM

[Bill Moss <bmoss clemson edu>]

Yes, I have been active in opening ipw2200 bugs at www.bughost.org. Yes, 
setting the ESSID last seems to be "standard" if there is such a thing 
with wireless.

Besides the experiments I listed, ipw2200 is doing one other strange 
thing. Start with the card unconfigured with essid=any and key=off. Now 
set the key on the home AP which can handle both Open System and Shared 
Key authentication. Go back and check the set up with iwconfig. You find 
that the essid has also been set. I assume ipw2200 is getting the essid 
from a scan. This means that setting the key is causing the scan, not 
setting the essid. This seems backwards so me.

[root localhost ~]# iwconfig eth1
eth1      unassociated  ESSID:off/any
         Mode:Managed  Channel=0  Access Point: 00:00:00:00:00:00
         Bit Rate=0kb/s   Tx-Power=20 dBm
         RTS thr:off   Fragment thr:off
         Encryption key:off
         Power Management:off
         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

[root localhost ~]# iwconfig eth1 key xxxxxxxxxxxxxxxxxxxxxxxxxx
[root localhost ~]# iwconfig eth1
eth1      IEEE 802.11b  ESSID:"mosswap"
         Mode:Managed  Frequency:2.437GHz  Access Point: 00:01:24:F0:40:5A
         Bit Rate=11Mb/s   Tx-Power=20 dBm
         RTS thr:off   Fragment thr:off
         Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx   Security 
mode:open
         Power Management:off
         Link Quality=91/100  Signal level=-53 dBm  Noise level=-82 dBm
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0


Dan Williams wrote:

> On Sun, 2005-01-16 at 16:01 -0500, Bill Moss wrote:
>  
>
> > Bug committed to ipw2200
> >    
>
> Bill,
>
> You submitted this to the ipw2200 people, have they given any
> explanation for the behavior?  (I assume we're talking about
> http://www.bughost.org/bugzilla/show_bug.cgi?id=534 here...)
>
> I always tried to set the ESSID _last_ in the NM code due to this issue,
> where in most cards setting the "essid" triggers the card to commit all
> changes up to that point and to begin scanning again.  Some cards also
> flush the firmware and reload it when a new essid is set, as the card's
> whole state has changed.
>
> Dan
>
>
>  

--
Bill Moss
Professor, Mathematical Sciences
Clemson University