You are here

VLAN2 / DTD operation on both ethernet ports Nanostation?

7 posts / 0 new
Last post
k1ky
k1ky's picture
VLAN2 / DTD operation on both ethernet ports Nanostation?
Can the Nanostation config file be changed to allow DTD/VLAN2 operation on both Ethernet ports like we can on the AirRouter models?
Any progress on enabling VLAN2/DTD on the main port on the XW Nanostation models?

 
AE6XE
AE6XE's picture
Nanostation M5 XW network port behavior

K1KY,  The NSM5 XW has a reported defect at the hardware level (or at least "unsupported" feature :) ).  It has a different chipset configuration than the others.  The tic is dug in deep.   When we try to define dtdlink or vlan 2 shared with the LAN untagged traffic on the same port, it fails.   Consequently, we ended up splitting the LAN on one port and WAN/DTDlink (vlan 1 / 2) on the other port.  this is unique to the NS M5 XW and keeps bitting me every once in a while forgetting this issue.    I ended up using a permanent marker and wrote "LAN only" by the main port, and "DTD/WAN only" by the secondary port.

Note, openwrt  closed this defect with the comment, "Status changed from new to closed -- The switch of the Nanostation M5 does not support mixed traffic, each port can only be tagged or untagged for all vlans it is part of."   See:  https://dev.openwrt.org/ticket/20021   However, this chip is reported to be working correctly in some devices.  Ubiquiti may have wired something up poorly on the motherboard or there's still a bug in the linux driver config in OpenWrt somewhere.

Joe AE6XE

k1ky
k1ky's picture
Nanostation M5 XW network port behavior - Thanks for the update
Thanks for the "refresher" Joe. So what I'm hearing is that this could possibly work on some devices.  I'm willing to give it a try and see what happens.  I have successfully attached  a mixture of Nanostations with the normal UBNT firmware and AREDN on the 2nd port and they seem to power up and communicate just fine.  What I'm looking for is the ability to add another MESH node station on a tower without running another network line and without adding a switch on the tower. 
AE6XE
AE6XE's picture
Each mesh node on the tower
Each mesh node on the tower only needs 1 x cat5.   2 x cat5 cables is not strictly needed for the NS M5 XW (is this what you mean by running up another cable?).   However, to only use 1 x cat5 cable for the NS M5 XW, this requires the power feeding into the secondary port and no LAN devices receive an IP address from this node.    I've done this many times, and while it is not the intended manufacturer's design and the typical "do at own risk" applies, I've yet to see any examples of this not working or smoking a device to date.   The NS M5 XW will DtDlink and communicate with all the other nodes on the tower (through the switch at the base of the tower).  Any LAN devices (laptop, ipCam, etc.) can be configured to receive IP addresses from another mesh node (non-NSM5XW) on the tower to meet all the needs.      

 
k1ky
k1ky's picture
Already doing that
Already successfully running XW Nanostations with just one cable to the secondary port with no issues for over a year.  Was looking for a way to add another node without running another cable back to the switch (space in the underground PVC pipe at a premium). Was hoping to tag another unit off an existing Nanostation on the tower.  
WU2S
WU2S's picture
An alternative method
Due to site constraints at Fair Lawn ARC we have one one Ethernet cable going to the roof and we wanted to operate nodes on three bands.
The solution is to put a 5 port ToughSwitch into a high quality weather proof box. Cable glands are used on all the cables going into the box.
We feed 24 VDC power up the cable, then using a PoE splitter, feed the ToughSwitch, which then distributes power to the 3 nodes. 
This has served us well for over 18 months in all kinds of weather - so far, so good.
KG6JEI
"Any progress on ..."
"Any progress on ..."

Official status location for everything is the ticket and code tracking in bloodhound. http://bloodhound.aredn.org

Anththing that's being progressed on with public info goes through that system either as a ticket or as code that's been approved and merged

If it isn't in there it probably doesn't have any progress or isn't being worked on.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer