Bug 156327 - [bwn] bwn driver causes 20%-50% packet loss
Summary: [bwn] bwn driver causes 20%-50% packet loss
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 8.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-11 06:10 UTC by Yuri Gorchakov
Modified: 2018-05-28 19:43 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Gorchakov 2011-04-11 06:10:11 UTC
Dell Vostro 3500 with Broadcom BCM4312 (as siba reports) accessing AP with WPA-PSK encryption enabled. AP is 2m away from notebook,directly visible. 

Loaded modules: 
if_bwn.ko 
siba_bwn.ko 
wlan.ko 
wlan_amrr.ko 
wlan_wep.ko 
wlan_ccmp.ko 
wlan_tkip.ko 
bwn_v4_lp_ucode.ko. 

Within first 1-2 mins after boot I get "bwn0: RX decryption attempted (old 0 keyidx 0x2)" errors at tty0. Pinging access point with 1000 packages gives 20% to 50% packet loss.

Loading Ubuntu LiveCD at the same conditions and installing offered 802.11 Linux STA driver gives 0% packet loss.

How-To-Repeat: grep -E "wlan|bwn" /boot/loader.conf 
wlan_load="YES"
wlan_wep_load="YES"
wlan_ccmp_load="YES"
wlan_tkip_load="YES"
wlan_amrr_load="YES"
if_bwn_load="YES"
siba_bwn_load="YES"
bwn_v4_lp_ucode_load="YES"

grep -E "wlan|bwn" /etc/rc.conf
ifconfig_wlan0="WPA DHCP"
wlans_bwn0="wlan0"

cat /etc/wpa_supplicant.conf 
network={
	ssid="ittomsk.ru"
	psk="******"
}

ping 192.168.0.1 (AP address)
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2011-04-11 12:50:45 UTC
Responsible Changed
From-To: freebsd-amd64->freebsd-wireless

Over to maintainer(s).
Comment 2 cafedjian.g 2012-07-14 13:37:17 UTC
The BCM4312 doesn't support 802.11n created by default. You juste have to
switch mode to 802.11b when creating virtual interface.

FIX:
#ifconfig wlan create wlandev bwn0 mode 11b
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:43:09 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.