InThe currentent implementation of VLAN- aware bridges, is not perfect, and there are various problems in the implementation. all VLANs must be addressed through sub-interfacesNow, such as:let's modify the implementation of VLAN bridge to make it close to professional equipment.
```
set interfaces bridge br1 member interface eth0 allowed-vlan 2
set interfaces bridge br1 member interface eth0 native-vlan 1
set interfaces bridge br1 vif 1 address 192.168.1.1/24
```For a discussion of the VLAN aware bridge consensus, see T1354
However, due to the lack of verification,Implement the following settings can be made:design features
```1. Disable `vif 1` configuration
set interfaces2. When the VLAN aware bridge br1 address 192.168.1.1/24is enabled, the parent interface is always VLAN 1
```
This is inconsistent with the design specification and should be repaired3. This will also cause some misleading to the user.When `native-vlan` is not configured, There will be conflicts whenthe default behavior of the following settings exist:
```device is `native-vlan 1`
set interfaces bridge br1 vif 1 address 192.168.1.1/24
set interfaces4. The VLAN ids forwarded by the bridge br1 address 192.168.1.1/24
```are determined by `vif`
Edit: Modify tThe implementation, the following configurations are not a needs to be divided into the followed:ing stages:
```[ ] Modify the current implementation to meet the characteristics discussed in the new consensus
set interfaces bridge br1 vif 1 address 192.168.1.1/24
```
The VLAN ID of the parent interface of the bridge is always limited to 1[ ] This change requires modification of the document