Date: Wed, 30 Apr 2008 09:04:01 -0700 From: Sam Leffler <sam@freebsd.org> To: Fabian Keil <fk@fabiankeil.de> Cc: freebsd-current@freebsd.org Subject: Re: Connection problems with wme enabled Message-ID: <48189871.2060005@freebsd.org> In-Reply-To: <48189577.4080109@freebsd.org> References: <6b8e8f4f0804291900v521cde5cw1ad4eaba70244e9c@mail.gmail.com> <4817E52F.5070806@freebsd.org> <20080430121014.209beb00@fabiankeil.de> <48189577.4080109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Sam Leffler wrote:
> 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
>
> Fabian Keil wrote:
>> Sam Leffler <sam@freebsd.org> wrote:
>>
>>
>>> This could be because wme is now enabled by default; if it's on try
>>> 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="wlan0"
>> ifconfig_wlan0="inet 192.168.0.49 ssid ... wepkey 1:... deftxkey 1
>> wepmode 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=0x028000 card=0x27128086
>> chip=0x42208086 rev=0x05 hdr=0x00
>> vendor = 'Intel Corporation'
>> device = 'MPCI3B driverIntel PRO/Wireless 2200BG'
>> class = network
>>
>> With the access point Netgear WGT 624 v3.
>>
>> Fabian
>>
>
> _______________________________________________
> 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"
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48189871.2060005>