VLAN

[yadavrajesh]

Hi -

Would love to have VLAN support !!!

[zed]

You mean Vlan tag/untag?

We are desperately looking for that... Dont understand the hold up..
maybe processing power?

Felipe

[ahooper]

There is vlan support in the units and although you can not set this up from a nice GUI interface in most cases you dont want to be doing this anyway.

[zed]

AHooper,


We dont mind the hard way, but we are getting mixed signals from the guys at UBNT, I think Keba said you could but then Mike said It wasnt possible.
There was a guy here that tried in so many ways and still couldnt get it done.

We have done these configs on other 802.11A products on pure shell and code and we dont mind. Do you kNow anyone that has created a managed vlan interface or Tag on these units? Vlan passthru works fine today.

I think that on the oswave firmware there are options to doing mgment vlan config..

Zed

[ahooper]

One tip i would give anyone is that if you want to play with the command line VLAN creation you put your unit into router mode as for some reason when it is in bridge mode you cant create the vlans and bind them correctly.

The first process is to destroy the default devices using wlanconfig (that is if you are creating the vlan on the wireless side)

/sbin/vconfig add <device> <vlan>
will create the relevent vlan on the selected device

you also need to bring the vlan device you ahve created up
/sbin/ifconfig <vlan.id> up

Also be sure that whatever you are creating is bound to the correct interface otherwise you just get your taggfed packets flowing the wrong way.

[zed]

Hooper, that is true and generally the way its done, somewhere down the forum there was a very smart guy who tried and tried and it seems that the guys at UBNT ran out of suggestions.

This is simple.. Has anyone done it? Has Ubnt tried it?
The way I see it is, that if they havent provided this feature when they know that it would make the nanos unbeatable is for a reason.

Mike, Keba and the others.. care to comment?

Zed













One tip i would give anyone is that if you want to play with the command line VLAN creation you put your unit into router mode as for some reason when it is in bridge mode you cant create the vlans and bind them correctly.

The first process is to destroy the default devices using wlanconfig (that is if you are creating the vlan on the wireless side)

/sbin/vconfig add <device> <vlan>
will create the relevent vlan on the selected device

you also need to bring the vlan device you ahve created up
/sbin/ifconfig <vlan.id> up

Also be sure that whatever you are creating is bound to the correct interface otherwise you just get your taggfed packets flowing the wrong way.

[fxwireless]

Hi,

Any updates as to when and/or if is it possible to have support for Management VLAN on NS.

Thanks,

Regards,


Satyam.

[void]

+1. I would really like to see support for VLANS as well.

[UBNT-keba]

Yes, it is working. Just all depends on fw version also in which custom script it is used.
I was using them with fw v 3.2.2-rc at least.

Also I know one WISP that uses VLANs with PS5 in they networks successfully.

[oneil]

Hey Ahooper

How do you tie back the vlans to the ethernet port so that they can be seen from a trunk port on a catalyst switch?

Oneil.

[sldnkarm]

Found this was possible after setting it up in MikroTik RouterOS. For my scenario, we have a Cisco switch with port(x) setup in trunk mode with VLAN 50 and 121 tagged across it.

VLAN 50 is management VLAN.
VLAN 121 is the single test client VLAN.

We install MikroTik AP in port(x) of Cisco switch and assign an IP on the vlan50 interface for management. Then we associate a PS2 running in Station-WDS mode (3.2.3734 firmware) to the MikroTik AP. The test setup of the VLANs that we are testing with was copied from this forum of another VLAN management example. I have just added to it to get our desired behavior.

Here is the file we are using in /etc/persistent/:
ifconfig br0 down
brctl delif br0 eth0
brctl delif br0 ath0
brctl delbr br0
ifconfig eth0 down
ifconfig ath0 down
ifconfig ath0 0.0.0.0 up
vconfig add ath0 121
vconfig add ath0 50
brctl addbr br0
brctl addif br0 ath0.121
brctl addif br0 eth0
ifconfig ath0.50 10.50.168.10 netmask 255.255.255.0 up
route add default gw 10.50.168.1
ifconfig eth0 0.0.0.0 up
ifconfig ath0.121 0.0.0.0 up
ifconfig br0 0.0.0.0 up

Basically we are shutting down and removing any interface configuration that was completed in our config-file that is on the PS2. The file above allows us to manage the PS2 via the ip assigned on the VLAN50 management VLAN. It also allows the client to connect via the eth0 interface and have the outbound packets Tagged with VLAN id 121 on the way to the AP and to have the incoming packets to the PS2 on VLAN 121 stripped as it goes on to the eth0 interface. Basically the client is on his own separate VLAN from the CPE all the way to the switch.

Let me know if I did not leave enough details for anyone else to successfully deploy this scenario on their own. Enjoy!

[oneil]

