Posted: Mon Jan 21, 2019 18:58 Post subject: VAP / VLAN bridge not working
Hi all,
asus rt-ac66 running v3.0-r38326M giga.
I am trying to set up the asus as an access point to 2 physically separate networks. I have a router with multiple networks configured - a 10.1.10.X for me, and a 192.168.255.X for guests. I want the asus to be a pure AP - so no DNS, DHCP, NAT, or other nonsense running on it.
Here's what I got:
- Ports 1 and 2 are assigned to vlan 1
- ports 3 and 4 assigned to vlan3
- 10.1.10.X cable plugged into port 1
- 192.168.255.X cable plugged into port 4
- created a new virtual interface, wl0.1, and bridge, br1.
- wl0.1 and vlan3 are assigned to bridge br1. All else is on br0.
When I plug in a cable to port 2 I get assigned a 10.XXX address as well as an IPv6 with the correct prefix. Same for port 3: 192.XXX address, and an IPv6 with a different prefix. So far so good.
However, clients cannot connect to wl0.1. They fail to receive an IP (v4 or v6) from the router. I can see the clients in the router's DHCPv4 lease table, so the DHCP requests seem to get through; the responses back to the client, not so much. Clients are able to connect to wl0 and get ipv4 and v6 addresses.
I'm at my wit's end with this - and I am pulling my hair out because I had the same setup working before with an older (ancient) dd-wrt version, but blew it away in an update
If anyone can tell me what I'm missing in my (slightly unconventional) setup, I'll be forever grateful!
Thanks,
- Dave.
Edit: Title; Removed paragraph about IPv6 connectivity not working. I figured that part out - it was my router. Simple reboot fixed it 🤷
vlans.png
Description:
Filesize:
30.65 KB
Viewed:
3623 Time(s)
bridging.png
Description:
Filesize:
48.07 KB
Viewed:
3623 Time(s)
Last edited by therealmrfox on Sat Jan 26, 2019 1:36; edited 1 time in total
Posted: Mon Jan 21, 2019 21:42 Post subject: Well, fuck me with a chainsaw.
Downgraded to the previous ancient version - v3.0-r30826 giga (11/01/16) - and this works like a charm. So it's definitely something that's broken with newer builds.
Thanks BR07H3R. However I don't want to actually get the access point involved with routing or DHCP (I have my Mikrotik router running DHCP and doing routing/NAT). All I need the AP to do is bridge traffic between the wireless interface and a LAN port assigned to a VLAN.
This does work on build v3.0-r30826 as it should. It does not on v3.0-r38326M.
Something in how bridging (or the combination of bridging + VLANs + VAP + asus hardware + phase of the moon...) is handled between those builds must have changed
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sat Jan 26, 2019 9:59 Post subject:
VAP is broken on newer builds.
There are two workarounds
Problems and workarounds:
1) When VAP is not working at boot; workaround startup command:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
2) Aternative way to get VAP working: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=317181
Posted: Sun Jan 27, 2019 0:38 Post subject: Re: VAP / VLAN bridge not working
jxm wrote:
You cannot use subnet 192.168.255.x. You cannot use 255 in any of the octets, because 255 is used for broadcasts.
Ugh. Oops. Actually the subnet is a /16 so 255.X for the host portion should be OK, but I certainly didn't do myself a favor by assigning a /24 to the bridge IIRC I tried this w/o assigning any IP to the bridge at all and that didn't work either, though.
Not sure if it will help but here is my networking tab.
Thanks BR07H3R!
I used brctl rather than the UI to assign the VAP and VLAN to the bridge (see my screenshot - I left the UI blank). I thought the result would be the same, but I'm starting to wonder if that assumption was mistaken.
IIRC I tried this w/o assigning any IP to the bridge at all and that didn't work either, though.