[mbze430]

I tried to add my wl0.1 interface into the br1 bridge which also contains vlan3. Which made the wl0.1 virtual interface unable to connect.

So I removed the wl0.1 from br1 and it works fine.

decided to create a br2 and put wl0.1 into that bridge and it ALSO doesn't work.

So there might be a bug when adding a wireless virtual interface into a bridge.

Can anyone else test this and report back?

I am on an ASUS AC-66u on Firmware: DD-WRT v3.0-r39296M giga (03/27/19)

[mbze430]

okay so I set a new virtual wifi interface using the 5G on the AC66U, which is wl1.1.

Added wl1.1 to the br1 bridge and works just fine.

so might be just isolated to wl0.1?.......

[mbze430]

So I have done a bit more testing.


I created a 2nd Virtual Wireless interface. Now I have Test-2 (wl0.1) and Test-3 (wl0.2). Added both to 'br1'.

wl0.1 still fails and reject all connection attempts. HOWEVER! wl0.2 WILL connect. So I don't WTF is going.....


**UPDATE**

Now nothing works wl0.1/wl0.2/wl1.1 all the virtual wifi interface if put in to the 'br1' bridge will not refuse to connect. Even after a router reboot

[mbze430]

okay I have done additional testing.

I would create the wl1.1 and left it (which is normally bridge to br0).

I would then connect a client into wl1.1. I would get my IP and connect successfully

After, I start a SSH session and at the command line I would switch wl1.1 from br0 to br1 'brctl delif br0 wl1.1 && brctl addif br1 wl1.1'

After issuing that command the client would still stay connected. and then on my laptop client release and renew a new IP and I would get a new IP from my vlan3. And I can access any website etc...etc....

HOWEVER, if I disconnect from the wl1.1 wifi and try to reconnect again, it won't let me.

So what can that possibly be?

PS: I also removed all my firewall tables and still does the same thing.

****UPDATE****

I just upgraded the firmware to DD-WRT v3.0-r39469M giga (04/10/19)
and it worked...the wl1.1 in br1 worked... but then after rebooting the router... stopped working.... getting REALLY frustrated here

[cvonk]

I just hit the same problem on build r41813, until I realized that I used to configure this using the CLI. My old writeup can be found at
http://coertvonk.com/sw/networking/dd-wrt-heading-two-networks-asus-rt-ac68u-11717

Let me know if that helps
/c

[cvonk]

As expected, wired Clients on Ethernet port LAN3 and LAN4 get an IP address on the Guest subnet. Traces from "tcpdump -i vlan3" and "tcpdump -i br1" both confirm this.

Clients on wl0.1 do not get an IP address assigned. Traces from "tcpdump -i wl0.1" and "tcpdump -i br1" both do not show DHCP traffic. The only traffic is some layer 2 messages. The same happens for wl1.1. However, "tcpdump -i eth2" show DHCP traffic for that client, and it get an address on my Main subnet (wrong).