Date: Thu, 3 Mar 2016 20:25:43 -0800 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-wireless@freebsd.org Subject: Re: odd behaviour on wireless on latest -head Message-ID: <CAJ-VmonYHXW1VBOKKrQVru0UiwHAifnCdtavJvFcZYx0dYdM2Q@mail.gmail.com> In-Reply-To: <CAJ-Vmo=HHRC=dYLQJP4pXrAFOcH%2BZFU%2BYddvuSQJmAndgdTiEg@mail.gmail.com> References: <CAJ-Vmo=HHRC=dYLQJP4pXrAFOcH%2BZFU%2BYddvuSQJmAndgdTiEg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rebooting it fixed it. I wonder if it's another manifestation of the interface mode flags getting set by the supplicant and not getting cleared and fixed later. Grr. Time to add more debugging. Adrian On Mar 3, 2016 3:53 PM, "Adrian Chadd" <adrian@freebsd.org> wrote: > hiya, > > there's something odd with the latest -head. it's not updating from > 11b to 11n on 2GHz channels, which is very bleh. > > Does anyone else see it? > > ifconfig wlan0 shows 11b associated, not HT20 or HT40. > > but it /says/ it was associated: > > Mar 3 15:51:44 victoria kernel: wlan0: start running, 0 vaps running > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_start_locked: up parent > iwn0 > Mar 3 15:51:44 victoria kernel: iwn0: iwn_read_firmware: ucode > rev=0x09dd0401 > Mar 3 15:51:44 victoria kernel: wlan0: start running, 1 vaps running > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_new_state_locked: > INIT -> SCAN (nrunning 0 nscanning 0) > Mar 3 15:51:44 victoria kernel: wlan0: ieee80211_newstate_cb: INIT -> > SCAN arg 0 > Mar 3 15:51:44 victoria kernel: wlan0: sta_newstate: INIT -> SCAN (0) > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] station > assoc via MLME > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] > ieee80211_ht_node_init: called > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > SCAN -> AUTH (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: SCAN -> > AUTH arg 192 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: SCAN -> AUTH (192) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > AUTH -> ASSOC (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: AUTH -> > ASSOC arg 0 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: AUTH -> ASSOC (0) > Mar 3 15:51:45 victoria kernel: wlan0: [e8:fc:af:94:fc:fc] assoc > success at aid 11: long preamble, long slot time, QoS, HT20 (+AMPDU) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_new_state_locked: > ASSOC -> RUN (nrunning 0 nscanning 0) > Mar 3 15:51:45 victoria kernel: wlan0: ieee80211_newstate_cb: ASSOC > -> RUN arg 16 > Mar 3 15:51:45 victoria kernel: wlan0: sta_newstate: ASSOC -> RUN (16) > Mar 3 15:51:45 victoria kernel: wlan0: link state changed to UP > Mar 3 15:51:52 victoria dhclient: New IP Address (wlan0): 192.168.5.64 > Mar 3 15:51:52 victoria dhclient: New Subnet Mask (wlan0): 255.255.0.0 > Mar 3 15:51:52 victoria dhclient: New Broadcast Address (wlan0): > 192.168.255.255 > Mar 3 15:51:52 victoria dhclient: New Routers (wlan0): 192.168.1.1 > > ..the transmit rate is showing up as 11b, not 11b rates (sysctl > dev.iwn.0.debug=0x1, and I can kinda read the plcp/rate values now ... > sigh. :) > > Anyway, I know this used to work fine, so I'll have to go over the > net80211 changes to see when they broke. > > Thanks, > > > > -adrian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonYHXW1VBOKKrQVru0UiwHAifnCdtavJvFcZYx0dYdM2Q>