Date: Wed, 19 Apr 2017 15:03:13 +0200 (CEST) From: Valentin VERGEZ <valentin.vergez@stormshield.eu> To: Adrian Chadd <adrian@freebsd.org> Cc: Michael Reifenberger <mike@reifenberger.com>, freebsd-wireless@freebsd.org Subject: Re: More than one SSID doesn't fully work with AR9280 (ath or hostapd bug?) Message-ID: <1980424436.49344919.1492606993421.JavaMail.zimbra@stormshield.eu> In-Reply-To: <CAJ-Vmok0Wb-69okde20GvVFc2Es8qSRUV2W9oTjOsY%2B-1MnS8g@mail.gmail.com> References: <20160914172742.Horde.ZL9ZWdGKhIB9Qt9HS2O7rhE@mail.eeeit.de> <CAJ-Vmok0Wb-69okde20GvVFc2Es8qSRUV2W9oTjOsY%2B-1MnS8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I experienced the same issue on 10.3 With two SSID, the ASSOC events are treated twice by hostapd, which discard the first when starting to process the second. So only the second SSID can establish an association. It still works if the first interface handles an OPEN SSID. By the way, I will soon work on HEAD and try to reproduce too. --- Valentin VERGEZ > De: "Adrian Chadd" <adrian@freebsd.org> > À: "Michael Reifenberger" <mike@reifenberger.com> > Cc: freebsd-wireless@freebsd.org > Envoyé: Mercredi 14 Septembre 2016 18:00:32 > Objet: Re: More than one SSID doesn't fully work with AR9280 (ath or hostapd > bug?) > hi, > I'll have to try it on -head. I tohught we fixed these issues! > -a > On 14 September 2016 at 08:27, Michael Reifenberger > <mike@reifenberger.com> wrote: > > Hi, > > I'm using pfsense (FreeBSD fw.rm-i.net 10.3-RELEASE-p7 FreeBSD > > 10.3-RELEASE-p7 #0 a0a18f4(stable/16.7): Mon Aug 15 06:35:28 CEST 2016 > > root@sensey64:/usr/obj/usr/src/sys/SMP amd64) and a Ubiquiti SR71-E on a > > APU.2C4 to get the following: > > I want two interfaces ath0_wlan1 and ath0_wlan2 with different SSID's and > > PSK's in order to implement > > two different access filters. > > The configuration works. I see: > > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290 > > ether 00:15:6d:85:e3:00 > > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> > > status: running > > ath0_wlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > > 1500 > > ether 00:15:6d:85:e3:00 > > inet6 fe80::215:6dff:fe85:e300%ath0_wlan1 prefixlen 64 scopeid 0x9 > > inet 10.0.4.1 netmask 0xffffff00 broadcast 10.0.4.255 > > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> > > status: running > > ssid WL1 channel 2 (2417 MHz 11g ht/40+) bssid 00:15:6d:85:e3:00 > > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 > > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 > > protmode RTSCTS ampdulimit 64k ampdudensity 8 shortgi wme burst > > -apbridge dtimperiod 1 -dfs > > ath0_wlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > > 1500 > > ether 06:15:6d:85:e3:00 > > inet6 fe80::415:6dff:fe85:e300%ath0_wlan2 prefixlen 64 scopeid 0xa > > inet 10.0.5.1 netmask 0xffffff00 broadcast 10.0.5.255 > > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> > > status: running > > ssid WL2 channel 2 (2417 MHz 11g ht/40+) bssid 06:15:6d:85:e3:00 > > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 > > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 > > protmode RTSCTS ampdulimit 64k ampdudensity 8 shortgi wme burst > > -apbridge dtimperiod 1 -dfs > > Both hostapd.conf's seem reasonable: > > root@fw:/var/etc # diff -u2 hostapd_ath0_wlan1.conf hostapd_ath0_wlan2.conf > > --- hostapd_ath0_wlan1.conf 2016-03-07 02:00:58.528705000 +0100 > > +++ hostapd_ath0_wlan2.conf 2016-03-07 02:01:00.348875000 +0100 > > @@ -1,3 +1,3 @@ > > -interface=ath0_wlan1 > > +interface=ath0_wlan2 > > driver=bsd > > logger_syslog=-1 > > @@ -5,11 +5,11 @@ > > logger_stdout=-1 > > logger_stdout_level=0 > > -dump_file=/tmp/hostapd_ath0_wlan1.dump > > +dump_file=/tmp/hostapd_ath0_wlan2.dump > > ctrl_interface=/var/run/hostapd > > ctrl_interface_group=wheel > > -#accept_mac_file=/tmp/hostapd_ath0_wlan1.accept > > -#deny_mac_file=/tmp/hostapd_ath0_wlan1.deny > > +#accept_mac_file=/tmp/hostapd_ath0_wlan2.accept > > +#deny_mac_file=/tmp/hostapd_ath0_wlan2.deny > > #macaddr_acl= > > -ssid=WL1 > > +ssid=WL2 > > debug= > > auth_algs=1 > > The problem: > > Only one of the interfaces works fully at the same time > > Either the first one or the second one, but not both together. > > If enabling both at the same time, I see both SSID's on the WLAN, > > can authenticate to one of the interfaces (probably the first configured > > one) but not > > to the other. The other allways gives an authentification failure. > > How can I debug this issue further? > > BTW (if it's related): > > Over time I see some of the following errors in dmesg: > > ... > > ath0: stuck beacon; resetting (bmiss count 4) > > ath0: stuck beacon; resetting (bmiss count 4) > > ath0: stuck beacon; resetting (bmiss count 4) > > ath0: stuck beacon; resetting (bmiss count 4) > > ath0: stuck beacon; resetting (bmiss count 4) > > .... > > In the wireless logfile I see during an unsuccessfull authentification: > > ... > > Sep 14 17:19:53 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 1 > > notification > > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: start > > authentication > > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:54 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:54 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:55 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:55 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:56 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:56 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: PTKSTART: > > Retry limit 4 reached > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 3 > > notification > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) > > Sep 14 17:19:57 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 2 > > notification > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:19:57 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 1 > > notification > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: start > > authentication > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:58 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:58 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:19:59 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:19:59 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:00 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:00 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: PTKSTART: > > Retry limit 4 reached > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 3 > > notification > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:01 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 2 > > notification > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:01 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 1 > > notification > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: start > > authentication > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:02 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:02 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:03 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:03 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:04 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:04 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: PTKSTART: > > Retry limit 4 reached > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 3 > > notification > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 2 > > notification > > Sep 14 17:20:05 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:05 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 1 > > notification > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: start > > authentication > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:06 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:06 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:07 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:07 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:08 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:08 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: PTKSTART: > > Retry limit 4 reached > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 3 > > notification > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:09 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 2 > > notification > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:09 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > associated > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 1 > > notification > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: start > > authentication > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:10 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:10 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:11 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:11 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:12 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:12 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: sending > > 1/4 msg of 4-Way Handshake > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: EAPOL-Key > > timeout > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: PTKSTART: > > Retry limit 4 reached > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 3 > > notification > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: > > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:13 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE 802.11: > > disassociated > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: event 2 > > notification > > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE 802.1X: > > unauthorizing port > > ... > > Any clues? > > Thanks in advance! > > --- > > mike mr@freebsd.org > > Gruß > > --- > > Michael Reifenberger > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Wed Apr 19 13:30:34 2017 Return-Path: <owner-freebsd-wireless@freebsd.org> Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B294D45D3F for <freebsd-wireless@mailman.ysv.freebsd.org>; Wed, 19 Apr 2017 13:30:34 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail.eeeit.de (mail.eeeit.de [37.120.160.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2697CE09; Wed, 19 Apr 2017 13:30:33 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from [10.0.5.100] (ppp-62-216-209-216.dynamic.mnet-online.de [62.216.209.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mike@reifenberger.com) by mail.eeeit.de (Postfix) with ESMTPSA id 8BF215F9D; Wed, 19 Apr 2017 15:23:43 +0200 (CEST) Date: Wed, 19 Apr 2017 15:23:57 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <1980424436.49344919.1492606993421.JavaMail.zimbra@stormshield.eu> References: <20160914172742.Horde.ZL9ZWdGKhIB9Qt9HS2O7rhE@mail.eeeit.de> <CAJ-Vmok0Wb-69okde20GvVFc2Es8qSRUV2W9oTjOsY+-1MnS8g@mail.gmail.com> <1980424436.49344919.1492606993421.JavaMail.zimbra@stormshield.eu> MIME-Version: 1.0 Subject: Re: More than one SSID doesn't fully work with AR9280 (ath or hostapd bug?) To: Valentin VERGEZ <valentin.vergez@stormshield.eu>, Adrian Chadd <adrian@freebsd.org> CC: freebsd-wireless@freebsd.org From: Michael <mike@reifenberger.com> Message-ID: <F6A0975D-4239-43A0-AFCD-85D228A092A4@reifenberger.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." <freebsd-wireless.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-wireless>, <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>; List-Post: <mailto:freebsd-wireless@freebsd.org> List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 19 Apr 2017 13:30:34 -0000 Hi, with a current Opnsense, based on FreeBSD-11 its working (two SSID's) now for me. Greetings --- Mike Am 19. April 2017 15:03:13 MESZ schrieb Valentin VERGEZ <valentin.vergez@stormshield.eu>: >Hi, > >I experienced the same issue on 10.3 >With two SSID, the ASSOC events are treated twice by hostapd, which >discard the first when starting to process the second. >So only the second SSID can establish an association. > >It still works if the first interface handles an OPEN SSID. > >By the way, I will soon work on HEAD and try to reproduce too. > >--- > >Valentin VERGEZ > >> De: "Adrian Chadd" <adrian@freebsd.org> >> À: "Michael Reifenberger" <mike@reifenberger.com> >> Cc: freebsd-wireless@freebsd.org >> Envoyé: Mercredi 14 Septembre 2016 18:00:32 >> Objet: Re: More than one SSID doesn't fully work with AR9280 (ath or >hostapd >> bug?) > >> hi, > >> I'll have to try it on -head. I tohught we fixed these issues! > >> -a > >> On 14 September 2016 at 08:27, Michael Reifenberger >> <mike@reifenberger.com> wrote: >> > Hi, > >> > I'm using pfsense (FreeBSD fw.rm-i.net 10.3-RELEASE-p7 FreeBSD >> > 10.3-RELEASE-p7 #0 a0a18f4(stable/16.7): Mon Aug 15 06:35:28 CEST >2016 >> > root@sensey64:/usr/obj/usr/src/sys/SMP amd64) and a Ubiquiti SR71-E >on a >> > APU.2C4 to get the following: > >> > I want two interfaces ath0_wlan1 and ath0_wlan2 with different >SSID's and >> > PSK's in order to implement >> > two different access filters. > >> > The configuration works. I see: >> > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 >mtu 2290 >> > ether 00:15:6d:85:e3:00 >> > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> >> > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> >> > status: running >> > ath0_wlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> >metric 0 mtu >> > 1500 >> > ether 00:15:6d:85:e3:00 >> > inet6 fe80::215:6dff:fe85:e300%ath0_wlan1 prefixlen 64 scopeid 0x9 >> > inet 10.0.4.1 netmask 0xffffff00 broadcast 10.0.4.255 >> > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> >> > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> >> > status: running >> > ssid WL1 channel 2 (2417 MHz 11g ht/40+) bssid 00:15:6d:85:e3:00 >> > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 >> > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 >> > protmode RTSCTS ampdulimit 64k ampdudensity 8 shortgi wme burst >> > -apbridge dtimperiod 1 -dfs >> > ath0_wlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> >metric 0 mtu >> > 1500 >> > ether 06:15:6d:85:e3:00 >> > inet6 fe80::415:6dff:fe85:e300%ath0_wlan2 prefixlen 64 scopeid 0xa >> > inet 10.0.5.1 netmask 0xffffff00 broadcast 10.0.5.255 >> > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> >> > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> >> > status: running >> > ssid WL2 channel 2 (2417 MHz 11g ht/40+) bssid 06:15:6d:85:e3:00 >> > country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 >> > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 27 scanvalid 60 >> > protmode RTSCTS ampdulimit 64k ampdudensity 8 shortgi wme burst >> > -apbridge dtimperiod 1 -dfs > >> > Both hostapd.conf's seem reasonable: >> > root@fw:/var/etc # diff -u2 hostapd_ath0_wlan1.conf >hostapd_ath0_wlan2.conf >> > --- hostapd_ath0_wlan1.conf 2016-03-07 02:00:58.528705000 +0100 >> > +++ hostapd_ath0_wlan2.conf 2016-03-07 02:01:00.348875000 +0100 >> > @@ -1,3 +1,3 @@ >> > -interface=ath0_wlan1 >> > +interface=ath0_wlan2 >> > driver=bsd >> > logger_syslog=-1 >> > @@ -5,11 +5,11 @@ >> > logger_stdout=-1 >> > logger_stdout_level=0 >> > -dump_file=/tmp/hostapd_ath0_wlan1.dump >> > +dump_file=/tmp/hostapd_ath0_wlan2.dump >> > ctrl_interface=/var/run/hostapd >> > ctrl_interface_group=wheel >> > -#accept_mac_file=/tmp/hostapd_ath0_wlan1.accept >> > -#deny_mac_file=/tmp/hostapd_ath0_wlan1.deny >> > +#accept_mac_file=/tmp/hostapd_ath0_wlan2.accept >> > +#deny_mac_file=/tmp/hostapd_ath0_wlan2.deny >> > #macaddr_acl= >> > -ssid=WL1 >> > +ssid=WL2 >> > debug= >> > auth_algs=1 > >> > The problem: >> > Only one of the interfaces works fully at the same time >> > Either the first one or the second one, but not both together. > >> > If enabling both at the same time, I see both SSID's on the WLAN, >> > can authenticate to one of the interfaces (probably the first >configured >> > one) but not >> > to the other. The other allways gives an authentification failure. > >> > How can I debug this issue further? > >> > BTW (if it's related): >> > Over time I see some of the following errors in dmesg: >> > ... >> > ath0: stuck beacon; resetting (bmiss count 4) >> > ath0: stuck beacon; resetting (bmiss count 4) >> > ath0: stuck beacon; resetting (bmiss count 4) >> > ath0: stuck beacon; resetting (bmiss count 4) >> > ath0: stuck beacon; resetting (bmiss count 4) >> > .... > > >> > In the wireless logfile I see during an unsuccessfull >authentification: >> > ... >> > Sep 14 17:19:53 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 1 >> > notification >> > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >start >> > authentication >> > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:19:53 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:54 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:54 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:55 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:55 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:56 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:56 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >PTKSTART: >> > Retry limit 4 reached >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 3 >> > notification >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) >> > Sep 14 17:19:57 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 2 >> > notification >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:19:57 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 1 >> > notification >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >start >> > authentication >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:19:57 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:58 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:58 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:19:59 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:19:59 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:00 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:00 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >PTKSTART: >> > Retry limit 4 reached >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 3 >> > notification >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:01 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 2 >> > notification >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:01 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 1 >> > notification >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >start >> > authentication >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:01 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:02 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:02 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:03 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:03 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:04 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:04 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >PTKSTART: >> > Retry limit 4 reached >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 3 >> > notification >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 2 >> > notification >> > Sep 14 17:20:05 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:05 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 1 >> > notification >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >start >> > authentication >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:05 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:06 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:06 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:07 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:07 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:08 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:08 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >PTKSTART: >> > Retry limit 4 reached >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 3 >> > notification >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:09 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 2 >> > notification >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:09 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > associated >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 1 >> > notification >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >start >> > authentication >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:09 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:10 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:10 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:11 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:11 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:12 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:12 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >sending >> > 1/4 msg of 4-Way Handshake >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >EAPOL-Key >> > timeout >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >PTKSTART: >> > Retry limit 4 reached >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 3 >> > notification >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DEAUTHENTICATE.indication(c4:85:08:3a:cf:f0, 2) >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 MLME: >> > MLME-DELETEKEYS.request(c4:85:08:3a:cf:f0) >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:13 fw hostapd: ath0_wlan1: STA c4:85:08:3a:cf:f0 IEEE >802.11: >> > disassociated >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 WPA: >event 2 >> > notification >> > Sep 14 17:20:13 fw hostapd: ath0_wlan2: STA c4:85:08:3a:cf:f0 IEEE >802.1X: >> > unauthorizing port >> > ... > >> > Any clues? > >> > Thanks in advance! >> > --- >> > mike mr@freebsd.org > > >> > Gruß >> > --- >> > Michael Reifenberger > >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >"freebsd-wireless-unsubscribe@freebsd.org" Gruß --- Michael From owner-freebsd-wireless@freebsd.org Wed Apr 19 14:01:42 2017 Return-Path: <owner-freebsd-wireless@freebsd.org> Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55381D457B2 for <freebsd-wireless@mailman.ysv.freebsd.org>; Wed, 19 Apr 2017 14:01:42 +0000 (UTC) (envelope-from valentin.vergez@stormshield.eu) Received: from work.stormshield.eu (gwlille.netasq.com [91.212.116.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2EB918C; Wed, 19 Apr 2017 14:01:40 +0000 (UTC) (envelope-from valentin.vergez@stormshield.eu) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTPS id 632DA37615B1; Wed, 19 Apr 2017 15:56:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 56DEF37615A1; Wed, 19 Apr 2017 15:56:20 +0200 (CEST) Received: from work.stormshield.eu ([127.0.0.1]) by localhost (work.stormshield.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9ykNyYz9pX7r; Wed, 19 Apr 2017 15:56:20 +0200 (CEST) Received: from work.stormshield.eu (localhost [127.0.0.1]) by work.stormshield.eu (Postfix) with ESMTP id 42431376158C; Wed, 19 Apr 2017 15:56:20 +0200 (CEST) Date: Wed, 19 Apr 2017 15:56:20 +0200 (CEST) From: Valentin VERGEZ <valentin.vergez@stormshield.eu> To: freebsd-wireless@freebsd.org Message-ID: <159600163.49355995.1492610180223.JavaMail.zimbra@stormshield.eu> Subject: [PHY] Adaptive equipment MIME-Version: 1.0 Thread-Topic: Adaptive equipment Thread-Index: DvLOuHLXXWm/MB64YghNGoiqlkW2kA=Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." <freebsd-wireless.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-wireless>, <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>; List-Post: <mailto:freebsd-wireless@freebsd.org> List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 19 Apr 2017 14:01:42 -0000 Hi, Do you guys know if the "Adaptive" aspect on a FreeBSD wifi product is manageable ? For an ETSI compliance certification, on a FreeBSD wifi Access Point with Atheros AR9380 NIC, the certifying authority needs to know if the equipment is adaptive or non-adaptive. And if it's an adaptive equipment, if it has the possibility to switch to a non-adaptive mode. Regarding ETSI EN 300 328 V1.9.1 section 4.2.2, Adaptive could correspond to DFS ... which, on hostap mode, is not fully implemented ? I thought that adaptive was for auto-selecting modulation depending on Signal/Noise ratio. But now, i'm confused. However, it is my understanding that these aspects are operated by the Qualcomm HAL and therefore not manageable. I seek confirmation on this point. While I am on the subject, I wonder if the "Listen Before Talk" is Frame Based or Load Based. And again, is it operated by the HAL or an upper layer ? Thanks, --- Valentin VERGEZ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1980424436.49344919.1492606993421.JavaMail.zimbra>