In/Out errors :(
-
Now tried IPCOP using the same wifi card and everything works perfect 0/0 errors.
I'll be waiting for a future version with a better wifi driver, pfsense is just better than ipcop. -
Now tried IPCOP using the same wifi card and everything works perfect 0/0 errors.
I'll be waiting for a future version with a better wifi driver, pfsense is just better than ipcop.Try FreeBSD and submit a bug report to the respective list. This will help it get attention. Simply waiting will result in no action and you just hope that someone happens to fix whatever issue there is.
PS: 99% of the time the errors are caused by the antenna setting. Make sure it using the right antenna.
-
Now tried IPCOP using the same wifi card and everything works perfect 0/0 errors.
I'll be waiting for a future version with a better wifi driver, pfsense is just better than ipcop.Try FreeBSD and submit a bug report to the respective list. This will help it get attention. Simply waiting will result in no action and you just hope that someone happens to fix whatever issue there is.
PS: 99% of the time the errors are caused by the antenna setting. Make sure it using the right antenna.
I am having in/out errors on a Atheros 5212 based PCI card. Here is athstats
athstats
80321 tx management frames
1232 tx frames discarded prior to association
2 tx stopped 'cuz no xmit buffer
900 tx failed 'cuz FIFO underrun
24742 tx failed 'cuz bogus xmit rate
1138 tx frames with rts enabled
79321 tx frames with an alternate rate
5242 tx frames with 11g protection
151167 rx failed 'cuz of FIFO overrun
1 rx failed 'cuz frame too short
58247 rx management frames
51043 beacon setup failed 'cuz no mbuf
195044131 beacons transmitted
219 periodic calibration failures
1307 tx used alternate antenna
Antenna profile:
[2] tx 38946 rx 40764
[3] tx 41701 rx 36158I am trying to change the antenna settings, but it does not allow me to change it. Actually the rxantenna changes between 1 and 2 every so often:
sysctl dev.ath.0
dev.ath.0.%desc: Atheros 5212
dev.ath.0.%driver: ath
dev.ath.0.%location: slot=8 function=0
dev.ath.0.%pnpinfo: vendor=0x168c device=0x001a subvendor=0x1113 subdevice=0xee24 class=0x020000
dev.ath.0.%parent: pci1
dev.ath.0.smoothing_rate: 95
dev.ath.0.sample_rate: 10
dev.ath.0.countrycode: 0
dev.ath.0.regdomain: 96
dev.ath.0.slottime: 9
dev.ath.0.acktimeout: 23
dev.ath.0.ctstimeout: 23
dev.ath.0.softled: 0
dev.ath.0.ledpin: 0
dev.ath.0.ledon: 0
dev.ath.0.ledidle: 2700
dev.ath.0.txantenna: 0
dev.ath.0.rxantenna: 1
dev.ath.0.diversity: 0
dev.ath.0.txintrperiod: 5
dev.ath.0.diag: 0
dev.ath.0.tpscale: 0
dev.ath.0.tpc: 0
dev.ath.0.tpack: 63
dev.ath.0.tpcts: 63
dev.ath.0.monpass: 24sysctl dev.ath.0
dev.ath.0.%desc: Atheros 5212
dev.ath.0.%driver: ath
dev.ath.0.%location: slot=8 function=0
dev.ath.0.%pnpinfo: vendor=0x168c device=0x001a subvendor=0x1113 subdevice=0xee24 class=0x020000
dev.ath.0.%parent: pci1
dev.ath.0.smoothing_rate: 95
dev.ath.0.sample_rate: 10
dev.ath.0.countrycode: 0
dev.ath.0.regdomain: 96
dev.ath.0.slottime: 9
dev.ath.0.acktimeout: 23
dev.ath.0.ctstimeout: 23
dev.ath.0.softled: 0
dev.ath.0.ledpin: 0
dev.ath.0.ledon: 0
dev.ath.0.ledidle: 2700
dev.ath.0.txantenna: 0
dev.ath.0.rxantenna: 2
dev.ath.0.diversity: 0
dev.ath.0.txintrperiod: 5
dev.ath.0.diag: 0
dev.ath.0.tpscale: 0
dev.ath.0.tpc: 0
dev.ath.0.tpack: 63
dev.ath.0.tpcts: 63
dev.ath.0.monpass: 24When I try to change the antenna to 0, it keeps changing back to 1 and 2. Any help is greatly appreciated.
-
I'm curious, change your rxbug and txbuf to 2000 instead of 40 and 100 by default.
sysctl hw.ath
hw.ath.hal.version: 0.9.17.2
hw.ath.hal.dma_brt: 2
hw.ath.hal.sw_brt: 10
hw.ath.hal.swba_backoff: 0
hw.ath.dwell: 200
hw.ath.calibrate: 30
hw.ath.outdoor: 1
hw.ath.xchanmode: 1
hw.ath.countrycode: 0
hw.ath.regdomain: 0
hw.ath.rxbuf: 4000
hw.ath.txbuf: 4000 -
I try that tonight. Will let you know the results. Thanks
-
Hey GoldServe
How do I change the values? When I do sysctl hw.ath.txbuf=2000 it says
sysctl: oid 'hw.ath.txbuf' is read only
Same for the rxbuf
-
Thanks GoldServe
I added "hw.ath.txbuf=3000" and "hw.ath.rxbuf=6000" on loader.conf and almost no In/Out Errors. And the WiFi is rock solid. Thanks again.
-
Eh?? Please test for a while and report back. This is very interesting.
-
Eh?? Please test for a while and report back. This is very interesting.
Wifi is still working solid. No random disconnections.
In the last 24 hours I have only 180740/0 In/Out errors. Before the change, this number was at least 10 times larger.
Lets see if this works permanently.
-
The errors are creeping up again. Here is the latest athstat with rxbuf and txbuf at 3000 and 6000 respectively
athstats
9269 tx management frames
275 tx frames discarded prior to association
262 tx failed 'cuz FIFO underrun
2121 tx failed 'cuz bogus xmit rate
1754 tx frames with rts enabled
7519 tx frames with an alternate rate
212 tx frames with 11g protection
483679 rx failed 'cuz of FIFO overrun
2 rx failed 'cuz frame too short
4119 rx management frames
113640 beacon setup failed 'cuz no mbuf
614465541 beacons transmitted
410 periodic calibration failures
75 tx used alternate antenna
Antenna profile:
[2] tx 5749 rx 4174
[3] tx 3530 rx 2081Any suggestions? Also, the dev.ath.0.rxantenna keeps switching from 1 to 2 and back?
-
neonsigns, could you post your config file (sysctl)… or at least a section of it with wifi settings you did
i tried g and a, different settings from this thread and still getting tons of in/out errors (btw, "a" mode produces less of'em :-) -
sysctl hw.ath
hw.ath.hal.swba_backoff: 0
hw.ath.hal.sw_brt: 10
hw.ath.hal.dma_brt: 2
hw.ath.hal.version: 0.9.17.2
hw.ath.txbuf: 3000
hw.ath.rxbuf: 6000
hw.ath.regdomain: 0
hw.ath.countrycode: 0
hw.ath.xchanmode: 1
hw.ath.outdoor: 1
hw.ath.calibrate: 30
hw.ath.dwell: 200sysctl dev.ath.0
dev.ath.0.%desc: Atheros 5212
dev.ath.0.%driver: ath
dev.ath.0.%location: slot=8 function=0
dev.ath.0.%pnpinfo: vendor=0x168c device=0x001a subvendor=0x1113 subdevice=0xee24 class=0x020000
dev.ath.0.%parent: pci1
dev.ath.0.smoothing_rate: 95
dev.ath.0.sample_rate: 10
dev.ath.0.countrycode: 0
dev.ath.0.regdomain: 96
dev.ath.0.slottime: 9
dev.ath.0.acktimeout: 48
dev.ath.0.ctstimeout: 48
dev.ath.0.softled: 0
dev.ath.0.ledpin: 0
dev.ath.0.ledon: 0
dev.ath.0.ledidle: 2700
dev.ath.0.txantenna: 0
dev.ath.0.rxantenna: 1
dev.ath.0.diversity: 0
dev.ath.0.txintrperiod: 5
dev.ath.0.diag: 0
dev.ath.0.tpscale: 0
dev.ath.0.tpc: 0
dev.ath.0.tpack: 63
dev.ath.0.tpcts: 63
dev.ath.0.monpass: 24athstats
10033 tx management frames
522 tx frames discarded prior to association
498 tx failed 'cuz FIFO underrun
3071 tx failed 'cuz bogus xmit rate
2491 tx frames with rts enabled
7547 tx frames with an alternate rate
212 tx frames with 11g protection
1084420 rx failed 'cuz of FIFO overrun
3 rx failed 'cuz frame too short
4277 rx management frames
266364 beacon setup failed 'cuz no mbuf
1822425091 beacons transmitted
932 periodic calibration failures
77 tx used alternate antenna
Antenna profile:
[2] tx 6512 rx 4668
[3] tx 3542 rx 2093ifconfig -v ath0
ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500
inet6 fe80::213:f7ff:fe1f:bffb%ath0 prefixlen 64 scopeid 0x2
ether 00:13:f7:1f:bf:fb
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
ssid NWIFI channel 11 (2462) bssid xx:xx:xx:xx:xx:xx
authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3
TKIP 2:128-bit
TKIP 3:128-bit powersavemode OFF powersavesleep 100 txpowmax 33
txpower 63 rtsthreshold 2346 mcastrate 1 fragthreshold 2346 bmiss 7
pureg protmode OFF -wme burst ssid SHOW apbridge dtimperiod 1
bintval 100 -countermeasures</hostap></up,broadcast,running,promisc,simplex,multicast> -
can you please try by forcing the media manually?
-
I have read somewhere that in freebsd, you can disable te bgscan via ifconfig ath0 -bgscan but it's not available in 6.2. Maybe someone can port over 6.3 and see if this helps.
-
I've the same problem about tons of IN/OUT errors. I also have a wifi card based on Atheros 5212.
I've been trying pfSense with the new txbuf and rxbuf and disconnections happen 8-9 hours later the first association instead of every 2 hours as usually occurs without that change in /boot/loader.conf
In my case those parameters in loader.conf make less OUT errors and few IN errors, but unluckily it doesn't solve the problem. Disconnections shouldn't occur due to the short distance between pfSense wifi antenna and client one.
It has been a year wifi connection have disconnection every 2-3 hours :(
As I've said, today wifi connection lasted 9 hours and then disconnection. I bet it will get disconnected with 9 hours from now.
I tought about a problem with hostapd, but now I think that is more driver related.
Moreover, I've two configurations and all of them have wifi cards based on Atheros chipset from different producers: I have the same problem reported in this thread with them. :-\What can we do? My wifi cards aren't faulty and I think yours, too. How can we report this problem to the maintainer of FreeBSD wireless drivers? Developers, we need your help! ::)
-
Hi neonsigns and all,your /boot/loader.conf looks like this ?
autoboot_delay="1"
kern.ipc.nmbclusters="0"
"hw.ath.rxbuf=6000"
"hw.ath.txbuf=3000" -
Hi neonsigns and all,your /boot/loader.conf looks like this ?
Not exactly. Be aware with system files!
autoboot_delay="1"
kern.ipc.nmbclusters="0"
hw.ath.rxbuf="6000"
hw.ath.txbuf="3000"…or without "
-
hey guys!
why would i have my in errors skyrocketing and our errors stay at the same level?
see attach…
tnx
-
@ermal:
can you please try by forcing the media manually?
ermal, how do I do that?
My loader.conf does not have kern.ipc.nmbclusters="0". What does this setting do?
-
[20070116, update 20070212] Systems with very heavy network activity have been observed to have some problems with the kernel memory allocator. Symptoms are processes that get stuck in zonelimit state, or system livelocks. One partial workaround for this problem is to add the following line to /boot/loader.conf and reboot:
kern.ipc.nmbclusters="0"
Setting this to 0 removes the max limit on allocating nmbclusters, this can be a problem if you have very large amounts of connections and not a lot of memory, So use it with caution.