Buenas noches, tengo un ptp de 42km con dos NetMetal 5 dual chain(6.15) la señal que se detecta desde el cliente es de -54, la configuracion y mensajes de log son:

AP1

name="wlan1" mtu=1500 mac-address=4C:5E:0C:85:C0:5C arp=enabled disable-running-check=no
interface-type=Atheros AR9888 radio-name="4C5E0C85C05C" mode=ap-bridge ssid="WCBackaul"
area="" frequency-mode=superchannel country=no_country_set antenna-gain=0 frequency=5420
band=5ghz-onlyac channel-width=20mhz scan-list=default wireless-protocol=any rate-set=default
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps
basic-rates-a/g=6Mbps max-station-count=2007 distance=42 tx-power-mode=default dfs-mode=none
vlan-mode=no-tag vlan-id=1 wds-mode=static-mesh wds-default-bridge=bridge1
wds-default-cost=100 wds-cost-range=50-150 wds-ignore-ssid=yes update-stats-interval=disabled
bridge-mode=enabled default-authentication=yes default-forwarding=yes default-ap-tx-limit=0
default-client-tx-limit=0 proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no
security-profile=default disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both
compression=no allow-sharedkey=no station-bridge-clone-mac=00:00:00:00:00:00
ampdu-priorities=0 guard-interval=any
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,mcs-16,mcs-17,mcs-18,mcs-19,mcs-20,mcs-21,mcs-22,mcs-23
ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7
vht-supported-mcs=mcs0-9,mcs0-9,mcs0-9 vht-basic-mcs=mcs0-7 tx-chains=0 rx-chains=0
amsdu-limit=8192 amsdu-threshold=8192 tdma-period-size=2 nv2-queue-count=2 nv2-qos=default
nv2-cell-radius=30 nv2-security=disabled nv2-preshared-key="" hw-retries=8 frame-lifetime=0
adaptive-noise-immunity=none hw-fragmentation-threshold=disabled hw-protection-mode=none
hw-protection-threshold=0 frequency-offset=0 rate-selection=advanced multicast-helper=default
multicast-buffering=enabled


00:31:15 wireless,info 4C:5E:0C:85:C2:84@wlan1: connected, is AP, wants WDS
00:31:19 wireless,info 4C:5E:0C:85:C2:84@wlan1: disconnected, extensive data loss
00:31:19 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:19 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:19 wireless,info 4C:5E:0C:85:C2:84@wlan1: connected, is AP, wants WDS
00:31:22 wireless,info 4C:5E:0C:85:C2:84@wlan1: disconnected, received deauth: cla
ss 2 frame received (6)
00:31:23 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:23 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:23 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:23 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:31 wireless,info 4C:5E:0C:85:C2:84@wlan1: connected, is AP, wants WDS
00:31:35 wireless,info 4C:5E:0C:85:C2:84@wlan1: disconnected, received deauth: cla
ss 2 frame received (6)
00:31:35 wireless,info 4C:5E:0C:85:C2:84@wlan1: connected, is AP, wants WDS
00:31:38 wireless,info 4C:5E:0C:85:C2:84@wlan1: disconnected, extensive data loss
00:31:38 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C2:84, sent dea
uth
00:31:39 wireless,info 4C:5E:0C:85:C2:84@wlan1: connected, is AP, wants WDS
00:31:41 wireless,info 4C:5E:0C:85:C2:84@wlan1: disconnected, received deauth: res
erved (0)

AP2

