You are here

Nodes island lost due to new commercial devices

5 posts / 0 new
Last post
VA2XJM
Nodes island lost due to new commercial devices

Hi everyone,

We have an island of 4 nodes linked through tunnel until we can link them through RF that we partly lost contact with due to new commercial equipment installed about 6ft above us....

Our equipment are configured like this:

3Nodes <> Mikrotik PowerBox (POE In) <---- 200' cable + lightning arrestor + 24V Injector ----> hAP - Tunnel node (Port 5) <> Internet ....

The hAP is still connected and someone on site can confirm me that the light on port 5 is blinking to suppose the link is connecting then dropping. Once in a while I can establish connection to hte powerbox for 2-3 seconds (not enough to past any command).

Is there a way to set the hAP DtD port to half-duplex for remote troubleshooting purpose ? I believe the new equipment might cause some RF to get into the wires, half-duplex might be a temporary way to set the island back until we can get on-site to move our units.

Over telnet, swconfig returns:

swconfig dev switch0 port 1 set link "autoneg off duplex half"
Failed to set attribute: Operation not supported



 

AJ6GZ
ethtool

Try using 'ethtool'. It's built-in to the AREDN code now, in latest releases.

Display the port and its capabilities:
ethtool eth0

Adjust:
ethtool -s eth0 speed 100 duplex half autoneg off

or whatever port settings u want to try.

Put the above line into /etc/rc.local to make it persist across reboots.

When u can get into the PowerBox, look in the logs for the reason the port to the hAP might be flapping. A bad cable might show up as a PoE short/overload for example. If you're not powering the hAP remotely, disable PoE on that port as good practice.

If by chance you have old code on the node(s) you can install ethtool manually by running this on the node's command line:
opkg install http://downloads.openwrt.org/releases/19.07.2/packages/mips_24kc/base/et...

Note that you may need to adjust the releases/19.x.x.x folder to find one that works if you have a really old AREDN version.

Ian

kc8ufv
kc8ufv's picture
Just another thought, make
Just another thought, make sure in the powerbox that the long ethernet cable option is turned on. We just did an install using that a couple weeks ago, did the testing on the ground with only a few feet of POE cable, and it worked fine, but when we put the nodes up, we had about a 50ft ethernet cable feeding the 3 nodes and the powerbox, and it kept showing the nodes as an overload. I first thought it might have been a cable damaged in install, but then found that option.
VA2XJM
@kc8ufv this is the first
@kc8ufv this is the first thing I checked in the config dump. But it worked perfectly until a WISP provider installed new dish above us.
VA2XJM
I edited the post to show
I edited the post to show port config. The PowerBox is plugged into the port #5 of the hAP that seems to be inside the virtual switch so ethtool will not work unless there is a way around....

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer