I got a couple of new Nanostation Loco M5s with the XW firmware. I downgraded to 5.5.x, and installed the "NanoStation M5 (XW)" firmware. After loading the firmware and rebooting, I was not able to get any DHCP lease or other traffic over the LAN port. I had to connect to MESHNODE to complete setup. After saving my node name as KG6KCO-LOCOM5-ROAMER and rebooting the node, I am not able to reach the node at all. The lights are on and the node seems happy, but no DHCP lease is offered. I can't ping the LAN IP of the node even if I set a good 10.X.X.X IP and netmask on my laptop' LAN port. Did I use the wrong firmware, or is this specific node not supported, or what?
I am getting the same results with the Beta firmware (same device type).
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
KG6KCO,
Unfortunately, the NS Loco XW is still not yet on the supported list. The hardware has this nasty side effect of the ethernet port locking up and becoming unusable (like in hours after booting). The NS-M5 XW firmware isn't compatible, it expects the hardware to have a 'switch' chip, which the loco only has a single ethernet port on the cpu. Hence, the ethernet port isn't configured with this firmware. These XW issues are next in line in the cross hairs after 3.16.1.0 is released.
Joe AE6XE
Thanks for the extra details on why it isn't enabled. I figured I might have some problems, as the specific model is marked YELLOW on the matrix. Good to know the whys of it. Is it possible to enable the Ethernet port as a dtd link, or connect to it via a crossover cable? As part of my initial troubleshooting, I tried connecting via normal and crossover cables, not knowing that the port was disabled in the firmware image.
On a semi-related note, I was seeing the OLSR announce packets on the Ethernet port (via tcpdump), even though it was disabled.