Wireless Wire/LHG 60 distance - expected signal

RouterOS Wireless Networking
1

Hello, I saw several threads about Wireless Wire and LHG60 products.
I think it would be helpful to share here some real life data of our installed links, what do we have expect on what distance.
Please share info like this:

interface w60g station monitor wlan60-station-1 once

connected: yes
remote: 04:D6:AA:A5:EF:20
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -61
tx-sector: 38
tx-sector-info: right 1 degrees, up 0.2 degrees
distance: 640.27m

remote:

connected: yes
frequency: 58320
remote-address: 04:D6:AA:A5:EF:14
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -59
tx-sector: 51
tx-sector-info: left 0.2 degrees, up 1 degrees
distance: 640.28m

LHG60 / LHG60 - ROS 6.43rc34

ps: at installation the maximum RSSI was around -51 and signal around 95, so i think, i have to install a script what logs those values, when and why the signal decreases…
probably you have script you would like to share? :slight_smile:

Also i would be pleased to get info about Wireless wire links, and Wireless Wire (AP) vs LHG60 too!

2

wAP 60G:

frequency: 58320
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -58
tx-sector: 35
tx-sector-info: center
rx-sector: 96
distance: 44.94m

But since the last firmware update, the tx-sector-info is all over the place (changing from “center” to +/- 27 degree in both horizontal and vertical axis)

I don’t have (yet) LHG60 but just for info:

Metrolinq 2.5 60-35:
Frequency: 62640
RSSI: -46
Remote RSSI: -49
Data rate: Tx: 2502 Mbps, Rx: 2502 Mbps
Distance: 1Km

Metrolinq 2.5 60-35:
Frequency: 64800
RSSI: -44
Remote RSSI: -45
Data rate: Tx: 2502 Mbps, Rx: 2502 Mbps
Distance: 1.3Km

Metrolinq PTP60-19:
Frequency: 62640
RSSI: -55
Remote RSSI: -47
Data rate: Tx: 2502 Mbps, Rx: 2502 Mbps
Distance: 300m

3

@cohprog thanks for the info. May i ask your experience in those rainy days over Metrolinq?

4

WW

frequency: 58320
mcs: 8
phy-rate: 2.3Gbps
signal: 50
rssi: -68
tx-sector: 28
tx-sector-info: center
rx-sector: 96
distance: 124.56m
5

We just got some big storms. I have those lines since 10 months or so and never got disconnected even during storms. The worse I got was a drop in rate from 2.5Mbps to 1.2Mbps (each direction) for a few minutes. But that’s because those line have plenty of margin: During the worse storms, the signal on the 1km+ lines droped from -45 to -67. (The Metrolinq have 5Ghz built-in backup but I disabled it as I never lost the connection)

There is a hugh difference between the channels. I think that at those range (1km+) only upper most channels (3 and 4) are really usable. In fact, those kind of lines should use the channel 4 (64800). That channel is available in the last Mikrotik firmware but only from the cli.

I haven’t tested the LHG60 yet but from what I read I think they should have higher rate with small packets than the Metrolinq. With large packets (1500), the Metrolinq are better as they can easily do 1.5Gbps one direction and 2.5Gbps total throughput (they have a 2.5G ethernet interface and a SFP+ one). What worry me a little about the LHG60 is that someone said he got a 1.3Km line runing with a -67 signal. I hope it’s a problem of alignement because such line would drop as soon as there is some rain.

There is a 60Ghz link calculator on Ignitenet cloud website. You don’t need to have one of their device to sign to it. Obviously it doesn’t apply to Mikrotik devices but it can still give you an idea of what signal drop you may expect based on the distance and rain condition.

Frankly, I am perfectly happy with all the Metrolinq devices I have. There is only 2 reasons I am considering using LHG60 over the Metrolinq: They are a lot cheaper (but the Metrolinq are cheap enough for the performances that I don’t really care) and they should have a higher rate with small packets (The AP are only connected to Gbps devices so I don’t care that the Metrolinq can do more).

6

SiteA

connected: yes
frequency: 58320
remote-address: 04:D6:AA:A4:CA:63
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -60
tx-sector: 29
tx-sector-info: right 0.6 degrees, down 0.2 degrees
distance: 1389.92m

SiteB

