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_at_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_at_TP51 ~ $pciconf -lv | grep -A 4 iwi0 > iwi0_at_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 >Received on Wed Apr 30 2008 - 13:51:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:30 UTC