Joined: 16 Sep 2019
|Posted: Tue Sep 17, 2019 11:45 Post subject: Configuration of STP bridge doesn't work on v3.0-r41027 std
|There seems to be an issue since the first betas which persists in the current build (v3.0-r41027 std), when running on an ASUS-RT-AC68U.
Scenario: add a new virtual wireless to a new bridge configured with a DHCP server.
* Wireless: add new virtual wireless interface (wl1.1)
- AP Isolation: disable
- Multicast To Unicast: disable
- Network Configuration: bridged
* Setup, Networking: add a new bridge, add the virtual wireless interface to it and map a new DHCP server:
- Create new bridge:
> name: br1
> STP: STP
> IGMP Snooping: off
> Prio: 32768
> Forward Delay: 15
> Max Age: 20
> MTU: 1500
> Root MAC: 38:2C:4A:E2:D6:B0 (same as br0's)
- Network Configuration br1:
> TX Queue Length: 1000
> MTU: 1500
> Multicast forwarding: disable
> Net Isolation: disable
> Forced DNS Redirection: disable
> IP Address: 192.168.11.1
> Subnet Mask: 255.255.255.0
> L2Mesh enable: unchecked
- Assign virtual wireless interface (wl1.1) to the bridge:
> Assignment: br1
> Interface: wl1.1
> STP: on
> Prio: 128
> Path cost: 100
> Hairpin Mode: unchecked
- Add new DHCP server for the new bridge
> DHCP 0: br1
> Start: 128
> Max: 50
> Lease time: 1440
Clients cannot connect to the configured wireless because the interface wl1.1 doesn't stay up.
The log file shows repeatedly:
Sep 17 01:41:33 router daemon.info mstpd: set_if_up: Port wl1.1 : up
Sep 17 01:41:33 router daemon.info mstpd: error, ethtool_get_speed_duplex: Cannot get speed/duplex for wl1.1: Not supported.
The message in the log file is informational, indeed. But it must be related to the incapacity of clients to obtain an IP address when trying to connect to the virtual wireless interface. If I bind the DHCP server directly to the interface (unbridged mode), it works. But not when using a bridge.
I hope that I've provided you with enough information for this issue.