Mikrotik AC PtP - Nstreme will NOT connect at all but NV2 will???

The site is pushing 50mb/s at night, and I usually like to have 2-3x the capacity. We upgraded to AirFiber5X a few days ago and got it to 170mb Down/ 30Mb Upload.

Did you see the problem only with the radios in ac mode, or with any radio that has ac support (even if it was configured only to use ‘n’)? Wondering about this since it appears Mikrotik have discontinued many of the non-ac variants of their products recently so there will soon be no option to not have an ac-capable radio (and it would be nice of they still worked as well as the older units for long-range PtP using Nstreme).

Thanks.

Well we are using nstreme everywhere on our network, AC and N hardware, SXT’s, Netmetals, OmniTik’s and DynaDishes without any problems. 6.33.3 and 6.33.5.

Please, post configs for Dynadish5 ot both sides?

Interesting. I turned up a new 17km p2p link yesterday using Mikrotik ac hardware (Netbox5 HP) and I am seeing much the same results as other posters here in that nstreme does not work hardly at all (station associates for a while but disconnects once traffic is passing). NV2 works reasonably well. Running 6.34.

Hey Folks (wispwest),

Found your thread searching for the same issue. 6.34, QRT5 on both sides with a link of about 500ft. (and yes, the power was/is turned down to 8db)

The link would only associate in NV2, but with only 50Mbs throughput. Downgraded to 6.25 and then saw this in the wireless logs:

wlan1: 4C:5E:0C:80:BA:80 not acceptable for security profile: requires privacy, but profile does not allow
wlan1: failed to select network

So we took a stab in the dark and configured and enabled a security profile with WPA2, and it linked right up with 100Mbs Throughput. We havent upgraded back to 6.34 to test if it stays, just need it up at this time. But my suggestion is to use a non-default security profile.

Good Luck!

Interesting. (I’m not wispwest but I have the same problem). I do have a security profile configured. Curiously, I was able to get nstreme working eventually. I’m not sure if enabling the security profile fixed it (I think it was always configured, but I’m not 100% sure – the link evaluation was done late at night). I took the link down today to work on the mounting arrangements on one end, so will test some more once it is up again.

If you could post the exact specifications of your security profile, it’d be useful (e.g. static keys/dynamic keys; eas or tkip, etc).

Thanks.

I couldn’t help but notice one of the radios had default-authenticate=no and I couldn’t see any mention of access or connect lists.

If this is correct and no connect or access list then you won’t get a connection :slight_smile:

Please double check - hope this helps…

[edit] a closer look and I saw an access list so as long as it matches the client radio it should be ok.

AP config:

/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk,wpa2-eap management-protection=allowed
mode=dynamic-keys name=NPP supplicant-identity=“” wpa2-pre-shared-key=\


/interface wireless
set [ find default-name=wlan1 ] band=5ghz-a/n default-authentication=no
disabled=no frequency=5530 ht-supported-mcs=“mcs-0,mcs-1,mcs-2,mcs-3,mcs-4
,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11,mcs-12,mcs-13,mcs-14,mcs-15,m
cs-16,mcs-17,mcs-18,mcs-19” max-station-count=2 mode=ap-bridge
nv2-cell-radius=10 nv2-qos=frame-priority radio-name=AP_Sdrujenie
rate-set=configured scan-list=5530 security-profile=NPP ssid=Sdrujenie
tdma-period-size=1 wireless-protocol=nv2-nstreme-802.11
/interface wireless nstreme
set wlan1 enable-nstreme=yes framer-policy=best-fit
/interface wireless access-list
add interface=wlan1 mac-address=4C:5E:0C:57:17:13 vlan-mode=no-tag

Client Config:
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk,wpa2-eap management-protection=allowed
mode=dynamic-keys name=NPP supplicant-identity=“” wpa2-pre-shared-key=\


/interface wireless
set [ find default-name=wlan1 ] band=5ghz-a/n disabled=no frequency=5530
mode=station-bridge radio-name=Client_Sdrujenie scan-list=5530
security-profile=NPP ssid=Sdrujenie wireless-protocol=nv2-nstreme-802.11
/interface wireless nstreme
set wlan1 enable-nstreme=yes

Just spotted the access list among the many lines [emoji41]

Access list is OK.

mac-address=4C:5E:0C:57:17:13 interface=wlan1 signal-range=-120..120 authentication=yes
forwarding=yes ap-tx-limit=0 client-tx-limit=0 private-algo=none private-key=“”
private-pre-shared-key=“” management-protection-key=“” vlan-mode=no-tag vlan-id=1

Now link is connected in NV2.
AP accept only devices in access list. (default-authentication=no)