connected: yes
frequency: 58320
remote-address: 04:D6:AA:A4:CA:57
mcs: 8
phy-rate: 2.3Gbps
signal: 95
rssi: -58
tx-sector: 27
tx-sector-info: center
distance: 1389.92m

In fact i would really love an option in the device, where I can set a link margin value - and below that, the wireless interface would be disabled in bridge.
(or just execute a command when stepping in/out the allowed range)
that would allow us to keep link until its dropping packets, because dynamic routing protocols do survives visible packet loss.
(i know, change hello time’s value is an option but…)

7

At siteA, we have installed a WirelessWire in AP mode, so will check if remote LHG60 can connect from 1.4km :slight_smile:

8

And ROS is a big advantage. Could do much more than a plain bridge.

9

You could do a script and even change ospf cost until the rain stops and signal goes to normal.

10

I know, that i can do checking signal in every minute and do something with script.

I would happily pay a bounty to have an option in wireless interface for this.

Like with LED wireless signal strength display where is can set which LED lit for what signal.

11

LHG60:

Side A:
frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 85
rssi: -55
tx-sector: 55
tx-sector-info: right 1.4 degrees, up 1 degrees
rx-sector: 96
distance: 1166.34m

Side B:
frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -58
tx-sector: 56
tx-sector-info: left 1.4 degrees, up 1.4 degrees
rx-sector: 96
distance: 1166.36m

(see post in other thread for details)

12

Wire Dish 60 GHz XL + 5Ghz BackUp
The LHG 60 PCBA has a 5Ghz Wifi part

when you make LHG 60 XL + 5GHz ?

LHG 391 mm
LHG XL 550 mm

13

Yesterday we had small storm here, both 640m and 1400m link stopped several times sometimes for seconds, but even 2 minute outtage happened.
kmet_csap1_20180727.png
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -58
tx-sector: 56
tx-sector-info: left 1.4 degrees, up 1.4 degrees
distance: 640.23m

jul/27 22:15:03 interface,info wlan60-station-1: link down
jul/27 22:15:27 interface,info wlan60-station-1: link up
jul/27 22:24:15 interface,info wlan60-station-1: link down
jul/27 22:24:50 interface,info wlan60-station-1: link up
jul/27 22:26:42 interface,info wlan60-station-1: link down
jul/27 22:26:50 interface,info wlan60-station-1: link up
jul/27 22:55:08 interface,info wlan60-station-1: link down
jul/27 22:55:11 interface,info wlan60-station-1: link up
jul/27 22:55:55 interface,info wlan60-station-1: link down
jul/27 22:56:07 interface,info wlan60-station-1: link up
jul/27 22:58:07 interface,info wlan60-station-1: link down
jul/27 22:58:42 interface,info wlan60-station-1: link up

longer:
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -60
tx-sector: 36
tx-sector-info: center
distance: 1389.94m

jul/27 22:13:41 interface,info wlan60-1: link down
jul/27 22:13:50 interface,info wlan60-1: link up
jul/27 22:15:12 interface,info wlan60-1: link down
jul/27 22:19:27 interface,info wlan60-1: link up
jul/27 22:26:25 interface,info wlan60-1: link down
jul/27 22:26:28 interface,info wlan60-1: link up
jul/27 22:27:18 interface,info wlan60-1: link down
jul/27 22:28:52 interface,info wlan60-1: link up
jul/27 22:28:56 interface,info wlan60-1: link down
jul/27 22:28:59 interface,info wlan60-1: link up
jul/27 22:29:15 interface,info wlan60-1: link down
jul/27 22:29:18 interface,info wlan60-1: link up
jul/27 22:29:24 interface,info wlan60-1: link down
jul/27 22:29:26 interface,info wlan60-1: link up
jul/27 22:55:50 interface,info wlan60-1: link down
jul/27 23:01:58 interface,info wlan60-1: link up
jul/27 23:02:05 interface,info wlan60-1: link down
jul/27 23:02:08 interface,info wlan60-1: link up

14

I updated Librenms to poll the Wireless Wire. Here is the updated file. It’s not perfect, but it works.

https://drive.google.com/file/d/1IwUy3cXoIuR--U3NpsBOmN-qSvUDp0Bl/view?usp=sharing (/opt/librenms/LibreNMS/OS/Routeros.php).

15

I’ve been looking for info on updating Librenms. Thanks for the file but I can’t see any extra in after changing the php file.