1

Hey fellow spicers, I need some help.
I have a wireless air bridge “nanostation M5” between 2 buildings about 40 meters apart. Signal is good. At building A is the core of the network “10.10.10.XX” and building b is just a extension for the internet and network. I have made a vlan for building B 10.10.20.XX. I have tested it and it works great from the POE switch at building A. The air bridge is connected to the above POE switch. The air bridge has a building A IP address on both ends. At building B the IP scheme is transferred over there by the wireless bridge. Each switch on both ends are HP. I am super stumped. Would I need a trunk set up so vlan traffic can flow? Do each of the air bridges need to be on building A or B ip scheme so building B can have its on. I think I have over thought this so I need to help. I am somewhat tech savvy but this has stumped me

Thank you in advanced

7 Spice ups
2

Ubiquiti NanoStation, I assume? These devices should pass any VLAN through. They have, I believe, a management VLAN awareness so you can enable that for the VLAN you want and configure an appropriate IP address.

The switch ports the NanoStations are plugged into would then be trunk ports (Cisco term) or in HP terms, tag the two VLANs on the port.

Untag ports this new VLAN on the Building B switch and provide DHCP in whichever way is appropriate. Now any computers connected to a port with VLAN xyz untagged in the 10.20.x.x subnet will maintain this VLAN ID as it traverses the NanoStations.

The switch at the other end should have the same VLANs tagged and then downstream from that to whichever devices/ports that VLAN has access to. There’ll be a router at some point on that new VLAN so the building B subnet can gain Internet access.

The ports NanoStations plug into could also be hybrid type ports where some VLANs are tagged and one of them is untagged. This untagged one is where the NanoStation’s management layer sits on and would get an IP address for itself. When dealing with network equipment it’s often more desirable to tag all the VLANs so you don’t end up having to remember what’s tagged and what’s untagged and keep it straight.

1 Spice up
3

Taking a step back for a minute… If building B is only an extension of the existing network, and Internet access, why bother with a VLAN?

4

I second this. Not discounting OP’s question, just would like clarification as if it is just an extension of the same network, routing rules should be the same.

5

It’s just an extension…for now. When things get busier the additional vlan might be needed, and that may not be the time to be prototyping.

6

I want building B to have their own vlan for wired and wireless connections. And I would like to manage it from building A. I don’t want to fill up building A ip scope from building B traffic . And also I want to move some servers over to building B in the future and have them on our VMware vlan. So just want to separate each building if that makes sense.

7

Then you will need to setup a full VLAN and routing setup for this to work. See my first reply to your question which includes some of the points you need to think about and implement.