I just got a nanostation M5. It turned out to be an XW model. I flashed it with AREDN 3.15.1.0. I racked my brain for hours trying to get it DTD'd to my 2.4 and 5 GHz nodes. It might be well known to some here or it might be a fluke, but I discovered quite by accident that my Nanostation XW M5s dtd link on the secondary Ethernet port but will not link on the primary. Just a heads up in case someone else gets a node that links this way.
73,
Anne
73,
Anne
On a side note, we have an exhibitor booth at the Linux Expo on Jan 21st-24th in the Pasadena conv center. https://www.socallinuxexpo.org/scale/14x Any and all local area Mesh'ers attending the conference are welcome to come hang with us.
Joe AE6XE
Orv W6BI
Joe AE6XE
David
Thanks,
http://www.aredn.org/content/device-device-linking-dtdlink
Keith - AI6BX
This is answered on the DTDLink documentation page graphically http://www.aredn.org/content/device-device-linking-dtdlink
After that that a straight or crossover shouldn't matter as the nodes have a build in auto cross ability (midi-X)
Did you see the port 1 Ethernet activity light on the XM device blinking and the Ethernet activity light on the secondary port of the XW device blinking signifiying a connection with data passing over it ?
Hi kg6kco. Are you using three ethernet cables?
1 cable running from the PoE port on its injector to the XM NSM2 primary port.
1 cable running from the PoE port on its injector to the XW NSM5 primary port.
1 cable running from the XW NSM5 secondary port to the LAN port on the XM NSM2’s injector.
A support data file contains significant amount of diagnostic data that provides significant necessary information on the operation of the node at the time the file is generated. Without this data we are essentially just guessing without any information and are unable to provide any viable input on the situation.