MikroTik is a trird party software, isnt there a way to configure the vlans in the NanoStation without a third party software?

[sldnkarm]

This was accomplished in AirOS, so there is no reason it will not work on the NS2. I simply stated that I first set up the scenario in MikroTik to get a grasp for what needed to be done to successfully deploy this architecture. Sorry if this was not clear and caused confusion.

You can use the example in my earlier post. Copy to a file in /etc/persistent/ save and reboot. Should be ready to go.

There is more than enough information in this forum to accomplish this setup or to tweak the config. I should know, as I learned most of this on this forum and from the 'ubnt crew' and 'arci'.

Next step is to get these configuration parameters established in the unit via the config file and not from an additional script. Either that or do some work in the SDK and create ways to manage VLAN setup in the web-frontend. Anythings possible as UBNT has given us the freedom to do so!

[oneil]

Still not working for me. when I copy that script into the directory i loose connection.

What am I doing wrong?
What mode should the radio be in Bridge or router?

[sldnkarm]

We are utilizing this configuration in bridge(network) mode and Station-WDS(wireless) mode. You must have a switch or Linux machine that is capable of vlan configuration. This is due to the fact that all packets on the wireless side will be vlan tagged packets. As for the Ethernet interface, you will not be able to directly access the unit as the management ip is via a vlan interface, so it needs a tagged packet.

You may want to try adding management ip on eth, so you can access the unit from the Ethernet port. I will not have time to further test any other vlan setups this week but will try and respond to your questions.

[texmesh]

Can someone post a summary of how to add a VLAN to the ethernet interface for management purposes.

I understand that a file can be place in /etc/persistent
Is the file extension name important?
Does that file run at boot up?

From the forum posting, this is what I gather I need to do to add vlan 24 to my ethernet interface. Is this correct?

ifconfig eth0 0.0.0.0 up # clean IP address from bridge
ifconfig eth0:0 down # remove auto IP address
vconfig add eth0 24 # add VLAN on top of bridge with WLAN ID=24
ifconfig eth0.24 172.16.200.23 up # add IP for VLAN

Does this affect any traffic flow through on other VLAN's?
I'm configured as a WDS bridge.

[UBNT-keba]

I understand that a file can be place in /etc/persistent
Is the file extension name important?
Does that file run at boot up?

It MUST be /etc/persistent/rc.poststart


From the forum posting, this is what I gather I need to do to add vlan 24 to my ethernet interface. Is this correct?

ifconfig eth0 0.0.0.0 up # clean IP address from bridge
ifconfig eth0:0 down # remove auto IP address
vconfig add eth0 24 # add VLAN on top of bridge with WLAN ID=24
ifconfig eth0.24 172.16.200.23 up # add IP for VLAN

Does this affect any traffic flow through on other VLAN's?
I'm configured as a WDS bridge.

If it is in bridge:
1. there is no eth0:0. There is br0.0 by default
2. all traffic coming from device to any IP from 172.16.200.X will taged with VLAN tag24
3. all other stuff seems OK from first view.

So you will be able to access device through ethernet side through VLAN24 by IP 172.16.200.23.

[meno]

but dont u have to add vlan to br0... to the bridge???

vconfig add br0 24


something like this..

[kellyv]

Mike,
I'm sure your getting sick of this but here is another +1 for VLAN support.

Ideally multiple SSID's with VLANs, however, any VLAN tagging would be a start.

I will have to look into the CLI method for now or alternative firmware :(

Kelly

[rb384997]

Hi -

Would love to have VLAN support !!!


I had to replace a short back-haul link. I used a bullet2 and a Ns2 for the link.
I could not get traffic to pass nor could I access the link through my mt-router at the end of the link.

I set the link to ap-wds/station-wds and also locked in the mac address on the station side to the ap. "similar to ptp mode"

WORKS!, I am able to pass vlan traffic.

see why below.........


Tranzeo links have this same problem if they are not in ptp mode. It is a layer 2 issue:

When you use a radio link on a VLAN trunk, there are some things to remember:

* If the link is not transparent (PxP, FDD, etc) the trunk will be unable to form. Remember, L2.5 bridging rewrites the layer 2 header.
* Tranzeo radios (and many other wireless devices) are not switches and are not VLAN aware. Therefore, tagged frames in the trunk will be ignored by the devices.
* Tranzeo (and other wireless devices) are not switches. They are BRIDGES between 802.3 and 802.11(or other wireless protocol). This is a fundamental difference that many, if not most, of our customers do not understand.
* The VLAN tag is 4 bytes long. This means that the maximum Ethernet frame size goes from 1518 bytes to 1522 bytes. Any devices on the trunk link need to be able to pass these frames. All current Tranzeo radios, with up to date firmware can pass VLAN tagged frames when in PxP mode.