name="wlan1" mtu=1500 mac-address=4C:5E:0C:85:C2:84 arp=enabled disable-running-check=no
interface-type=Atheros AR9888 radio-name="4C5E0C85C284" mode=ap-bridge ssid="WCBackaul" area=""
frequency-mode=superchannel country=no_country_set antenna-gain=0 frequency=5420 band=5ghz-onlyac
channel-width=20mhz scan-list=default,5400-5500 wireless-protocol=any rate-set=default
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-a/g=6Mbps
max-station-count=2007 distance=42 tx-power-mode=default dfs-mode=none vlan-mode=no-tag vlan-id=1
wds-mode=static-mesh wds-default-bridge=bridge2 wds-default-cost=100 wds-cost-range=50-150
wds-ignore-ssid=yes update-stats-interval=disabled bridge-mode=enabled default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0
proprietary-extensions=post-2.9.25 wmm-support=disabled hide-ssid=no security-profile=default
disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no allow-sharedkey=no
station-bridge-clone-mac=00:00:00:00:00:00 ampdu-priorities=0 guard-interval=any
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,mcs-16,mcs-17,mcs-18,mcs-19,mcs-20,mcs-21,mcs-22,mcs-23
ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-4,mcs-5,mcs-6,mcs-7 vht-supported-mcs=mcs0-9,mcs0-9,mcs0-9
vht-basic-mcs=mcs0-7 tx-chains=0,1 rx-chains=0,1 amsdu-limit=8192 amsdu-threshold=8192
tdma-period-size=auto nv2-queue-count=2 nv2-qos=default nv2-cell-radius=30 nv2-security=disabled
nv2-preshared-key="" hw-retries=8 frame-lifetime=0 adaptive-noise-immunity=none
hw-fragmentation-threshold=disabled hw-protection-mode=cts-to-self hw-protection-threshold=0
frequency-offset=0 rate-selection=advanced multicast-helper=default multicast-buffering=enabled

00:31:08 wireless,info 4C:5E:0C:85:C0:5C@wlan1: connected, is AP, wants WDS
00:31:11 wireless,info 4C:5E:0C:85:C0:5C@wlan1: disconnected, extensive data loss
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:11 wireless,info 4C:5E:0C:85:C0:5C@wlan1: connected, is AP, wants WDS
00:31:11 wireless,info 4C:5E:0C:85:C0:5C@wlan1: disconnected, received deauth: class 2 frame received (6)
00:31:20 wireless,info 4C:5E:0C:85:C0:5C@wlan1: connected, is AP, wants WDS
00:31:23 wireless,info 4C:5E:0C:85:C0:5C@wlan1: disconnected, extensive data loss
00:31:24 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:24 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:24 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:24 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:24 wireless,info wlan1: data from unknown device 4C:5E:0C:85:C0:5C, sent deauth
00:31:24 wireless,info 4C:5E:0C:85:C0:5C@wlan1: connected, is AP, wants WDS
00:31:27 wireless,info 4C:5E:0C:85:C0:5C@wlan1: disconnected, received deauth: class 2 frame received (6)
00:31:27 wireless,info 4C:5E:0C:85:C0:5C@wlan1: connected, is AP, wants WDS

Que puede pasar?

Un saludo

English please
Then can we help you

Good evening, I have a ptp 42km NetMetal 5 with two dual chain (6.15) the signal is detected from the client is -54, the configuration and log messages are:


That can happen?

Post :

Post :

Code: Select all

/interface wireless registration-table print stats

interface=wlan1 radio-name="4C5E0C85C05C" mac-address=4C:5E:0C:85:C0:5C ap=yes
wds=yes bridge=no rx-rate="6Mbps" tx-rate="6Mbps" packets=5,1 bytes=399,151
frames=5,1 frame-bytes=369,145 hw-frames=558,1 hw-frame-bytes=94302,169
tx-frames-timed-out=0 uptime=3s last-activity=2s770ms
signal-strength=-52dBm@6Mbps signal-to-noise=52dB signal-strength-ch0=-52dBm
signal-strength-ch1=-93dBm
strength-at-rates=-52dBm@6Mbps 0ms,-52dBm@9Mbps 2s520ms,-52dBm@12Mbps 2s630ms
p-throughput=5535 nstreme=no framing-mode=none routeros-version="6.15"
802.1x-port-enabled=yes management-protection=no compression=no
wmm-enabled=yes tx-rate-set="OFDM:6-54 BW:1x SGI:1x HT:0-7 VHTMCS:SS1=0-9"

the problem may be signal-strength-ch1=-93dBm . pigtatil one may be bad.

First thing I notice is that you have -93dBm signal on ch1. Is this a single polarity antenna ?
The next problem is you are using 802.11 which will have problems on such a long link due to ack limitations.
Switch the wireless protocol to nv2 :
and adjust this property accordingly :
Set at around 10% more than real distance.

