NetMetal5 mANT30 NV2 low CCQ and no connection on 802.11

RouterOS Wireless Networking
1

We have 2 mANT30 with NetMetal5 connected and can only establish a connection with NV2. The link is 33km with the signal at -68 and -74. Noise floor is -104 and signal to noise is 39 but the CCQ is 2/2%. We’ve tried 20Mhz wide channels on N and 20,40, and 80 Mhz on AC all with the same result. I have NV2 tdma set to 2 and distance at 36km.

AP

/interface bridge
add name=bridge1
/interface wireless
set [ find default-name=wlan1 ] antenna-gain=30 band=5ghz-onlyac channel-width=20/40/80mhz-eeCe country="united states" disabled=no distance=36 frequency=5300 frequency-mode=superchannel hide-ssid=yes l2mtu=1600 mode=ap-bridge nv2-cell-radius=36 nv2-preshared-key=password rx-chains=0,1 tx-chains=0,1 wireless-protocol=nv2
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=password
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan1
/ip address
add address=172.16.2.4/29 interface=bridge1 network=172.16.2.0
/ip route
add distance=1 gateway=172.16.2.1
add distance=1 dst-address=172.16.2.32/27 gateway=172.16.2.2
add distance=1 dst-address=172.16.3.0/24 gateway=172.16.2.2
/system identity
set name=Mikrotik
/system leds
set 1 interface=wlan1
/system routerboard settings
set cpu-frequency=720MHz

Client

/interface bridge
add name=bridge1
/interface wireless
set [ find default-name=wlan1 ] antenna-gain=30 band=5ghz-onlyac channel-width=20/40/80mhz-eeCe country="united states" disabled=no frequency=auto frequency-mode=superchannel l2mtu=1600 nv2-preshared-key=password rx-chains=0,1 ssid=Mikrotik tx-chains=0,1 wireless-protocol=nv2
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys wpa2-pre-shared-key=password
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan1
/ip address
add address=172.16.2.3/29 interface=bridge1 network=172.16.2.0
/ip route
add distance=1 gateway=172.16.2.1
/system leds
set 1 interface=wlan1
/system routerboard settings
set cpu-frequency=720MHz
2

You need to realign the antenna. Same hapened to me but I moved it left to right a lot until the signal was good. The antenna has lobes and you align them on that lobes. Also the signal must be identical ±3dbi. The link must have ~ -60dbi.

3

We actually had it at -53 before we raised it up on the pole. There’s a palm tree in the way. At -53 it still wouldn’t connect even at 20Mhz AC or N.

4

Client didn’t have a mode set up, try station-bridge

5

I think is easier to set wireless debug and check the log. But with 2% ccq I wouldn’t bother.

6

Yeah; when I wasn’t using NV2 I kept getting disconnect messages in the log.

07:10:50 wireless,info @wlan1 established connection on 5300000, SSID
07:10:53 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:10:53 wireless,info @wlan1 established connection on 5300000, SSID
07:10:56 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:10:57 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:11:09 wireless,info @wlan1 established connection on 5300000, SSID
07:11:12 wireless,info @wlan1: lost connection, extensive data loss
07:11:12 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:11:24 wireless,info @wlan1 established connection on 5300000, SSID
07:11:27 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:11:28 wireless,info @wlan1 established connection on 5300000, SSID
07:11:31 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:11:31 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:11:43 wireless,info @wlan1 established connection on 5300000, SSID
07:11:46 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:11:46 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:11:58 wireless,info @wlan1 established connection on 5300000, SSID
07:12:01 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:12:02 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:12:14 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:12:26 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:12:38 wireless,info @wlan1 established connection on 5300000, SSID
07:12:41 wireless,info @wlan1: lost connection, received deauth: unspecified (1)
07:12:41 wireless,info @wlan1 established connection on 5300000, SSID
07:12:44 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:12:44 wireless,info @wlan1 established connection on 5300000, SSID
07:12:48 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:12:48 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:13:00 wireless,info @wlan1 established connection on 5300000, SSID
07:13:03 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:13:03 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:13:15 wireless,info @wlan1 established connection on 5300000, SSID
07:13:18 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:13:19 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:13:31 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:13:43 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:13:55 wireless,info @wlan1 established connection on 5300000, SSID
07:13:58 wireless,info @wlan1: lost connection, extensive data loss
07:13:58 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:14:10 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:14:22 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:14:34 wireless,info @wlan1 established connection on 5300000, SSID
07:14:37 wireless,info @wlan1: lost connection, received deauth: class 2 frame received (6)
07:14:37 wireless,info @wlan1: failed to connect, on 5300/20/ac, association failed: unspecified (1)
07:14:50 wireless,info @wlan1 established connection on 5300000, SSID
07:14:53 wireless,info @wlan1: lost connection, extensive data loss

