Re: CFT: ndis, iwi, ipw users

Sam Leffler wrote:
> Michal Mertl wrote:
> > Michal Mertl wrote:
> > 
> >>Sam Leffler wrote:
> >>
> >>>http://people.freebsd.org/~sam/curchan.patch
> >>>
> >>>has changes to resolve an issue with not recognizing when an ap moves to 
> >>>a different channel.  It eliminates the use of ic->ic_bss->ni_chan to 
> >>>identify the current channel while scanning.  It's been reviewed and 
> >>>tested ok on ath, wi, ral, and ural devices.  I need folks to verify it 
> >>>does not break ndis, iwi, and ipw devices (there are changes for awi but 
> >>>so far as I know noone uses awi).
> >>>
> >>>I want to get this committed to HEAD soon so quick feedback on those 
> >>>devices would be appreciated.  Thanks.
> >>>
> >>>	Sam
> >>
> >>
> >>My notebook with ipw still works. I have set up hostap on ath on channel
> >>1 and associated the notebook to it. I then changed the channel on the
> >>AP and the notebook immediately switched too.
> > 
> > 
> > I've just noticed that the channel reported by ifconfig on the ipw
> > station is wrong.
> > 
> > genius1# ifconfig ipw0
> > ipw0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >         inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
> >         ether 00:0c:f1:3e:8b:07
> >         media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
> >         status: associated
> >         ssid testap channel 1 bssid 00:0b:6b:35:dc:f0
> >         authmode OPEN privacy OFF txpowmax 100 bintval 100
> > genius1# ifconfig ipw0 list scan
> > SSID            BSSID              CHAN RATE  S:N   INT CAPS
> > testap          00:0b:6b:35:dc:f0    9   11M 62:0   100 E
> > genius1# ping 192.168.0.1
> > PING 192.168.0.1 (192.168.0.1): 56 data bytes
> > 64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=8.801 ms
> > ^C
> > --- 192.168.0.1 ping statistics ---
> > 1 packets transmitted, 1 packets received, 0% packet loss
> > round-trip min/avg/max/stddev = 8.801/8.801/8.801/0.000 ms
> > genius1#
> > 
> > 
> > Is this expected? I've never really checked it before.
> 
> I missed that change; thanks.  IEEE80211_IOC_CHANNEL should return 
> ic->ic_curchan instead of using the getcurchan routine.  Attached is an 
> updated patch for just ieee80211_ioctl.c.
> 
> 	Sam

The patch works - ifconfig on the station now correctly reports the
channel on which the association has been established.

Thanks

Michal