interface wireless registration-table print stats
0 interface=wlan1 radio-name="4C5E0C85C05C" mac-address=4C:5E:0C:85:C0:5C ap=yes
wds=yes bridge=no rx-rate="6Mbps" tx-rate="6Mbps" packets=4,1 bytes=339,151
frames=4,1 frame-bytes=315,145 hw-frames=522,1 hw-frame-bytes=88218,169
tx-frames-timed-out=0 uptime=2s last-activity=2s60ms
signal-strength=-52dBm@6Mbps signal-to-noise=53dB signal-strength-ch0=-52dBm
signal-strength-ch1=-71dBm
strength-at-rates=-52dBm@6Mbps 0ms,-51dBm@9Mbps 1s750ms,-51dBm@12Mbps 1s920ms
p-throughput=5535 nstreme=no framing-mode=none routeros-version="6.15"
802.1x-port-enabled=yes management-protection=no compression=no
wmm-enabled=yes
tx-rate-set="OFDM:6-54 BW:1x SGI:1x HT:0-15 VHTMCS:SS1=0-9,SS2=0-9"

you have several configuration failures;

Both units are AP? For PtP this is wrong. One of the two should be ´station´ or ´station-bridge´.
Unit 1 is looking for WDS slave. Do you have WDS enabled? Should not. PtP better uses AP-bridge + station (If routed link) or 'AP-bridge' + 'station-bridge' (Transparant bridge).

ANI (Adaptive Noise Immunity) is switch off in both radio's. Switch it on! (AP+client mode in AP, client mode only in Station)
Wireless protocol in both is "Any" which probably means default which means "legacy 802.11". This is the 'old' default standard that is prone to interferences. Use either 'n-streame' or better; NV2 (TDMA) in AP.

Did you perform an frequency scan before you setup the link? Is the frequency indeed free or are (m)any interfering wifi signals around.

The disconnections while you have obviously good signal is a strong sign of interfering signals that disrupts the link.

thank you very much to CyberTod and WirelessRudy, now link with your advice, but I have to review a pigtail that have -75 before had this link with rocket m5 and the signal was -61.

a greeting.

interface wireless registration-table print stats
0 interface=wlan1 radio-name="4C5E0C85C05C" mac-address=4C:5E:0C:85:C0:5C ap=yes
wds=no bridge=yes rx-rate="39Mbps-20MHz/2S" tx-rate="86.6Mbps-20MHz/2S/SGI"
packets=1929,727 bytes=346297,535889 frames=1563,724
frame-bytes=348340,535906 uptime=2m5s last-activity=0ms
signal-strength=-54dBm signal-to-noise=50dB signal-strength-ch0=-54dBm
signal-strength-ch1=-71dBm tx-signal-strength-ch0=-55dBm
tx-signal-strength-ch1=-75dBm
strength-at-rates=-54dBm@6Mbps 0ms,-54dBm@9Mbps 600ms,-54dBm@12Mbps 4s220ms,-
54dBm@18Mbps 10s860ms
tx-signal-strength=-55dBm tx-ccq=72% rx-ccq=31% distance=39
routeros-version="6.15"

Also put latest ROS on; v6.19 is OK for simple PtP links.
And indeed, like CyberTod said, check one of the chains. I presume you work with a duo chain antenna?

But do a spectrum scan on both end;
\interface wireless pr
scan 0 d=4
and wait for the output.

If scan takes too long so the link disconnects, set on the remote end the scan frequency for a range up and down your aimed working frequency. (So in your case 5300 to 5500 for instance.) This give receiver more time 'to listen' while the connection is not broken (yet).
Also set 'hw-retries=15' (=max) so the link doesn't break too soon)

thank you very much to CyberTod and WirelessRudy, now link with your advice, but I have to review a pigtail that have -75 before had this link with rocket m5 and the signal was -61.

You obviously chained the radios so most probably one of the pigtails is not properly attached or became bend or dirty or wet.
If rest of the hardware (antennas) and link is the same netmetal should give almost same signals on both chains as rocket. And both chains should be more or less the same anyway..

Sorry; "chained" should be "changed"

HAVE A LINK WITH EVEN MORE EQUIPMENT TRANSMISSION AT LOW CCQ WHAT CAN BE? PASS AND NOT MORE THAN THIS LINK 50 MBPS 27 KM 34 am USASNDO ANTENNAS DBI.