Thats about the only thing I didn’t try, was enabling security on it. Too late now, as I already switched to AF5X, but I’ll keep that in mind next time Nstreme doesn’t link on AC!

Followup on my post in this thread:

I was able to get Nstreme to work. I’m not sure why it didn’t when I first tested. One thing I noticed, after enabling verbose logging for wireless is that the client may be checking each and every AP it can “see” to decide whether to connect or not. In my location there are a very large number of APs that are visible. So one theory is that the station can spend a bunch of time wondering which one to connect to. This can be confused with “not connecting at all”, unless you know to wait long enough. I have also seen the station disconnect and reconnect in the first minute or so after initial contact. Finally, I have seen some big differences between 802.11, Nstreme and NV2 regarding the threshold for making a connection vs interference/packet loss. Given the right environment of noise and interference it could be that one will connect when the others won’t.

Anyway, after much time testing and experimenting, I found that I get higher throughput with Nstreme than NV2 on my 17Km P2P link. I don’t ever see UDP throughput higher than about 0.4x the modulation rate (e.g. if the radios are connected at “120Mbit/s”, I see about 50Mbit/s throughput half-duplex). I’m not sure if that’s the best I can expect.

I have p2p Link with netmetal(921UAGS-5SHPacT) and mant 30. but link disconnect when nstreme enabled. so when i read this posts i understand that using nstreme on AC mode is wrong. am I true ? what should i do ? while using nv2 on links there is no disconnection problem but bad latency and throughput on the links.

there might be interference from airport. There are some radars operating near 5ghz band
we are experiencing same problems sometimes =) but link does not goes direct over airfield, lets say its 3km aside and parrallel to the airport, but
during night we have 650mbps both, day time-operational drops to 390-520 or kind of =) but we have military one nearby.. not for civilian

I have been trying to temporarily switch wireless protocol’s from NV2 N to Nstreme or 802.11 so that a virtual AP can used to change registered CPE’s SSID details?
But no matter what setting i use Nstreme or 802.11 will not connect? - using superchannel - ROS 6.44, 6.47.6, - any suggestions!

/interface wireless security-profiles
set [ find default=yes ] group-ciphers=“” supplicant-identity=MikroTik
unicast-ciphers=“”
add authentication-types=wpa-psk,wpa2-psk eap-methods=“” group-key-update=15m
mode=dynamic-keys name=Security supplicant-identity=“”
/interface wireless
set [ find default-name=wlan1 ] band=5ghz-onlyn basic-rates-a/g=
6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps default-forwarding=no
disabled=no disconnect-timeout=10s distance=15 frequency=5260
frequency-mode=superchannel ht-basic-mcs=
mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11
ht-supported-mcs=
mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7,mcs-8,mcs-9,mcs-10,mcs-11
hw-protection-mode=rts-cts keepalive-frames=disabled mode=ap-bridge
multicast-buffering=disabled nv2-cell-radius=20 nv2-downlink-ratio=80
nv2-qos=frame-priority nv2-queue-count=8 nv2-security=enabled
on-fail-retry-time=300ms radio-name=XXXXXX rate-set=configured
rx-chains=0,1 security-profile=Security ssid=XXXXXX tx-chains=0,1
wireless-protocol=nv2 wmm-support=enabled
/interface wireless nstreme
set wlan1 disable-csma=yes enable-polling=no framer-policy=dynamic-size

Client side should have this set to

wireless-protocol=nv2-nstreme-802.11

This will allow client to follow changes on AP side.

All the Clients have wireless-protocol=nv2-nstreme-802.11 and still no wireless registration?

Check if clients (and AP) have WPA and WPA2 preshared keys defined and are the same. NV2 uses separate setting nv2-preshared-key= under /interface wireless while standard 802.11 and nstreme use settings from /interface wireless security-profiles (I’m not entirely sure about nstreme).

AP Wireless security-profile

/interface wireless security-profiles
set [ find default=yes ] group-ciphers="" supplicant-identity=MikroTik unicast-ciphers=""
add authentication-types=wpa-psk,wpa2-psk eap-methods="" group-key-update=15m mode=dynamic-keys name=Security supplicant-identity=""

Client Wireless security-profile

/interface wireless security-profiles
set [ find default=yes ] group-ciphers="" group-key-update=15m \
    supplicant-identity=MikroTik unicast-ciphers=""
add authentication-types=wpa-psk,wpa2-psk group-key-update=15m mode=\
    dynamic-keys name=Security supplicant-identity=""

Since wireless security profiles definitions incude authentication-types=wpa-psk,wpa2-psk, they should be including definition of PSK used, something like

wpa-pre-shared-key=TopSecret wpa2-pre-shared-key=TopSecret

And that’s both on AP and clients.