Tue Jun 01, 2021 11:14 pm
It is quite common to setup up bridges on microtik devices for everything but the wan etherport.
In this case you want to include the wan etherport for the purposes of carrying vlan-voice to the second router.
The internet vlan is NOT associated not with the bridge but to the port itself and just needs to have the correct vlan-id that the ISP is providing.
By sticking this into the dhcp client the router then knows what to do, and by assigning the vlan as an interface member for WAN, the router can handle other issues such as firewall.
The voice vlan like any other vlans assigned on the hapac (you may want one for normal home traffic, one for iot devices, one for guest wifi etc.......) is attached to the bridge.
The vlans provide their own dhcp etc............... not the bridge.
The voice vlan just needs to be defined with the correct vlan-id number with interface being the bridge (no dhcp or pool). so that it can be picked up from ether1 and go to ether X (where X is the port leading to the ISP router).
There is no issue at the ISP router, it doesnt care about names or anything else, it will see the properly tagged frames on the incoming stream, from the Mikrotik, into its wan port and will know how to deal with this traffic.