Sam Leffler <sam@freebsd.org> wrote:

quoted text
> This could be because wme is now enabled by default; if it's on try=20
> turning it off.

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