You are here

Mikrotik XL HP5 ethernet issue

5 posts / 0 new
Last post
AD6KV
Mikrotik XL HP5 ethernet issue
Recently upgraded to ver 25.x.x successfully, went into package management to remove and reinstall meshchat.  After rebooting no ethernet activity.  I'm unable to recover ethernet and the node.  Suggestions?
nc8q
nc8q's picture
resetting-a-node-to-firstboot-state
http://docs.arednmesh.org/en/latest/arednGettingStarted/firstboot_setup....

With your node powered on and running its current AREDN® firmware, press and hold the reset button on your node for 15 seconds.
This will cause your node to enter its firstboot state from which you can start fresh with your node’s configuration.
AD6KV
resetting-a-node-to-firstboot-state
Hi and thanks - 

Tried that with no luck, changed cables and checked power, tried pinging 192.168.1.100 as well as localnode... no visible ethernet connection.  I was hoping for the "NOCALL-..." window but receive nothing.  Seems to be ethernet at the node, I connected to a LAN using the computer port to verify the computer.
nc8q
nc8q's picture
tried pinging 192.168.1.100 as well as localnode
Try PINGing 192.168.1.1 .

Did you assign a static IP address on your workstation in the range 192.168.1.[2-254] ?

"I connected to a LAN using the computer port to verify the computer."
So, I assume that your computer is in DHCP client mode.
Did your workstation obtain an IP address via DHCP?

http://docs.arednmesh.org/en/latest/arednGettingStarted/firstboot_setup....
"After you have installed the AREDN® firmware and rebooted the device, the node will have a default IP address of 192.168.1.1.
You can set your computer to receive an IP address from your node via DHCP.
After connecting your computer to a LAN port on the node or the PoE unit, you should be able to ping the node at 192.168.1.1.
Navigate to your node’s web interface at http://192.168.1.1 or http://localnode.local.mesh.
Some computers may have DNS search paths configured that require you to use the fully qualified domain name (FQDN) to resolve localnode to the mesh node’s IP address."
-or-
Try loading the factory.bin via TFTP.

3s, Chuck
 
AD6KV
Reloaded it...
Had to revert back to the initial install using TinyPXE.  Fortunately no hardware issues.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer