kern/88793: wlan(4) broken, sends corrupted packets with iwi(4) or ral(4)

Matthias Andree matthias.andree at
Thu Nov 10 06:50:25 PST 2005

>Number:         88793
>Category:       kern
>Synopsis:       wlan(4) broken, sends corrupted packets with iwi(4) or ral(4)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 10 14:50:23 GMT 2005
>Originator:     Matthias Andree
>Release:        FreeBSD 6.0-RELEASE i386
System: FreeBSD 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Mon Nov 7 16:10:51 CET 2005 toor at i386


the FreeBSD 6.0 WLAN stack or ral(4) driver appears to be broken.
After sending some amount of data, it starts sending out corrupted data,
including broken MAC, packet length and similar.

Soeren Schmidt confirmed a similar problem for iwi, so it may not be driver

See this thread for details, excerpts below

| I have an oldish computer VIA KT333/Athlon XP board (i386) that I
| recently upgraded from FreeBSD 5.4 (was rock solid) to 6.0-BETA3 and
| today to 6.0-RC1 (I rebuilt everything from scratch).
| I had to upgrade because there was no ral(4) driver for FreeBSD 5.4 but
| only for 6.0, which I needed after I had switched from 3C900 Combo
| (802.3 whatever 10Base2) to Edimax EW-7128g (802.11b/g). The latter card
| is based on RT2525 and RT2560 chips/modules. I'm using WPA-TKIP to
| connect it to an AVM Fritz!Box Fon WLAN.
| The computer is dual boot with SUSE Linux 9.3, where RA card is
| absolutely stable and does 48 Mbps without trouble.

And Soeren replied:

| Yes I see the same thing with iwi, it looses connection now and then.  Heavy
| traffic alone doesn't do it, but starting VNCviewer kills it  every time. A
| killall -1 wpa_supplicant gets the connection back on  track...  Other end here
| is a Dlink DI624+ so the mix is totally different from  yours...





More information about the freebsd-bugs mailing list