login
Search
Hi, I am trying to build an access point out of a Soekris 4801 - I have built two images from the CURRENT source, one on March 28, 2008 (pre-VAPS) and one from today April 29th, 2008. The 3/28 one works beautifully, the 4/29 one has authorization problems. I converted the rc.conf to the new wlan_* things. Is there something wrong with my configurations? thanks, dave c good old config, kernel & world built march 28th sources. === rc.conf === hostname="ap1.dogwood.com" hostapd_enable="YES" ifconfig_sis0="up" ifconfig_sis1="up" ifconfig_sis2="up" ifconfig_ath0="mode 11a mediaopt hostap dturbo" cloned_interfaces="bridge0" ifconfig_bridge0="ether 92:74:fd:88:12:f3 addm sis0 addm sis1 addm sis2 addm ath0 stp sis0 stp sis1 stp sis2 stp ath0 DHCP" ntpdate_enable="YES" ntpdate_flags="pool.ntp.org" sendmail_enable="NONE" sshd_enable="YES" syslogd_flags="-ss" rwhod_enable="YES" smartd_enable="YES" ntpd_enable="YES" === hostapd.conf interface=ath0 driver=bsd logger_syslog=-1 logger_syslog_level=0 logger_stdout=-1 logger_stdout_level=0 debug=4 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=hoana-a wpa=1 wpa_passphrase=v1g1lance wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP === log output Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d IEEE 802.11: associated Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: event 1 notification Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: start authentication Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d IEEE 802.1X: unauthorizing port Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: sending 1/4 msg of 4-Way Handshake Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: received EAPOL-Key frame (2/4 Pairwise) Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: sending 3/4 msg of 4-Way Handshake Apr 29 15:22:37 ap1 hostapd: ath0: STA 00:13:e8:30:a7:6d WPA: received EAPOL-Key ...
Please show the output of ifconfig -v wlan0 and the mac+phy revs of the ath card. I also need to know what hal you're using. This could be because wme is now enabled by default; if it's on try turning it off. Sam _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Maybe this would be worth mentioning in /usr/src/UPDATING.
Since rebuilding world last weekend, I had connection
problems with iwi0. Under load it would be associated
for less than 10 seconds after which I had to run
"ifconfig wlan0 down up" to get a connection again.
Running the above ifconfig line in a delayed loop
would more or less work for about 30 minutes after
which if_iwi.ko had to be reloaded to get it working
again.
Disabling wme for wlan0 seems to have solved the problem.
My rc.conf used to be:
vaps_iwi0=3D"wlan0"
ifconfig_wlan0=3D"inet 192.168.0.49 ssid ... wepkey 1:... deftxkey 1 wepmod=
e on chanlist 7 bmiss 100 -bgscan country de regdomain indoor"
(Not touching the bmiss and bgscan settings didn't
seem to affect the problem.)
I'm using:
fk@TP51 ~ $pciconf -lv | grep -A 4 iwi0
iwi0@pci0:2:2:0: class=3D0x028000 card=3D0x27128086 chip=3D0x4220808=
6 rev=3D0x05 hdr=3D0x00
vendor =3D 'Intel Corporation'
device =3D 'MPCI3B driverIntel PRO/Wireless 2200BG'
class =3D network
With the access point Netgear WGT 624 v3.
Fabian
The default configuration of iwi did not change; only ath. I don't see
any information to show the cause of your "connection problems" so
there's no way to guess what's going on.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Actually, I take it back. WME did get enabled for all drivers by
default now and I'll look to switch that back. What I was thinking of
was that I fixed an issue with ath where WME+TKIP did not work and
because of that enabled WME use for all ath parts.
It would still be worth understanding why WME operation breaks iwi;
please provide logs showing what is happening.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Where would I get meaningful logs?
dmesg doesn't show any relevant messages,
even when booted in verbose mode.
The ifconfig output looks normal (to me) as well:
fk@TP51 ~ $sudo ifconfig -v wlan0
wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15=
00
ether 00:0e:...
inet 192.168.0.49 netmask 0xffffff00 broadcast 192.168.0.255
media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
status: associated
ssid ... channel 7 (2442 Mhz 11g) bssid 00:14:...
regdomain DEBUG country DE anywhere -ecm authmode OPEN -wps -tsn
privacy ON deftxkey 1
wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 30
txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 24
11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11na ucast NONE mgmt 0 MCS mcast 0 MCS maxretry 6
11ng ucast NONE mgmt 0 MCS mcast 0 MCS maxretry 6
scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
roam:11b rssi 7dBm rate 1 Mb/s
roam:11g rssi 7dBm rate 5 Mb/s -pureg protmode CTS -ht
-htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi
htprotmode RTSCTS -puren wme -burst -ff -dturbo -dwds roaming AUTO
bintval 100
AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack
cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm
AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack
cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm
AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack
cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm
AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack
cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm
groups: wlan=20
While it shows association, open connections stall and
I can't create new ones until reviving the device ...man wlandebug. If the 802.11-related activity doesn't show you what you
want then try driver-level debugging. This should be controlled through
wlanstats 1 gives you a rolling display every second; that's usually
more helpful in understanding what's happening. Unfortunately there are
more stats than can fit on a rolling display so sometimes the one(s) you
want aren't shown. There is a column fmt mechanism a la ps to control
output but it's not well developed (someone please take and improve).
Also some stats are maintained by drivers and not yet counted in the
iwi does tx rate control in the firmware so unlikely to be related. The
more likely issue is the beacon miss handling. The driver should
recover and reconnect but it sounds like something didn't work. As a
workaround you can try upping the bmiss count to see if this is a
problem w/ the radio going deaf for a period of time--something I've
See above. I ran tests yesterday w/ wme enabled in my environment but
the signal was stronger so not an equivalent test. What you need to do
is get a log that captures the event of losing connectivity. This must
include net80211 logging and probably needs to include some level of
driver debugging as the problem is in the driver. Try:
wlandebug state+scan+auth+assoc
sysctl debug.iwi=5
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
While working:
fk@TP51 ~ $wlanstats 1
input 2short rx_ucast bvers wrbss rxdup mecho wrdir
14 0 14 0 1 29861 54 0
19 0 19 0 0 0 0 0
7 0 7 0 0 0 0 0
15 0 15 0 0 0 0 0
14 0 14 0 0 0 0 0
4 0 4 0 0 0 0 0
1 0 1 0 0 0 0 0
1 0 1 0 0 0 0 0
1 0 1 0 0 0 0 0
3 0 3 0 0 0 0 0
2 0 2 0 0 0 0 0
2 0 2 0 0 0 0 0
2 0 2 0 0 0 0 0
3 0 3 0 0 0 0 0
2 0 2 0 0 0 0 0
0 0 0 0 0 0 0 0
3 0 3 0 0 0 0 0
2 0 2 0 0 0 0 0
0 0 0 0 0 0 0 0
1 0 1 0 0 0 0 0
1 0 1 0 0 0 0 0
^C
While "hanging" ...
fk@TP51 ~ $wlanstats 1
input 2short rx_ucast bvers wrbss rxdup mecho wrdir
882 0 831 0 1 29859 50 0
1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
1 0 0 0 0 0 0 0
0 0 ...Well if your beacon interval is 100 TU then the default setting of 24
means you didn't see a beacon frame in 2400 TU (~2.4 seconds) which is a
really long time even if the channel is way busy. The firmware handles
this notification so it could be a firmware issue; if I were
investigating I'd sniff packets to see.
I've tested bmiss handling before (yesterday even) and it worked for me
w/ and w/o wme enabled so not sure what to say. What I have noticed is
the firmware some times delivers a slew of beacon miss notifications
immediately after associating to an ap. I have some ideas why this
might occur but Intel wouldn't answer when asked. However if you're
seeing bmiss after lots of traffic has passed then it's unclear what's
happening.
Looks like I failed to include IEEE80211_DEBUG in the default kernel
configs; you'll need that to get wlan debug msgs. I'll try to look at
your log later.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Indeed.
While "hanging":
fk@TP51 ~ $wlanstats 1
input mgmt output rxkid ascan bgscn bmiss rssi noise rate
113 591 207 0 10 0 3 42 0 54M
0 0 2 0 0 0 0 42 0 54M
0 0 1 0 0 0 0 42 0 54M
0 0 2 0 0 0 0 42 0 54M
0 0 2 0 0 0 0 42 0 54M
0 1 1 0 0 0 0 42 0 54M
0 0 1 0 0 0 0 42 0 54M
0 0 2 0 0 0 0 42 0 54M
0 0 1 0 0 0 0 42 0 54M
0 0 2 0 0 0 0 42 0 54M
1 1 3 0 0 0 0 43 0 54M
0 0 1 0 0 0 0 43 0 54M
0 0 2 0 0 0 0 43 0 54M
0 0 2 0 0 0 0 43 0 54M
0 0 2 0 0 0 0 43 0 54M
0 1 3 0 0 0 0 42 0 54M
0 0 1 0 0 0 0 42 0 54M
0 0 2 0 0 0 0 42 0 54M
^C
While working with wme enabled:
7 0 7 0 0 0 0 42 0 2M
4 0 4 0 0 0 0 42 0 11M
10 0 6 0 0 0 0 42 0 11M
5 0 4 0 0 0 0 43 0 12M
5 1 3 0 0 0 0 43 0 12M
3 0 4 0 0 0 0 43 0 18M
3 0 3 0 0 0 0 43 0 18M
4 0 3 0 0 0 0 43 0 18M
3 0 2 0 0 0 0 43 ...from dmesg:
ath0: mac 5.9 phy 4.3 radio 3.6
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[root@ap2] 111% ifconfig -v wlan0
wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 2290
ether 00:0b:6b:34:65:99
media: IEEE 802.11 Wireless Ethernet autoselect mode 11a <hostap>
status: running
ssid hmiln channel 52 (5260 Mhz 11a) bssid 00:0b:6b:34:65:99
regdomain DEBUG country US anywhere ecm authmode WPA -wps -tsn
privacy MIXED deftxkey 2
TKIP 2:128-bit
TKIP 3:128-bit powersavemode OFF powersavesleep 100 txpower 19
txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7
11a ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6
11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6
turboA ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6
11na ucast NONE mgmt 0 MCS mcast 0 MCS maxretry 6
11ng ucast NONE mgmt 0 MCS mcast 0 MCS maxretry 6
scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
roam:11a rssi 7dBm rate 12 Mb/s
roam:11b rssi 7dBm rate 1 Mb/s
roam:11g rssi 7dBm rate 5 Mb/s
roam:turboA rssi 7dBm rate 12 Mb/s
roam:sturbo rssi 7dBm rate 12 Mb/s -pureg protmode CTS -ht
-htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi
htprotmode RTSCTS -puren -wme burst ff dturbo -dwds -hidessid apbridge
dtimperiod 1 doth dfs inact bintval 100
groups: wlan
I disabled WME and it behaves a little different:
[root@ap2] 115% ifconfig wlan0 list sta
ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG
00:13:e8:30:a7:6d 1 52 54M 25.0 0 5 10624 EP AQP WPA WME
But the client (Win XP) can't get an address from the DHCP server, and
if I set a static address on the client still nothing. ...Are you certain hostapd is up to date? There was a bug like this a
while back (before code was committed to CVS) when I failed to update
hostapd to plumb keys correctly. I routinely test this same config
(i.e. card) w/o any issues.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
recompiled everything from todays sources, [win xp connection attempt] wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 wlan0: ieee80211_crypto_setkey: TKIP keyix 4 flags 0x3 mac 00:13:e8:30:a7:6d rsc 0 tsc 0 len 16 wlan0: ieee80211_crypto_setkey: TKIP keyix 4 flags 0x3 mac 00:13:e8:30:a7:6d rsc 0 tsc 0 len 16 wlan0: _ieee80211_crypto_delkey: TKIP keyix 4 flags 0x3 rsc 0 tsc 2 len 16 wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 wlan0: [00:0b:6b:34:65:99] discard frame due to countermeasures (tkip_encap) [ repeat this a couple hundred times ] wlan0: [00:0b:6b:34:65:99] discard frame due to countermeasures (tkip_encap) wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 wlan0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 wlan0: ieee80211_crypto_setkey: TKIP keyix 4 flags 0x3 mac 00:13:e8:30:a7:6d rsc 0 tsc 0 len 16 [win xp thinks it's connected, but no DHCP] I'm wondering if it's not an interaction problem with if_bridge? I'll try a simpler config... thanks, dave c _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
What you show are PTK's being plumbed but the issue I asked about was for the GTK and you haven't shown the log of it being plumbed. You also don't show the Michael failure msg so I cannot tell what key was involved. Please collect a full log and either send it privately or give me a url. You might also look at the scripts in tools/tools/net80211/scripts for examples of how I setup working configurations of various flavors. Sam _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
ok, i am building a new kernel with some trepidation. will the following work in the new way of things? wlans_ath0="wlan0 wlan1" cloned_interfaces=bridge0 ifconfig_bridge0="192.168.0.1 addm vr1 addm vr2 addm vr3 addm wlan0 addm wlan1 up" ipv6_ifconfig_bridge0="inet6 2001:666:42::1/64" ifconfig_vr1=up ifconfig_vr2=up ifconfig_vr3=up ifconfig_wlan0="channel 11 ssid rgnet-crypt wep wepkey thirteenchars weptxkey 1 mediaopt hostap up" ifconfig_wlan1="channel 4 ssid rg-open mediaopt hostap up" randy _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
with the following:
wlans_ath0="wlan0"
cloned_interfaces=bridge0
ifconfig_bridge0="192.168.0.1 addm vr1 addm vr2 addm vr3 addm wlan0 up"
ipv6_ifconfig_bridge0="inet6 2001:240:6a8::1/64"
ifconfig_vr1=up
ifconfig_vr2=up
ifconfig_vr3=up
ifconfig_wlan0="channel 11 ssid rgnet-aden wep wepkey thirteenchars
weptxkey 1 mediaopt hostap up"
i am not seeing carrier on wlan0 and i am not seeing the access point
from local hosts.
randy
# ifconfig ath0
ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric
0 mtu 2290
ether 00:0b:6b:83:59:25
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
# ifconfig wlan0
wlan0:
flags=8d43<UP,BROADCAST,RUNNING,PROMISC,OACTIVE,SIMPLEX,MULTICAST>
metric 0 mtu 1500
ether 00:0b:6b:83:59:25
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid rgnet-aden channel 11 (2462 Mhz 11g)
country US ecm authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit
txpower 19 bmiss 7 scanvalid 60 bgscan bgscanintvl 300
bgscanidle 250
roam:rssi 7 roam:rate 5 protmode CTS wme burst ff dturbo bintval 0
# athstats
4537885 data frames received
1016560 data frames transmit
1934 mib overflow interrupts
0M current transmit rate
1016560 tx frames with no ack marked
1280120 rx failed 'cuz of bad CRC
2192058 rx failed 'cuz frame too short
54659 rx failed 'cuz of PHY err
7152 transmit override receive
2 OFDM restart
47505 CCK restart
6 rssi of last ack
1 switched default/rx antenna
Antenna profile:
[1] tx 1016558 rx 4537884
[2] tx 0 rx 1
-30-
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Note that it says "autoselect" instead of "hostap". AFAIK, you have to specify a media and a mode before you specify a mediaopt. Try "media autoselect mode 11g mediaopt hostap" instead of just "mediaopt hostap". DES -- Dag-Erling Smørgrav - des@des.no _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
The operating mode of a vap is immutable; it must be set when it's
created by cloning the underlying ifnet. I believe there are usage
examples in all the wireless driver man pages. The scripts in
src/tools/tools/net80211/scripts
also demonstrate how to setup various configurations.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
indeed. it is the mapping to /etc/rc.conf which is hurting me. randy _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I'm able to reproduce this now; will fix this weekend.
Sam
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I've had a chance to rebuild and all works well now, thanks Sam! dave c _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
