Hello,
I am new in mikrotik and can anyone help me to make this my situation on Mikrotik step by step.
Thanks in advance
nikson
Hi nikson,
did you get your scenario solved? I am currently facing the same challenge.
Stefan
What kind of ethernet switch splits the wired side of RB133 to these 2 computers?
Hi taduikis,
in my case I have DLink DGS-1216T switches attached.
So they are websmart manageable switches. You shouldn’t have problems assigning your desired vlans then. All work is done by switches themselves. I’m not sure, but I don’t really think you have to do anything with Mikrotik itself. Just make wireless link completely transparent (WDS, MPLS, EoIP).
Understood.
So on the AP end, I have 3 VLAN assigned to the Ether interface. Two of them need to go across this particular WDS link.
What does the bridge on the AP need to look like in order for MT not to touch the VLAN tags but to direct them accordingly?
No VLANs on the bridge at all, i.e. just ether interface and WDS?
My scenario is described in thread http://forum.mikrotik.com/t/vlans-through-ptmp-link/50617/1 .
I’m quite new to vlan’s myself. I have got some managed switches lying still to be experimented with. Some time later, I think I will be able to tell more from the practical side. Anyway I think you should be able to do what you want without Routerboards. Imagine that all these RB’s and wifi link’s are like simple ethernet cable. Could you achieve what you want if you can connect these switches directly, with wires?
yes, with pure cables this would not be a big deal on the switches.
Switch 1 (my AP):
Ether == trunk port
Wifi/WDS to station 1 (OCB) == Access Port for VLAN 3
Wifi/WDS to station 2 (STW) == trunk port for VLAN 5 and 66 (to switch 2)
Switch 2 (station WDS [STW]):
Wifi/WDS == trunk port for VLAN 5 and 66
Ether == trunk port for VLAN 5 and 66
… or considering the actual switch instead of MT I would split traffic on the outgoing interfaces with trunk port for only one of the two VLANs or Access ports.
That is the cabling solution, but all this WDS/bridging/Wifi with the MT confuses me and I cannot get the solution working.
Well then, imagine that you somehow have to make that ethernet link between these two switches go wireless. Transparent bridge behaves almost like the wire itself. It shouldn’t strip any VLAN info while passing traffic. Check MikroTik Wiki for how to get it working. Since you’re using RB133’s, I’d recommend using WDS. Especially if you have nstreme turned on. Either way, from my personal experience, I can tell, that sorting everything out on the testbench before fitting the solution in real world is way better than trying it on “living links”..
Okay, I tried and failed.
As the AP has two VAPs running, I cannot change the mode of just a VAP as I have to change the real AP mode to bridge. But that’s not feasible as I do need the ap-bridge mode for the second VAP.
So, I followed http://wiki.mikrotik.com/wiki/Transparently_Bridge_two_Networks (just without the AP mode set to bridge) and found out that I can ping across now however, the VLAN tags are stripped off on the WDS link.
Hence, I have two IP networks bridged on the same wire which is not quite what we want.
I do agree with the testbench scenario, so I will keep trying.
Hello,
This is the second post that I see with this question and no direct answer…
I’m facing the same problem as describe wear, different VLAN’s but the same scenario.
VAP1: VLAN 101 → Station A
VAP1: VLAN 102-> Station A
VAP2: VLAN 202 → Station B
I Have put 1 VLAN in a WDS link with no problems…
But were you able to put 2 VLAN’s in the same WDS link. I also need two VLANs over one WDS link.
Can someone help me with advises, opinions, something…
Thanks,
Regards,
Craig Davids
I routinely put multiple vlan’s on the same wds link.
I have both ends of the link in AP-Bridge mode.
At each end, I have a single wds interface under the AP-Bridge.
At each end, I create all of my vlan’s under the single wds interface.
You can now use the vlan interfaces at each end. One usually creates a bridge for each vlan, and add the vlan interfaces you just created to their associated bridges.
You then use the bridges any way you need to.
This has always worked for me.
What I can’t get to work is vlan’s over nstreme. In that scenario, you can’t make both ends AP-bridge with a wds interface.
Using nstreme, I make one end AP-bridge, and the other end station-wds. I make the vlan’s under the wds interface on the AP-Bridge side, and under the station-wds on the other side. I find that traffic isn’t passing over the vlan’s, although something is happening with stp packets so the bridges associated with the vlans seem to see each other. I just can’t get traffic to flow over the vlan’s in the nstreme case.
If you’re not using nstreme, try the first configuration above.
If anyone is using vlan’s over nstrame, please let me know how you got it to work.
hello,
@dsobin
thanks for the advises.
I do not use nstreme.
I’ll be thankfully if you provide me some configuration examples about the first configuration that you mentioned.
Thanks,
Regards,
Craig Davids
craigdavids:
You said you have successfully put one vlan over a wds link. Post how you did that and I’ll show you what to do to add more vlans. I’m away from my office for the next two weeks and I can’t access my equipment, but I can explain it to you. Since you got one vlan to work, you must have most of what you need.
So, post generally what you did to make 1 vlan work, and I’ll add to it.
hello,
@dsobin
Refreshing what I said below:
I’m facing, different VLAN’s but the same scenario.
VAP1: VLAN 101 → Station A
VAP1: VLAN 102-> Station A
VAP2: VLAN 202 → Station B
I Have put 1 VLAN in a WDS link with no problems…
I have put vlan 101 on WDS 1 with VAP1 to link to station A, and VLAN 202 on wds 2 with VAP2 to link to station B.
When I said station is another Wireless router.
But I’m no been able to put VLAN 102 on WDS 1 in VAP1. I need two VLANs over one WDS link.
My configuration example:
eth1 is my uplink wired trunk port
I create VLAN interfaces for my vlans:
/interface vlan
add arp=enabled comment=“” disabled=no interface=ether1 mtu=1500 name=vlan101 \ vlan-id=101
add arp=enabled comment=“” disabled=no interface=ether1 mtu=1500 name=vlan202 \ vlan-id=202
I Create one bridge per vlan:
/interface bridge
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes
comment=“” disabled=no forward-delay=15s max-message-age=20s mtu=1500
name=bridge_VLAN_101 priority=0x8000 protocol-mode=stp
transmit-hold-count=6
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes
comment=“” disabled=no forward-delay=15s max-message-age=20s mtu=1500
name=bridge_VLAN_202 priority=0x8000 protocol-mode=stp
transmit-hold-count=6
Add vlan interfaces to the bridge:
add bridge=bridge_VLAN_101 comment=“” disabled=no edge=auto external-fdb=auto
horizon=none interface=vlan10 path-cost=10 point-to-point=auto priority=
0x80
add bridge=bridge_VLAN_202 comment=“” disabled=no edge=auto external-fdb=auto
horizon=none interface=vlan20 path-cost=10 point-to-point=auto priority=
0x80
I create virtual APs, one per vlan
The Primary interface, wlan1 in this case will be in ap-bride mode and will not have any SSID associated with it.
/interface wireless
set 0 ack-timeout=dynamic adaptive-noise-immunity=none allow-sharedkey=no
antenna-gain=0 antenna-mode=ant-a area=“” arp=enabled band=2.4ghz-b
basic-rates-a/g=6Mbps basic-rates-b=1Mbps burst-time=disabled comment=“”
compression=no country=no_country_set default-ap-tx-limit=0
default-authentication=yes default-client-tx-limit=0 default-forwarding=
yes dfs-mode=none disable-running-check=no disabled=no
disconnect-timeout=3s frame-lifetime=0 frequency=2412 frequency-mode=
manual-txpower hide-ssid=no hw-retries=4 mac-address=00:80:48:60:6B:91
max-station-count=2007 mode=ap-bridge mtu=1500 name=wlan1
noise-floor-threshold=default on-fail-retry-time=100ms
periodic-calibration=default periodic-calibration-interval=60
preamble-mode=both proprietary-extensions=post-2.9.25 radio-name=
008048606B91 rate-set=default scan-list=default security-profile=default
ssid=“” station-bridge-clone-mac=00:00:00:00:00:00 supported-rates-a/g=
6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps supported-rates-b=
1Mbps,2Mbps,5.5Mbps,11Mbps tx-power-mode=default update-stats-interval=
disabled wds-cost-range=50-150 wds-default-bridge=none wds-default-cost=
100 wds-ignore-ssid=no wds-mode=disabled wmm-support=disabled
add area=“” arp=enabled comment=“” default-ap-tx-limit=0
default-authentication=yes default-client-tx-limit=0 default-forwarding=
yes disable-running-check=no disabled=no hide-ssid=yes mac-address=
02:80:48:60:6B:91 master-interface=wlan1 max-station-count=2007 mtu=1500
name=wlan_VAP_101 proprietary-extensions=post-2.9.25 security-profile=
default ssid=CISCO_V_10 update-stats-interval=disabled wds-cost-range=0
wds-default-bridge=bridge_VLAN_101 wds-default-cost=0 wds-ignore-ssid=no
wds-mode=dynamic wmm-support=disabled
add area=“” arp=enabled comment=“” default-ap-tx-limit=0
default-authentication=yes default-client-tx-limit=0 default-forwarding=
yes disable-running-check=no disabled=no hide-ssid=yes mac-address=
02:80:48:60:6B:92 master-interface=wlan1 max-station-count=2007 mtu=1500
name=wlan_VAP_202 proprietary-extensions=post-2.9.25 security-profile=
default ssid=CISCO_V_20 update-stats-interval=disabled wds-cost-range=0
wds-default-bridge=bridge_VLAN_202 wds-default-cost=0 wds-ignore-ssid=no
wds-mode=dynamic wmm-support=disabled
Now I will need to put VLAN 102 on the WDS and VAP link that transport VLAN 101. I need two VLANs over the same WDS link.
Can you help me?
Thanks
Regards,
Craig Davids
Well, I do this in a different way. I do not use any virtual AP’s, nor do I use dynamic wds.
Here is my procedure:
At the central location, and ALL OF THE REMOTE LOCATIONS, create the interface: name=ap mode=ap-bridge wds-mode=static wds-default-bridge=none wds-ignore-ssid=yes
At the central location, interface->wireless->wds add name=wds-to-A, master-interface=ap , wds-address=
At the central location, interface->wireless->wds add name=wds-to-B, master-interface=ap , wds-address=
At the central location, interface->vlan add name=vlan101 interface=wds-to-A, vlan-id=101
At the central location, interface->vlan add name=vlan102 interface=wds-to-A, vlan-id=102
At the central location, interface->vlan add name=vlan201 interface=wds-to-B, vlan-id=201
At location A, interface->wireless->wds add name=wds-to-Central, master-interface=ap , wds-address=
At location A, interface->vlan add name=vlan101 interface=wds-to-central, vlan-id=101
At location A, interface->vlan add name=vlan102 interface=wds-to-central, vlan-id=102
At location B, interface->wireless->wds add name=wds-to-Central, master-interface=ap , wds-address=
At location B, vlan add name=vlan201 interface=wds-to-central, vlan-id=201
You can add as many vlan’s as you want to any location. Just use as interface the name of the wds interface to the place you want the vlan to go to.
Consider the wds link between the central location and location A as an ethernet wire. You can connect as many vlan’s to that ethernet (or wds link) as you want.
Same for the wds link between the central location and location B.
Add the vlans created above to ports on the appropriate bridge or bridges at each location and you are done.
There are no virtual AP’s needed in this example.
You could make locations A and B use mode=station-wds, but I don’t like to do that. By making all routers use mode=ap-bridge, I can perform a scan from anywhere and see the SSID and check for the link being up.
There are many ways to do this, but I’ve only used the one shown above.
Let me know how it works and if you have any more questions.
Thanks very much dsobin.
I never thought in a way like this. I was convinced that I have to create VAP’s.
In my test, seems all ok.
Thanks for the time spent,
Regards,
Craig Davids
I’m glad to help. I hope this helps others as well.
Feel free to check the plus box under Karma on the left side of the page to show others that I’ve been able to help someone.