interface=wlan1 radio-name="4C5E0C8597DB" mac-address=4C:5E:0C:85:97:DB ap=yes
wds=no bridge=yes rx-rate="130Mbps-80MHz/2S/SGI" tx-rate="6Mbps"
packets=982,2706 bytes=414196,546807 frames=969,2387
frame-bytes=414321,548124 uptime=14m19s last-activity=0ms
signal-strength=-57dBm signal-to-noise=45dB signal-strength-ch0=-59dBm
signal-strength-ch1=-60dBm tx-signal-strength-ch0=-62dBm
tx-signal-strength-ch1=-58dBm
strength-at-rates=-57dBm@6Mbps 0ms,-57dBm@9Mbps 10s930ms,-57dBm@12Mbps
44s360ms
tx-signal-strength=-56dBm tx-ccq=6% rx-ccq=49% distance=28
routeros-version="6.19" last-ip=192.168.201.1 encryption=aes-ccm
group-encryption=aes-ccm
tx-rate-set="OFDM:6-54 BW:1x-4x SGI:1x-4x HT:0-15 VHTMCS:SS1=0-9,SS2=0-9"
tdma-timing-offset=180 tdma-tx-size=496 tdma-rx-size=496 tdma-retx=11
tdma-winfull=0

Also put latest ROS on; v6.19 is OK for simple PtP links.
And indeed, like CyberTod said, check one of the chains. I presume you work with a duo chain antenna?

But do a spectrum scan on both end;
\interface wireless pr
scan 0 d=4
and wait for the output.

If scan takes too long so the link disconnects, set on the remote end the scan frequency for a range up and down your aimed working frequency. (So in your case 5300 to 5500 for instance.) This give receiver more time 'to listen' while the connection is not broken (yet).
Also set 'hw-retries=15' (=max) so the link doesn't break too soon)

that's very interesting!

I tried your suggestion without success... as soon as I hit enter I lose the connection (when running it on the remote).

You meant scanning first a range below the working frequency, then again for a range above the working frequency isn't it?

No, doesn't matter what you scan.

When you hit the 'scan' option, off course the remote unit almost immediately disconnects from the AP. But if you have a winbox session to that CPE open, it stays 'alive' (well, everything 'freezes') until the unit associate back to the AP (so, after the scan is stopped).
Now, this has to happen within some 4-6 minutes, otherwise the winbox session to that CPE is considered 'dead' and no longer valid.
But, if the CPE comes back associated soon enough it 'old' winbox session to it still picks it up and becomes 'live' again...

Now the trick is to have the CPE come back within 4-6 seconds. So you have to make sure the CPE doesn't scan too long, hence the D=4 (seconds) because in my experience that works 85% of the time. (But if you have an AP with a lot of CPE's, or the CPE has to scan a whole band before it finds th AP again... it all might take too long and the winbox session is broken..)

So, to make sure the CPE comes back asap after the scan has stopped you have to make sure that the CPE knows where to find the AP (limited scan range, both mac as SSID in 'connect to' list, wireless protocol set to what you use (so not 'all') etc.)

By limiting the scan range you not only give the radio time (4 seconds if D=4) to scan that part of the band thoroughly but this also brings it back to the AP faster (if you select a big range it takes longer for CPE to find the AP)

Off course you never set a frequency range in the scan range that does not include the AP's frequency. Otherwise it will not find it back after the scan is done...

If you really need to scan a part of a band away from the frequency in use by AP you can still set some remote frequency, like 5400-5500 and a separate frequency in the scan list (open new field in winbox) with the AP's frequency, like 5745 for instance.....

When a CPE has a very weak signal from AP (>-75dBm) than it might also delay 're-association' to AP and winbox session might be broken.
(You can now try to set D=3 or even D=2 to give CPE more time to associate again to AP but the shorter time to run the scan the less change radio 'sees' all that can be 'seen'.

One other 'trick'; When there are too many CPE associated to AP (and they are also very active) so the client you try to run a scan with won't come back fast enough is to temporarily deny access of all other clients to AP. This helps but is really a last resort thing, because you throw all other user temporarily off line.....

Remember to use the 'scan' option only from terminal, inside the winbox session of winbox. All in remote terminal might work but more delays so more change of a 'broken' session.


I use this feature regularly to find if a client with 'issues' is not hampered by a strong 3rd party signal that is close to the working frequency of the client's AP. Sometimes it can be that a 3rd party signal is relative weak at AP (so scan here didn't bother you) but at the remote client with issues you'll find this same 3rd party signal hits hard.......