i have been trying to create a multiple VLAN connection over an existing wireless link, but every time i create a VLAN, and add the existing WLAN interface to VLAN, then the wireless connection will be broken, and disconnect.
The reason i do this, because i have multiple router behind the wireless link, and i need to separate each of them via a VLAN.
Please help, what method did i miss? or is this an incorrect setting?
QpoX,
Thank you for your reply, i have read those thread before.
but those thread use multiple interface wlan.
My situation is like this:
[Router A]via LAN cable[Client]~via wireless~[AP]Via Lan cable[Router B]
on Router A: 2 ether
on Client (routerboard) : 1 ether, 1 wlan
on AP (routerboard): 1 ether, 1 wlan
on Router B: 2 ether
The target is to create a vlan from network behind client to the other side of AP.
I just give example with router A and router B, in reality i have multiple router behind the client.
I have try to create vlan between router [A] and [Client], but since only 1 interface wlan,
i dont know how to create multiple vlan for another router behind [Client]
Do i make you dizzy?
Please help…do you have any direction?
You must use wds bridging. Create your vlans on wlan interface
Create a bridge for each vlan, in ports add vlan to appropriate bridge. We use wds bridging network wide… works very well.
I am not quite sure about the wds bridging.
What do i need to use as default bridging in the wlan for each network ?
Because there is only 1 wlan on the each side of the radio.
[Router A,B,C]via LAN cable[Client]~via wireless~[AP]Via Lan cable[Router D,E,F]
For network A:
wlan1 : default bridge: Bridge A
Bridge A, port = vlan_A_wlan1, ether 1
For network B:
wlan1 : default bridge: ???
Bridge B, port = vlan_B_wlan1, ether 1
For network C:
wlan1 : default bridge: ???
Bridge C, port = vlan_C_wlan1, ether 1
If i’m right, you have 3 clients connecting to AP.
VLAN1 is connecting to all 3 clients AND AP, but VLAN2 only to eth2 of clients.
For this, you have to make an AP, with WDS allowed.
-all clients will have it’s own WDS interface (like wds-client1 or so)
-make VLAN1 interface bound to all wds-clientX interface (like vlan1-client1)
-put all the vlan1-clientX interface to bridge (if needed)
-make VLAN2 interface bound to all wds-clientX interface (like vlan2-client1)
-put all the vlan2-clientX interface to bridge (if needed)
On clients:
make station-wds interface
make VLAN1 interface bound to station-wds (bridge it with ether1)
make VLAN2 interface bound to station-wds (bridge it with ether2)
Keep in mind, if you want to use VLAN interfaces, don’t use their master (physical) interface!
I don’t really get the point of your separation in vlans, but you might use EOIP tunnels, between the client routers and the router in the right of your picture, and run them across any routed network in between, and in this way you have a “virtual ethernet” to your clients, passing layer 2 data.
After this, use your imagination.
Well, EoIP should work, but its using extra resources, while VLAN is a simple bridge, with (i think) minimal extra resouce to put extra 22byte on the frames.
unlimitedme: you need only one WDS on each client, but need more VLAN
you need this on AP side:
add arp=enabled comment=“” disabled=no interface=xxx-wds mtu=1500
name=“backbone_vlan_xxx” vlan-id=1000
add arp=enabled comment=“” disabled=no interface=xxx-wds mtu=1500
name=“bridge_xxx” vlan-id=1
you need this on CPE side:
add arp=enabled comment=“” disabled=no interface=wlan1 mtu=1500
name=“backbone_vlan_xxx” vlan-id=1000
add arp=enabled comment=“” disabled=no interface=wlan1 mtu=1500
name=“bridge_xxx” vlan-id=1
than bridge the backbone_vlan_xxx interface with eth1 and bridge_xxx with eth2
oh, the above for passing VLAN over wireless.
if didn’t realised - until now - that you want to pass VLAN on wire.
For this you must have an active node (let’s say 802.1q capable switch) to work well - or have a mikrotik CPE with 3 ethernet ports
connecting client1 to eth1 and so.
I participated in that topic, being worried about the eoip overhead. In my scenario, it prooved of little impact. I am transferring about 10 mbits over 2 hops, wireless, with just about no impact in performance, as far as i can see it.