I’m interested if anyone run into this issue:
Wireless card stops transmission (counter stable stays on 0), but receiving works.
If i disable/enable the wireless card, datas flow again.
It happened with:
RB411AH, ROS5.18 and 5.22 (this board reboots with kernel failure as well, few times a day)
AP mode, MIMO, 20mhz, nv2, a dozen of clients. Now ping watchdog set to one of the clients
The following are in P2P setup
RB433AH(with mikrotik card) and MetalTik. one with 5.16 other with 5.18
nv2 as well
I have no ideas what can cause this, and what can fix. Nor of other APs (yet) did this.
I would even welcome and idea for script this thing.
The problem with your 411 might be related to power supply issues. The remaining problems could be down to a shaky installation. If you are certain that it’s not hardware related, then it’s might be worth upgrading the software on each device to the same version. You might also run a quick check to detect if there are no rogue DHCP servers on your network.
You could set up a script which will check for 20 seconds if there is any tx trafic. If no trafic for 20 seconds then restart the interface. However you should nail down the problem instead of trying to find a workaround.
Ohara: right.
finding the problem is more important than finding a workaround.
What i tought is make a script what check the tx packets five to ten times in a row (between few second diff). Log them all, and if sum is 0, than disable/enable.
Maybe you have better idea?
Power supply is a UBNT Toughswitch 5port. 2 or 3 other devices on it, and works well. The other devices are same 411AH or 711.
The kernel problem might be power or hardware issue. If you don’t want to take down the RB then you might erase the config and set up again or try to disable other devices on you poe switch and see if it makes a difference.
As per wireless disconnects, did you get a response fron support? I have seen some other threads about the same issue recently and it is certainly about nv2 and ptmp, unless you have observed it in ptp.
Ohara: there are 3 pcs of 411AH on the toughswitch. It can provider 5x12W
i think, 411AH + wireless does not eats more than 8-10W
The support responded to replace/re-netinstall.
I also can confirm it’s an NV2 issue. It’s just happened on another AP what has 3 wlan cards. 2 of 3 are nstreme, p2p
the 3rd one (what stopped) running NV2 multipoint. That AP is running since 72 days.
@wpeople: Personally I am not facing such issues on our end, but I experienced them some time ago. Here is a simple script that should reset the interface when there is no traffic for 10 seconds. It’s a workaround and it does not resolve the problem though. Feel free to test it.
@beeski: do you have a similar script which you could possibly share?
watchdog forces reboot, who wants to loose the connectivity for 45 secs + watchdog period when the script could do it far quicker.
However, a good explanation of the script would be useful to us all and I cant wait to start using it (as soon as I fully understand ALL the parameters)
When I was facing the problem, it was enough to re-enable the wireless interface on any CPE unit. Thereafter the traffic on all other CPE’s would be restored. Theoretically it would be enough to launch the script from task scheduler on a CPE, but I don’t know if the current issues are similar to mine. I have added comments to explain the script:
# variable for intervals
:local i 0
# variable for traffic
:local txrx 0
# name of the wireless interface
:local iface "wlan1"
# check if interface exists, otherwise don't continue
:if ([:len [/interface find name=$iface]] > 0) do={
# check if connection is running, otherwise don't continue
:while ([/interface get [find name=$iface] running]=true) do={
# we will do 10 snapshots of the network traffic
:if ($i<10) do={
# each time we do a snapshot, we increment the counter
:set i ($i+1)
# snapshots are done in 1 second intervals
:delay 1
# take traffic snapshot and increment txrx variable by current bps
# to validate TX only replace line with :set txrx ($txrx+$("tx-bits-per-second"))
/interface monitor-traffic $iface once do={
:set txrx ($txrx+$("tx-bits-per-second")+$("rx-bits-per-second"))
}
# print information in the log window, this line can be removed to keep the logs clean
:log info ($i . " - txrx: " . $txrx)
# execute this part of script after 10 snapshots
} else {
# if the sum of all 10 traffic snapshots is 0 then disable and enable interface
:if ($txrx=0) do={
:log warning "Resetting interface"
/interface disable [/interface find name=$iface]
/interface enable [/interface find name=$iface]
}
# stop the script
stop
}
}
}
Script is installed, but the wireless card is up for 5days 2hrs (411AH, running ROS 5.22).
What is strange, the longest uptime client (5days 2hrs) is a non N client.
the rest are:
1d 17h
17h24m
1h37m
1h24m
1h8m
1h3m
52m
22m
20m
16m
On AP side: control frame timeout logged
on client: lost connection, medium-access timeout
maybe 5.23 not 4.23
as you see above, in the first times, my AP was rebooted (or stopped) with 5.22 - and now working well since 6d3h (thas is a longest uptime client, since ap reboot).
So it should be now hardware problem.
Since the ROS 5.23 (rc) is not public and sent us within a week, i cannot tell you that is a solution.
What IS a well working workaround: set watchdog to your uplink router IP ANDinstall one of the scripts above. That will reboot the AP if got stucks, and restart wireless if it stops.