Re: WPA2 Enterprise with hostapd and iphone
Is there any point in trying just the hostapd code from head? Will that work at all on a 10.1 machine? > On 30 mar 2015, at 02:22, Adrian Chadd wrote: > > Hi! > > * which NIC is this? > * can you please try -HEAD A lot of bugs have been fixed! > > > -a > > >> On 29 March 2015 at 06:31, Peter Ankerstål wrote: >> Hi! >> >> I have problems with my iphone since i switched to wpa2 enterprise on my >> home network. (All other devices work fine including ipad and macs). The >> connection seems to work fine at first but then it gets REALLY slow or no >> connection at all. (but iOS still shows it as connected). >> >> machine: >> FreeBSD gw 10.1-RELEASE-p1 FreeBSD 10.1-RELEASE-p1 #2 r275849 >> >> # hostapd -v >> hostapd v2.0 >> User space daemon for IEEE 802.11 AP management, >> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator >> Copyright (c) 2002-2012, Jouni Malinen and contributors >> >> hostapd.conf: >> — >> interface=wlan0 >> driver=bsd >> logger_syslog=-1 >> logger_syslog_level=0 >> ctrl_interface=/var/run/hostapd >> ctrl_interface_group=wheel >> ssid=web >> wpa=2 >> wpa_key_mgmt=WPA-EAP >> wpa_pairwise=TKIP CCMP >> macaddr_acl=0 >> auth_algs=1 >> own_ip_addr=127.0.0.1 >> ieee8021x=1 >> eap_server=1 >> eapol_version=1 >> eap_user_file=/etc/hostapd_eap_user >> ca_cert=/etc/ssl/startssl.ca.pem >> server_cert=/etc/ssl/auth.pean.org/auth.pean.org.crt >> private_key=/etc/ssl/auth.pean.org/auth.pean.org.key >> — >> >> This is what hostapd spits out when I connect with the phone: >> >> — >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: event 1 >> notification >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: start >> authentication >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: start >> authentication >> Mar 29 15:14:08 gw hostapd: wlan1: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan2: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> unauthorizing port >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 105) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=105 len=19) from STA: EAP Response-Identity >> (1) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 106) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=106 len=152) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 107) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=107 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 108) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=108 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 109) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=109 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 110) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=110 len=592) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 111) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=111 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 112) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=112 len=59) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 113) &
Re: WPA2 Enterprise with hostapd and iphone
> On 30 Mar 2015, at 02:22, Adrian Chadd wrote: > > Hi! > > * which NIC is this? AR9300 > * can you please try -HEAD A lot of bugs have been fixed! > Hehe, Im not sure Im ready for another round of -HEAD right now. :) > > -a > > > On 29 March 2015 at 06:31, Peter Ankerstål wrote: >> Hi! >> >> I have problems with my iphone since i switched to wpa2 enterprise on my >> home network. (All other devices work fine including ipad and macs). The >> connection seems to work fine at first but then it gets REALLY slow or no >> connection at all. (but iOS still shows it as connected). >> >> machine: >> FreeBSD gw 10.1-RELEASE-p1 FreeBSD 10.1-RELEASE-p1 #2 r275849 >> >> # hostapd -v >> hostapd v2.0 >> User space daemon for IEEE 802.11 AP management, >> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator >> Copyright (c) 2002-2012, Jouni Malinen and contributors >> >> hostapd.conf: >> — >> interface=wlan0 >> driver=bsd >> logger_syslog=-1 >> logger_syslog_level=0 >> ctrl_interface=/var/run/hostapd >> ctrl_interface_group=wheel >> ssid=web >> wpa=2 >> wpa_key_mgmt=WPA-EAP >> wpa_pairwise=TKIP CCMP >> macaddr_acl=0 >> auth_algs=1 >> own_ip_addr=127.0.0.1 >> ieee8021x=1 >> eap_server=1 >> eapol_version=1 >> eap_user_file=/etc/hostapd_eap_user >> ca_cert=/etc/ssl/startssl.ca.pem >> server_cert=/etc/ssl/auth.pean.org/auth.pean.org.crt >> private_key=/etc/ssl/auth.pean.org/auth.pean.org.key >> — >> >> This is what hostapd spits out when I connect with the phone: >> >> — >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: event 1 >> notification >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: start >> authentication >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: start >> authentication >> Mar 29 15:14:08 gw hostapd: wlan1: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan2: STA cb:aa:3a:a1:78:7b IEEE 802.11: >> associated >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> unauthorizing port >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 105) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=105 len=19) from STA: EAP Response-Identity >> (1) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 106) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=106 len=152) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 107) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=107 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 108) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=108 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 109) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=109 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 110) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=110 len=592) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 111) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=111 len=6) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 112) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> received EAP packet (code=2 id=112 len=59) from STA: EAP Response-PEAP (25) >> Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: >> Sending EAP Packet (identifier 113) >> Mar 29 15:14:08 gw hostap
WPA2 Enterprise with hostapd and iphone
Hi! I have problems with my iphone since i switched to wpa2 enterprise on my home network. (All other devices work fine including ipad and macs). The connection seems to work fine at first but then it gets REALLY slow or no connection at all. (but iOS still shows it as connected). machine: FreeBSD gw 10.1-RELEASE-p1 FreeBSD 10.1-RELEASE-p1 #2 r275849 # hostapd -v hostapd v2.0 User space daemon for IEEE 802.11 AP management, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator Copyright (c) 2002-2012, Jouni Malinen and contributors hostapd.conf: — interface=wlan0 driver=bsd logger_syslog=-1 logger_syslog_level=0 ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=web wpa=2 wpa_key_mgmt=WPA-EAP wpa_pairwise=TKIP CCMP macaddr_acl=0 auth_algs=1 own_ip_addr=127.0.0.1 ieee8021x=1 eap_server=1 eapol_version=1 eap_user_file=/etc/hostapd_eap_user ca_cert=/etc/ssl/startssl.ca.pem server_cert=/etc/ssl/auth.pean.org/auth.pean.org.crt private_key=/etc/ssl/auth.pean.org/auth.pean.org.key — This is what hostapd spits out when I connect with the phone: — Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.11: associated Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: event 1 notification Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: start authentication Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: start authentication Mar 29 15:14:08 gw hostapd: wlan1: STA cb:aa:3a:a1:78:7b IEEE 802.11: associated Mar 29 15:14:08 gw hostapd: wlan2: STA cb:aa:3a:a1:78:7b IEEE 802.11: associated Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: unauthorizing port Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 105) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=105 len=19) from STA: EAP Response-Identity (1) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 106) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=106 len=152) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 107) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=107 len=6) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 108) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=108 len=6) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 109) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=109 len=6) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 110) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=110 len=592) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 111) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=111 len=6) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 112) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=112 len=59) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 113) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=113 len=107) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 114) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=114 len=43) from STA: EAP Response-PEAP (25) Mar 29 15:14:08 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 115) Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: received EAP packet (code=2 id=115 len=43) from STA: EAP Response-PEAP (25) Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b IEEE 802.1X: Sending EAP Packet (identifier 115) Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: sending 1/4 msg of 4-Way Handshake Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: received EAPOL-Key frame (2/4 Pairwise) Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: sending 3/4 msg of 4-Way Handshake Mar 29 15:14:09 gw hostapd: wlan0: STA cb:aa:3a:a1:78:7b WPA: received EAPOL-Key frame (4/4 Pairwise) Mar 29 15:14:09 gw hostapd: wl
Re: 802.11ac on FreeBSD
Hehe, I see. Hälsningar / regards Peter Ankerstål > On 22 jan 2015, at 18:07, Adrian Chadd wrote: > > ... I have so much first gen 11ac hardware it hurts. I'm lacking time. :P > > > > > -adrian > > >> On 22 January 2015 at 05:35, Peter Ankerstål wrote: >> Hi, >> >> What if I buy you a >> http://202.75.43.34:809/WPproductdetailinfo.asp?model=WLE600VX&acc1Panel=1 ? >> :D >> >> /Peter. >> >> >>> On 01/07/2015 05:22 PM, Adrian Chadd wrote: >>> >>> Hi, >>> >>> There isn't 11ac support in the wifi stack. :( >>> >>> >>> >>> -adrian >>> >>> >>>> On 7 January 2015 at 06:19, Peter Ankerstål wrote: >>>> >>>> Hi! >>>> >>>> What cooking within this field? Im looking for a ac radio supported by >>>> FreeBSD. Preferably a minipcie. >>>> >>>> on https://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport it says >>>> "The >>>> 802.11ac devices will be supported by an alternate driver (not yet >>>> written.) >>>> " >>>> >>>> Thanks! >>>> >>>> /Peter. > smime.p7s Description: S/MIME cryptographic signature
Re: 802.11ac on FreeBSD
Hi, What if I buy you a http://202.75.43.34:809/WPproductdetailinfo.asp?model=WLE600VX&acc1Panel=1 ? :D /Peter. On 01/07/2015 05:22 PM, Adrian Chadd wrote: Hi, There isn't 11ac support in the wifi stack. :( -adrian On 7 January 2015 at 06:19, Peter Ankerstål wrote: Hi! What cooking within this field? Im looking for a ac radio supported by FreeBSD. Preferably a minipcie. on https://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport it says "The 802.11ac devices will be supported by an alternate driver (not yet written.) " Thanks! /Peter. smime.p7s Description: S/MIME Cryptographic Signature
802.11ac on FreeBSD
Hi! What cooking within this field? Im looking for a ac radio supported by FreeBSD. Preferably a minipcie. on https://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport it says "The 802.11ac devices will be supported by an alternate driver (not yet written.) " Thanks! /Peter. smime.p7s Description: S/MIME Cryptographic Signature
Re: Multiple ssid or multiple radios with hostapd
On 01/06/15 17:01, Adrian Chadd wrote: Hi! So: * you can run one hostapd - just not via the startup script. You can just pass it multiple config files at the command line. Try it and if you make it work, we'll figur eout how to teach the hostapd rc script about taking a specific config file parameter so we can list config files there. Yep it works! Thanks. I now have my primary wifi on 2.4ghz and 5ghz and one "guest wifi" using /usr/sbin/hostapd -P /var/run/hostapd.pid -B /etc/hostapd.conf /etc/hostapd2.conf /etc/hostapd3.conf rc.conf: wlans_ath0="wlan0" wlans_ath1="wlan1 wlan2" create_args_wlan0="wlanmode hostap" create_args_wlan1="wlanmode hostap" create_args_wlan2="wlanmode hostap" ifconfig_wlan0="channel 56 up" ifconfig_wlan1="channel 11 up" ifconfig_wlan2="channel 11 up" hostapd_enable="YES" * yes, you'll need >1 ssid on a radio, regardless .:) * yes, the atheros chips have one radio and one baseband, and our framework only supports it being in one channel AP mode at a time (ie, not switching between multple channels/bands.) smime.p7s Description: S/MIME Cryptographic Signature
Re: Multiple ssid or multiple radios with hostapd
On 01/06/15 16:53, Adrian Chadd wrote: Hi! It should be pretty simple: wlans_ath0="wlan0 wlan1" ifconfig_wlan0="create flags go here HOSTAP" ifconfig_wlan1="create flags go here HOSTAP" Then you populate /etc/hostapd-wlan0.conf and /etc/hostapd-wlan1.conf . Hm, this isn't well documented at all. Ok, time to update it. -adrian Thanks, this is what I did. (ie run two instances of hostapd). But is it possible to run just one? in the other case then, when I need two ssid on the same radio? This should be simple I guess? and finally a not so related question. I guess my radio (AR9300) cant runt 2.4 and 5ghz at the same time? On 6 January 2015 at 02:28, Peter Ankerstål wrote: Hi! Im trying to get hostapd to work with multiple wifi cards (and multiple ssid on a single card) but I cant get how to do it from the manual. And when searching the googlez I dont get much. Thanks. smime.p7s Description: S/MIME Cryptographic Signature
Multiple ssid or multiple radios with hostapd
Hi! Im trying to get hostapd to work with multiple wifi cards (and multiple ssid on a single card) but I cant get how to do it from the manual. And when searching the googlez I dont get much. Thanks. smime.p7s Description: S/MIME Cryptographic Signature
Re: iwn: firmware error
On 01/04/15 17:32, Adrian Chadd wrote: Hi! Which version of freebsd? Oops. FreeBSD mobius.uppmax.uu.se 10.1-RELEASE-p3 FreeBSD 10.1-RELEASE-p3 #14 r276407M: Tue Dec 30 13:32:05 CET 2014 smime.p7s Description: S/MIME Cryptographic Signature
iwn: firmware error
I have noticed a problem with the iwn firmware.
On the client side I have these settings:
wlan0: flags=8843 metric 0 mtu 1500
ether f0:de:f1:c9:14:4d
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11na
status: associated
ssid web channel 56 (5280 MHz 11a ht/40-) bssid 04:f0:21:01:3d:87
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
AES-CCM 3:128-bit txpower 14 bmiss 10 mcastrate 6 mgmtrate 6
scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
roam:rate 64 ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi
wme roaming MANUAL
wpa_conf:
---
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="web"
key_mgmt=WPA-PSK
psk=""
priority=1
---
It first associates but then after some traffic the card turns off with thse
messages:
iwn0: iwn_intr: fatal firmware error
firmware error log:
error type = "UNKNOWN" (0x2078)
program counter = 0x9758
source line = 0x063D
error data = 0x40008030E90F
branch link = 0x96CE96CE
interrupt link = 0xD6BE
time= 2154208510
driver status:
tx ring 0: qid=0 cur=66 queued=0
tx ring 1: qid=1 cur=0 queued=0
tx ring 2: qid=2 cur=0 queued=0
tx ring 3: qid=3 cur=8 queued=0
tx ring 4: qid=4 cur=161 queued=0
tx ring 5: qid=5 cur=0 queued=0
tx ring 6: qid=6 cur=0 queued=0
tx ring 7: qid=7 cur=0 queued=0
tx ring 8: qid=8 cur=0 queued=0
tx ring 9: qid=9 cur=0 queued=0
tx ring 10: qid=10 cur=65 queued=0
tx ring 11: qid=11 cur=0 queued=0
tx ring 12: qid=12 cur=0 queued=0
tx ring 13: qid=13 cur=0 queued=0
tx ring 14: qid=14 cur=0 queued=0
tx ring 15: qid=15 cur=0 queued=0
tx ring 16: qid=16 cur=0 queued=0
tx ring 17: qid=17 cur=0 queued=0
tx ring 18: qid=18 cur=0 queued=0
tx ring 19: qid=19 cur=0 queued=0
rx ring: cur=50
On the accesspoint I have:
wlan0: flags=8943 metric
0 mtu 1500
ether 04:f0:21:01:3d:87
nd6 options=29
media: IEEE 802.11 Wireless Ethernet autoselect mode 11na
status: running
ssid web channel 56 (5280 MHz 11a ht/40-) bssid 04:f0:21:01:3d:87
regdomain ETSI country SE ecm authmode WPA2/802.11i privacy MIXED
deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 24
mcastrate 6
mgmtrate 6 scanvalid 60 -ht ampdulimit 64k ampdudensity 8
shortgi wme
burst dtimperiod 1 -dfs
hostapd.conf:
---
interface=wlan0
driver=bsd
debug=0
logger_syslog=1
logger_syslog_level=0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
ssid=web
wpa=2
wpa_passphrase=
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
rsn_pairwise=CCMP
---
smime.p7s
Description: S/MIME Cryptographic Signature
Re: wpa_supplicant problem.
On 01/18/14 17:10, Adrian Chadd wrote: Ok. Compile the kernel with IWN_DEBUG, then sysctl dev.iwn.0.debug=0x1 (that enables TX debugging) and send over the log. Hi! Here's the log! Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 1 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 6 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 11 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 7 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 13 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 52 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 56 status 1 Jan 18 21:01:00 mobius kernel: iwn_notif_intr: scanning channel 60 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 64 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 36 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 40 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 44 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 48 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 2 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 3 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 4 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 5 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 8 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 9 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 10 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 12 status 1 Jan 18 21:01:01 mobius kernel: iwn_notif_intr: scanning channel 149 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 153 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 157 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 161 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 165 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 100 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 104 status 1 Jan 18 21:01:02 mobius kernel: iwn_notif_intr: scanning channel 108 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 112 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 116 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 120 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 124 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 128 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 132 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 136 status 1 Jan 18 21:01:03 mobius kernel: iwn_notif_intr: scanning channel 140 status 1 Jan 18 21:01:49 mobius wpa_supplicant[608]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="web" Jan 18 21:01:49 mobius wpa_supplicant[608]: wlan0: Trying to associate with 04:f0:21:01:3d:87 (SSID='web' freq=2452 MHz) Jan 18 21:01:49 mobius kernel: iwn_tx_data_raw: qid 3 idx 30 len 6 nsegs 1 Jan 18 21:01:49 mobius kernel: iwn5000_tx_done: qid 3 idx 30 retries 0 nkill 0 rate 420a duration 778 status 201 Jan 18 21:01:49 mobius kernel: iwn_tx_data_raw: qid 3 idx 31 len 84 nsegs 1 Jan 18 21:01:49 mobius kernel: iwn5000_tx_done: qid 3 idx 31 retries 0 nkill 0 rate 420a duration 1402 status 201 Jan 18 21:01:49 mobius kernel: wlan0: link state changed to UP Jan 18 21:01:49 mobius kernel: lagg0: link state changed to UP Jan 18 21:01:49 mobius kernel: received statistics without RSSI Jan 18 21:01:49 mobius wpa_supplicant[608]: wlan0: Associated with 04:f0:21:01:3d:87 Jan 18 21:01:49 mobius kernel: iwn_tx_data: qid 3 idx 32 len 129 nsegs 2 Jan 18 21:01:50 mobius kernel: iwn5000_tx_done: qid 3 idx 32 retries 16 nkill 0 rate 6904 duration 2330 status 83 Jan 18 21:01:50 mobius kernel: iwn_tx_data: qid 3 idx 33 len 129 nsegs 2 Jan 18 21:01:50 mobius kernel: iwn5000_tx_done: qid 3 idx 33 retries 16 nkill 0 rate 80006904 duration 2650 status 83 Jan 18 21:01:51 mobius kernel: iwn_tx_data: qid 3 idx 34 len 129 nsegs 2 Jan 18 21:01:51 mobius kernel: iwn5000_tx_done: qid 3 idx 34 retries 16 nkill 0 rate 80006904 duration 2650 status 83 Jan 18 21:01:52 mobius dhclient[1338]: send_packet: No buffer space available Jan 18 21:01:52 mobius kernel: iwn_tx_data: qid 3 idx 35 len 129 nsegs 2 Jan 18 21:01:53 mobius kernel: iwn5000_tx_done: qid 3 idx 35 retries 16 nkill 0 rate 80006904 duration 2650 status 83 Jan 18 21:01:53 mobius wpa_supplicant[608]: wlan0: CTRL-EVENT-DISCONNECTED bssid=04:f0:21:01:3d:87 reason=0 Jan 18 21:01:53 mobius wpa_supplicant[608]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Jan 18 21:01:53 mobius wpa_supplicant[608]: wl
Re: wpa_supplicant problem.
On 08 Jan 2014, at 18:46, Adrian Chadd wrote: > On 8 January 2014 00:31, Peter Ankerstål wrote: >> Hehe, >> >> I dont think Im ready for 11 yet. Do you think these fixes will be in 10 any >> time soon? > > I can try backporting the EAPOL fix(es) to HEAD but it may involve other > fixes. > > I'll take a look. Just as an experiment i tried in my own stupidity to “implement” your change in r257947 of if_iwn.c and just added the extra if statement, but at last that did not change anything. /Peter. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: wpa_supplicant problem.
On 08 Jan 2014, at 18:46, Adrian Chadd wrote: > On 8 January 2014 00:31, Peter Ankerstål wrote: >> Hehe, >> >> I dont think Im ready for 11 yet. Do you think these fixes will be in 10 any >> time soon? > > I can try backporting the EAPOL fix(es) to HEAD but it may involve other > fixes. > > I'll take a look. > Maybe you already knew this but I just realised that its only when the AP uses ht it fails. If I turn off ht it works perfectly for both 2.4 and 5ghz. /Peter. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: wpa_supplicant problem.
Hehe, I dont think Im ready for 11 yet. Do you think these fixes will be in 10 any time soon? On 01/08/2014 07:30 AM, Adrian Chadd wrote: Hm, sounds to me like something I fixed in -HEAD. Try -HEAD. The TL;DR - the EAPOL frames are going out at a much higher transmit rate than the initial association attempts, which means it associates fine but it can't authenticate successfully. Try running -HEAD. I bet it'll work. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: wpa_supplicant problem.
Ooops. Missed the important part of client messages. Also I have tried with
different pre-shared keys but it still don’t work.
wlan0: State: ASSOCIATING -> ASSOCIATED
wlan0: Associated to a new BSS: BSSID=04:f0:21:01:3d:87
wlan0: No keys have been configured - skip key clearing
wlan0: Associated with 04:f0:21:01:3d:87
wlan0: WPA: Association event - clear replay counter
wlan0: WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
wlan0: Setting authentication timeout: 10 sec 0 usec
wlan0: Cancelling scan request
wlan0: RX EAPOL from 04:f0:21:01:3d:87
wlan0: Setting authentication timeout: 10 sec 0 usec
wlan0: IEEE 802.1X RX: version=2 type=3 length=95
wlan0: EAPOL-Key type=2
wlan0: key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
wlan0: key_length=16 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 94 73 9c af a7 74 b0 22 b2 28 94 82 ac b2 63 13
e5 f1 96 d7 8e e1 61 15 e3 0c 7c 2d 4c 41 f1 d8
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
wlan0: State: ASSOCIATED -> 4WAY_HANDSHAKE
wlan0: WPA: RX message 1 of 4-Way Handshake from 04:f0:21:01:3d:87 (ver=2)
RSN: msg 1/4 key data - hexdump(len=0):
WPA: Renewed SNonce - hexdump(len=32): 89 be 5d 40 70 3f 59 27 34 ed 6d 31 0e
03 c5 41 b5 de cc 2d 9e 05 a0 b4 5b b8 ac 7a 46 bc 6a 79
WPA: PTK derivation - A1=f0:de:f1:c9:14:4d A2=04:f0:21:01:3d:87
WPA: Nonce1 - hexdump(len=32): 89 be 5d 40 70 3f 59 27 34 ed 6d 31 0e 03 c5 41
b5 de cc 2d 9e 05 a0 b4 5b b8 ac 7a 46 bc 6a 79
WPA: Nonce2 - hexdump(len=32): 94 73 9c af a7 74 b0 22 b2 28 94 82 ac b2 63 13
e5 f1 96 d7 8e e1 61 15 e3 0c 7c 2d 4c 41 f1 d8
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=48): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f
ac 04 01 00 00 0f ac 02 00 00
WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 01
wlan0: WPA: Sending EAPOL-Key 2/4
WPA: KCK - hexdump(len=16): [REMOVED]
WPA: Derived Key MIC - hexdump(len=16): c1 6a 85 5f fa 2c f2 b1 d8 25 bf ad 39
bf 71 b9
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
wlan0: Event DISASSOC (1) received
wlan0: Disassociation notification
wlan0: CTRL-EVENT-DISCONNECTED bssid=04:f0:21:01:3d:87 reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="web" auth_failures=1 duration=10
On 08 Jan 2014, at 00:00, Adrian Chadd wrote:
> hi,
>
> please retry with the only network block entries being:
>
> ssid=
> psk=
>
> .. and let wpa_supplicant figure it out.
>
>
> -a
>
>
> On 7 January 2014 13:07, Peter Ankerstål wrote:
>> Hi!
>>
>> Im trying to connect from a Lenovo X220 to my FreeBSD router running
>> hostapd. The router is supporting
>> a lot of other clients (OS X and iOS) without any problems. And my laptop
>> can connect to my phone when
>> I set it up as a hotspot.
>>
>> Lenovo X220:
>> FreeBSD lenny 10.0-RC2 FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 08:18:20 UTC
>> 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>>
>> iwn0@pci0:3:0:0:class=0x028000 card=0x13118086 chip=0x00858086
>> rev=0x34 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Centrino Advanced-N 6205 [Taylor Peak]'
>>class = network
>>
>> # cat /etc/wpa_supplicant.conf
>> ctrl_interface=/var/run/wpa_supplicant
>> eapol_version=2
>> ap_scan=1
>> fast_reauth=1
>>
>> network={
>>priority=100
>>proto=RSN WPA
>>ssid="web"
>>key_mgmt=WPA-PSK
>>pairwise=CCMP TKIP
>>group=CCMP TKIP
>>psk=“secret”
>> }
>>
>> Router:
>> FreeBSD gw 10.0-RC1 FreeBSD 10.0-RC1 #3 r259258: Thu Dec 12 16:21:37 CET
>> 2013 root@gw:/usr/obj/usr/src/sys/SOEKRIS i386
>>
>> ath0@pci0:7:0:0:class=0x028000 card=0x3114168c chip=0x0030168c
>> rev=0x01 hdr=0x00
>>vendor = 'Atheros Communications Inc.'
>>
Re: wpa_supplicant problem.
Hi!
Now I get on the router:
wlan0: STA f0:de:f1:c9:14:4d WPA: EAPOL-Key timeout
WPA: f0:de:f1:c9:14:4d WPA_PTK entering state PTKSTART
wlan0: STA f0:de:f1:c9:14:4d WPA: sending 1/4 msg of 4-Way Handshake
and on the client:
wlan0: Selecting BSS from priority group 0
wlan0: 0: 04:f0:21:01:3d:87 ssid='web' wpa_ie_len=0 rsn_ie_len=20 caps=0x31
level=-65
wlan0:selected based on RSN IE
wlan0:selected BSS 04:f0:21:01:3d:87 ssid='web'
wlan0: Request association: reassociate: 0 selected: 04:f0:21:01:3d:87 bssid:
00:00:00:00:00:00 pending: 00:00:00:00:00:00 wpa_state: SCANNING
wlan0: Trying to associate with 04:f0:21:01:3d:87 (SSID='web' freq=2412 MHz)
FT: Stored MDIE and FTIE from (Re)Association Response - hexdump(len=0):
wlan0: Cancelling scan request
wlan0: WPA: clearing own WPA/RSN IE
wlan0: Automatic auth_alg selection: 0x1
RSN: PMKSA cache search - network_ctx=0x0 try_opportunistic=0
RSN: Search for BSSID 04:f0:21:01:3d:87
RSN: No PMKSA cache entry found
wlan0: RSN: using IEEE 802.11i/D9.0
wlan0: WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 proto 2
wlan0: WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04
01 00 00 0f ac 02 00 00
wlan0: WPA: using GTK CCMP
wlan0: WPA: using PTK CCMP
wlan0: WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00
0f ac 04 01 00 00 0f ac 02 00 00
wlan0: No keys have been configured - skip key clearing
wlan0: State: SCANNING -> ASSOCIATING
Limit connection to BSSID 04:f0:21:01:3d:87 freq=2412 MHz based on scan results
(bssid_set=0)
wpa_driver_bsd_associate: ssid 'web' wpa ie len 22 pairwise 3 group 3 key mgmt 1
wpa_driver_bsd_set_drop_unencrypted: enabled=1
bsd_set_opt_ie: set WPA+RSN ie (len 22)
wpa_driver_bsd_associate: set PRIVACY 1
wlan0: Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RSN: Ignored PMKID candidate without preauth flag
wlan0: Event ASSOC (0) received
wlan0: State: ASSOCIATING -> ASSOCIATED
On 08 Jan 2014, at 00:00, Adrian Chadd wrote:
> hi,
>
> please retry with the only network block entries being:
>
> ssid=
> psk=
>
> .. and let wpa_supplicant figure it out.
>
>
> -a
>
>
> On 7 January 2014 13:07, Peter Ankerstål wrote:
>> Hi!
>>
>> Im trying to connect from a Lenovo X220 to my FreeBSD router running
>> hostapd. The router is supporting
>> a lot of other clients (OS X and iOS) without any problems. And my laptop
>> can connect to my phone when
>> I set it up as a hotspot.
>>
>> Lenovo X220:
>> FreeBSD lenny 10.0-RC2 FreeBSD 10.0-RC2 #0 r259404: Sun Dec 15 08:18:20 UTC
>> 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>>
>> iwn0@pci0:3:0:0:class=0x028000 card=0x13118086 chip=0x00858086
>> rev=0x34 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Centrino Advanced-N 6205 [Taylor Peak]'
>>class = network
>>
>> # cat /etc/wpa_supplicant.conf
>> ctrl_interface=/var/run/wpa_supplicant
>> eapol_version=2
>> ap_scan=1
>> fast_reauth=1
>>
>> network={
>>priority=100
>>proto=RSN WPA
>>ssid="web"
>>key_mgmt=WPA-PSK
>>pairwise=CCMP TKIP
>>group=CCMP TKIP
>>psk=“secret”
>> }
>>
>> Router:
>> FreeBSD gw 10.0-RC1 FreeBSD 10.0-RC1 #3 r259258: Thu Dec 12 16:21:37 CET
>> 2013 root@gw:/usr/obj/usr/src/sys/SOEKRIS i386
>>
>> ath0@pci0:7:0:0:class=0x028000 card=0x3114168c chip=0x0030168c
>> rev=0x01 hdr=0x00
>>vendor = 'Atheros Communications Inc.'
>>device = 'AR9300 Wireless LAN adaptor'
>>class = network
>>
>> # cat /etc/hostapd.conf
>> interface=wlan0
>> driver=bsd
>> debug=0
>> ctrl_interface=/var/run/hostapd
>> ctrl_interface_group=wheel
>> ssid=web
>> wpa=2
>> wpa_passphrase=secret
>> wpa_key_mgmt=WPA-PSK
>> wpa_pairwise=CCMP TKIP
>> rsn_pairwise=CCMP
>>
>>
>> debug output from wpa_supplicant.
>> # wpa_supplicant -D bsd -i wlan0 -d -c /etc/wpa_supplicant.conf
>> wpa_supplicant v2.0
>> Successfully initialized wpa_supplicant
>> Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'bsd'
>> ctrl_interface 'N/A' bridge 'N/A
Re: FYI: When trying to create new wlan1
Ah, finally. The problem seems to be that I used "mode 11a". Now everything seems to work. Thanks again! On Jun 18, 2013, at 8:59 PM, Adrian Chadd wrote: > Hi! > > If 11n is available, it will "upgrade" your AP interface to be 11n. > > Just do this: > > ifconfig -v wlan0 list chan > > If it shows 11n HT20 and HT40 channels, then it will just be upgraded. > > next, don't set + or - - some channels require HT40+ or HT40-. They're > not supposed to overlap! > > Just do: > > (whilst creating things) > ifconfig wlan0 channel 52:ht/40 > ifconfig wlan0 up > > On 18 June 2013 11:55, Peter Ankerstål wrote: >> Hey, >> >> Sorry about all these questions but I frustrated now. :D >> >> Im trying to get ht/40 but I don't seem to get it right. I now have it setup >> like this: >> >> gw# ifconfig ath0 >> ath0: flags=8843 metric 0 mtu 2290 >>ether 04:f0:21:01:3d:87 >>nd6 options=29 >>media: IEEE 802.11 Wireless Ethernet autoselect mode 11a >>status: running >> gw# ifconfig wlan0 >> wlan0: flags=8943 metric 0 >> mtu 1500 >>ether 04:f0:21:01:3d:87 >>inet6 fe80::6f0:21ff:fe01:3d87%wlan0 prefixlen 64 tentative scopeid >> 0xd >>nd6 options=29 >>media: IEEE 802.11 Wireless Ethernet autoselect mode 11a >>status: running >>ssid web channel 52 (5260 MHz 11a) bssid 04:f0:21:01:3d:87 >>regdomain ETSI country SE ecm authmode WPA2/802.11i privacy MIXED >>deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 24 mcastrate 6 >>mgmtrate 6 scanvalid 60 wme burst dtimperiod 1 -dfs >> >> gw# ifconfig wlan0 list sta >> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> 00:1f:5b:c7:5d:df1 52 54M 18.00 61 49264 EP AQP RSN WME >> e8:92:a4:78:31:622 52 54M 30.50 45249 57200 EP AQP RSN WME >> 58:55:ca:f3:8a:273 52 48M 29.00 40147 19440 EP AQ RSN WME >> >> all of these are N-capable. >> >> can't set ht/40: >> gw# ifconfig wlan0 channel 52:ht/40+ >> ifconfig: SIOCS80211: Invalid argument >> >> but at some point I got it to work yesterday and I don't know how I did it: >> ssid web channel 52 (5260 MHz 11a ht/40+) bssid 04:f0:21:01:3d:87 >> >> I don't really get why I can set ht/40+ sometimes but not always. >> >> Thanks for all code and help! (where can I send my donation? :D) >> >> /Peter. >> >> On Jun 18, 2013, at 4:40 PM, Adrian Chadd wrote: >> >>> HM! Please file a PR? >>> >>> >>> >>> >>> adrian >>> >>> On 18 June 2013 02:15, Peter Ankerstål wrote: >>>> Hi! >>>> >>>> Just for your information. (I dont need this). >>>> >>>> When I try to create a new virtual wlan interface I get this panic. >>>> >>>> gw# ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid ssid testar up >>>> >>>> >>>> >>>> Jun 18 10:56:47 gw kernel: >>>> Jun 18 10:56:47 gw kernel: >>>> Jun 18 10:56:47 gw kernel: Fatal trap 12: page fault while in kernel mode >>>> Jun 18 10:56:47 gw kernel: cpuid = 0; apic id = 00 >>>> Jun 18 10:56:47 gw kernel: fault virtual address= 0x0 >>>> Jun 18 10:56:47 gw kernel: fault code = supervisor read, page not >>>> present >>>> Jun 18 10:56:47 gw kernel: wlan1: Ethernet address: 06:f0:21:01:3d:87 >>>> Jun 18 10:56:47 gw kernel: instruction pointer = 0x20:0xc07fb620 >>>> Jun 18 10:56:47 gw kernel: stack pointer= 0x28:0xe8c129e0 >>>> Jun 18 10:56:47 gw kernel: frame pointer= 0x28:0xe8c129e8 >>>> Jun 18 10:56:47 gw kernel: code segment = base 0x0, limit 0xf, >>>> type 0x1b >>>> Jun 18 10:56:47 gw kernel: = DPL 0, pres 1, def32 1, gran 1 >>>> Jun 18 10:56:47 gw kernel: processor eflags = ath0: >>>> ath_edma_recv_proc_queue: handled npkts 0 >>>> Jun 18 10:56:47 gw kernel: interrupt enabled, >>>> Jun 18 10:56:47 gw kernel: resume, IOPL = 0 >>>> Jun 18 10:56:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts 0 >>>> Jun 18 10:58:53 gw syslogd: kernel boot file is /boot/kernel/kernel >>>> Jun 18 10:58:53 gw kernel: current process = 2744 (bsnmpd) >>>> Jun 18 10:58:53 gw kernel: ath0: ath_edma
Re: Support for Mini PCie card WLE300NX( (AR9380)
Seems I needed to take the interface down to change country. But.. Final question, Can I get any information about the MIMO operation? Is there sopport for three streams right now? /Peter On 06/18/2013 09:47 AM, Adrian Chadd wrote: If 11n is available, it'll negotiate it. adrian On 18 June 2013 00:46, Peter Ankerstål wrote: Oops. That did the trick. Thanks! But now I cant get it to work with 802.11an. First of all it seems locked in "country US" and setting :ht/40+ seems to have no effect. /Peter. On 06/17/2013 09:07 PM, Adrian Chadd wrote: Hm, do you have ATH_ENABLE_11N in your kernel config? adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Support for Mini PCie card WLE300NX( (AR9380)
Oops. That did the trick. Thanks! But now I cant get it to work with 802.11an. First of all it seems locked in "country US" and setting :ht/40+ seems to have no effect. /Peter. On 06/17/2013 09:07 PM, Adrian Chadd wrote: Hm, do you have ATH_ENABLE_11N in your kernel config? adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Support for Mini PCie card WLE300NX( (AR9380)
; > > On 14 June 2013 04:33, Peter Ankerstål wrote: >> On 02/16/2013 08:33 PM, Adrian Chadd wrote: >>> >>> Oops, I didn't reply in public! >>> >>> On 15 February 2013 09:03, Adrian Chadd wrote: >>>> >>>> Yup! I'm working on open sourcing the HAL side of things soon. >>> >>> >>> I'm going through final code approval now. >>> >>> Then, of course, there's all this extra work required to get it >>> somewhat validated - I have to write a bunch of testing routines to >>> test TX power, TX and RX EVM (to make sure that things aren't >>> distorting), fix up some of the shortcuts I've taken (eg making ANI >>> work right), implement MSI interrupt handling, test whether 3-stream >>> negotiation, TX and RX works correctly, make sure the STA timers are >>> setup right, make sure the hostap timers are setup right, implement >>> CABQ handling for hostap mode... >>> >>> .. yeah, there's still a lot of work to do. :-) >>> >>> But it's almost there. >>> >>> >>> >>> Adrian >>> >> >> Ooops. Just found: >> >> http://lists.freebsd.org/pipermail/freebsd-wireless/2013-May/003274.html >> >> Will I be able to use this in FreeBSD 9? > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Support for Mini PCie card WLE300NX( (AR9380)
On 02/16/2013 08:33 PM, Adrian Chadd wrote: Oops, I didn't reply in public! On 15 February 2013 09:03, Adrian Chadd wrote: Yup! I'm working on open sourcing the HAL side of things soon. I'm going through final code approval now. Then, of course, there's all this extra work required to get it somewhat validated - I have to write a bunch of testing routines to test TX power, TX and RX EVM (to make sure that things aren't distorting), fix up some of the shortcuts I've taken (eg making ANI work right), implement MSI interrupt handling, test whether 3-stream negotiation, TX and RX works correctly, make sure the STA timers are setup right, make sure the hostap timers are setup right, implement CABQ handling for hostap mode... .. yeah, there's still a lot of work to do. :-) But it's almost there. Adrian Ooops. Just found: http://lists.freebsd.org/pipermail/freebsd-wireless/2013-May/003274.html Will I be able to use this in FreeBSD 9? ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Support for Mini PCie card WLE300NX( (AR9380)
On 02/16/2013 08:33 PM, Adrian Chadd wrote: Oops, I didn't reply in public! On 15 February 2013 09:03, Adrian Chadd wrote: Yup! I'm working on open sourcing the HAL side of things soon. I'm going through final code approval now. Then, of course, there's all this extra work required to get it somewhat validated - I have to write a bunch of testing routines to test TX power, TX and RX EVM (to make sure that things aren't distorting), fix up some of the shortcuts I've taken (eg making ANI work right), implement MSI interrupt handling, test whether 3-stream negotiation, TX and RX works correctly, make sure the STA timers are setup right, make sure the hostap timers are setup right, implement CABQ handling for hostap mode... .. yeah, there's still a lot of work to do. :-) But it's almost there. Adrian Hey! Just wanted to check the status of this. Thanks! ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Support for Mini PCie card WLE300NX( (AR9380)
Hi! What is the current status for this card in -HEAD? Would it be usable in the near future? FreeBSD gw 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Thu Feb 7 11:31:17 CET 2013 root@gw:/usr/obj/usr/src/sys/SOEKRIS i386 none12@pci0:7:0:0: class=0x028000 card=0x3114168c chip=0x0030168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9300 Wireless LAN adaptor' class = network ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
