Hello,
has anybody problem with nv2 and client freeze? We have problem to use nv2 on some our APs, bacause of client freeze. If we disable and enable wireless, client is suddenly ok. ROS v is 6.18, new wireless package enabled, ROS is the same on AP and client. If we use nstreme, no freezes at all, but we want to use nv2 because we have better throuput and latency …
Does anybody have a solution for theese?
Thank you.
please describe your freezing detection methodics.
please describe your freezing detection methodics.[/quote]
It is simple, our customer calls, that internet is not working … everything what we do, is disable and enable him on AP and everything is than ok. This is not happening if there is nstreme or simple 802.11, only NV2 do this …
what wireless hardware are you using?
Please make sure that you also upgrade the Routboard firmware to the latest version.
What wireless configuration you are using.
Try to reset the wireless interface configuration to the default settings and then report back.
Wireless almost everywhere RB52Hn, or RB52, and APs are RB433AH or RB433L. Yes we do upgrade firmware also too, always with the upgrade of ROS.
Where should I reset configuration on AP or on client?
Please give the details of the specific CPE device that is having problems and the AP.
I have same problem. RB750. After upgrade to 6.18 version winbox stop working. C++ runtime error.
CPE is mostly SXT or RB711 or RB911, i upgraded yesterday one site to 6.18 and customer also to 6.18 with newest firmware, so far so good … will report later …
So from your post I understand that you upgraded both sides (AP and CPE) to v6.18 and that solved the problem.
OK today same problem,
AP: RB433AH
/interface wireless print
name=“wlan1” mtu=1500 mac-address=XXXXXXXX arp=enabled interface-type=Atheros AR92xx mode=ap-bridge ssid=“XXXX” frequency=5680 band=5ghz-a/n channel-width=20mhz scan-list=default
wireless-protocol=nv2 vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=no default-forwarding=no default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default compression=no
CPE: 911-5HnD
/interface wireless print
0 R name=“wlan1-gateway” mtu=1500 mac-address=XXXXXXXXX arp=enabled interface-type=Atheros AR9300 mode=station ssid=“XXXX” frequency=5680 band=5ghz-a/n channel-width=20mhz scan-list=default
wireless-protocol=any vlan-mode=no-tag vlan-id=1 wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 hide-ssid=no security-profile=default compression=no
both newest firmware and ros …
on AP there are some other customers with older ros (6.15) but i dont think that is the problem …
asimko, please contact support@mikrotik.com so we could get support output files from the time when that happens and maybe access your devices remotely.
Mostly a defective WLAN client or on client with bad fluctuating signal makes this trouble.
Typ to find the bad station and change it.
Hello everyone, i have this same problem.
I use Omnitiks v6.31 and SXT v6.31, the problem persist.
What’s the problem?
Thanks everyone.