Hello everyone
Situation:
I want OFFICE A LAN and OFFICE B LAN would be completly separated by vlan. Why vlan? I think it’s less resource hungry then vpls, or especially eoip. I need as much bandwidth as possible. On both LANs there are no any managed(vlan capable) switches.
Tried this:
on AP
add vlan1 on iface wds1
add bridge1 with vlan1, eth1
on STA
add vlan1 on iface station-wds
add bridge1 with vlan1, eth1
vlans dont see each other
Any solution?
Thanks.
Hi VMNX,
Your setup and procedure is not clear. elaborate more clearly.
Thanks for your reply, I edited first post, I think now it’s much easier 
Your statements make little sense.
Why vlan? I think it’s less resource hungry then vpls, or especially eoip
Actually I would argue that VLAN and anything ethernet based is inefficient here. if you have limited bandwidth, then ROUTING should be used because VLANS will broadcast a lot of broadcast traffic over the WAN link that makes no sense there.
You need a carrier level protocol. eoip HAS overhead, VPLS less. Pure VLAN would assume a pure ethernet leayer but even more without routing on both ends it means you miss a roadcast boundary which just is going to come and hurt you.
Routing for 20+5 PCs ? I doubt it
So, how to make this setup work?
i m stucked in AP-bridge configuration.
Station wds configuration is easy.
OK Now i got it.
This is little bit complicated…
Need to create 3 Virtual APs, 3 Bridges, 3 VLANs on both side.
2nd
station wds same
1- creat bridge between eth1+wds+wlan
2-creat vlan in interface "bridge"
3- creat ascond bridge betwin vlan+eth2
4- ip - dhcpclient add bridge1 and bridge 2
it will separate your a and b office
add a second radio with antenna and you get 2 different links and more bandwidth.
Thanks for replies. Done it with abdu808’s scenario. Ran some test, and saw that vlan is the same as vpls in CPU resources. So I stay with vpls config, it is less complicated, I can add vpls interface directly to wlan, and then bridge vpls with eth. Simple.
Thanks again, for help.