7



This might be the reason. NV2 is able to keep the connection.

8

This parameter is wrong :

distance=36

This is not in km and represents the ack timeout value. Leave it on dynamic and try again. This parameter is used only on 802.11 protocol. That is why you have connection on nv2 because it uses the nv2-cell-radius parameter which is in km. But an ack-timeout value of 36 means less than 1km, basically close to indoor.

9

I removed the distance setting and CCQ is still 2%.

10

:laughing:

11

After a few days of aligning I now have the signal at -48. My connection says -52 and -53 with NV2 and the CCQ is now 6/2. NetMetal5 with mANT30 and their flex-guide and still no connection.

12

Please read my post again. Don’t remove the setting set it like this :

distance=dynamic

Also please note the following :

ACK Hardware limits are:

40MHz - 15.2 miles (24.5 km)
30MHz - 32.5 miles (52.3km)
20MHz - 32.5 miles (52.3km)
10MHz - 65.2 miles (104.9 km)
8MHz - 65.2 miles (104.9 km)
5MHz - 130.9 miles (210.7 km)

So if you use 802.11 on such a long link on more than 20Mhz channel width it will just not work. This is a protocol limitation. Just use NV2 or try nstreme.
On NV2 don’t watch the ccq value until you have some traffic running on that link. It stays low when no traffic passes, don’t ask me why.

13

Setting the distance to dynamic had no change. NV2 is the only one it will connect with but not even ping with work. CCQ is as low as 2 and as high as 10. Set AP to 20Mhz channels and 80Mhz with no difference.

14

I got it to connect with nstreme and the CCQ is now 66/70 but it still won’t ping. No traffic across the link.

15

Changing the client mode to station-bridge fixed it! I wasn’t able to get more then 30Mb with Nstreme even though the ping times are shorter. Switching to NV2 I got 400Mb. Thanks everyone!

16

He put mode=Station and put interfaces in bridge and took him 7 days at least to realised he didn’t read basic ROS manual that says :

Mode station
This is standard mode that does not support L2 bridging on station - attempts to put wireless interface in bridge will not produce expected results

Mode station-bridge
This mode works only with RouterOS APs and provides support for transparent protocol-independent L2 bridging on station device. RouterOS AP accepts clients in station-bridge mode when enabled using bridge-mode parameter

:laughing: :laughing: :laughing:

17

InoX

Shows how much you know or didn’t you bother with reading my posted config.

jrudrow was actually the one who caught it and CyberTod interpreted the low CCQ was due to no traffic.

Maybe YOU should concentrate on posting useful information instead of sounding like a babbling moron.

18

In your config, operation mode for the station is missing. Only for AP.



So you are the moron.
Thank you anyway for the compliment.

And this is how an wireless interface config should be:

/interface wireless> print
Flags: X - disabled, R - running
0 R name=“wlan1” mtu=1500 mac-address=D4:CA:6D:94:77:94 arp=enabled
interface-type=Atheros AR9300 mode=station-bridge ssid=“B_Mosneni”
frequency=5180 band=5ghz-a/n channel-width=20/40mhz-Ce 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

19

It’s not missing; its default which won’t show in the config. Haven’t you ever read or programmed these?

20

No. It’s my first time. I’m so lucky you teached me.

Read what? Routerboards?
Since today I will read Routerboards NetMetal5 every day. :laughing: