now i would like ether 2 and ether 5 to act like ether 3,4 but on a different vlan (10), change bridge pvid to 10, enable allow only untagged and priority tagged and have vlan 10 ip 88.x
easiest thing to do is move the subnet OFF the bridge (just let it do bridging) and use another vlan instead…
In terms of requirements, think of them as use cases.
Determine the users/devices or groups of users/devices that need to be able to do tasks (talk to a printer, reach the internet etc).
Once those are all clear in your mind, then a configuration will be much easier.
If you’re connecting via IP (webfig, ordinary winbox, ssh, …), then moving IP address from one interface (bridge) to another (vlan10) will brwak connection for sure. If, OTOH, you connect via MAC (winbox where you click device’s MAC address), the management connection should survive changes in IP layer. No guarantee for survival of L2 changes though (those include enabling vlan-filtering on bridge).
A bit more sensible approach would be to create additional IP subnet on vlan10 interface (complete with DHCP server & co.) and only when you’re able to establish management connection over that subnet you drop old subnet from bridge. Nothing is forcing you to use 192.168.88.0/24 subnet in your LAN, you know?
sounds right… id like to access the router via its ip, so i i believe i need to type 192.168.88.1 in winbox
im doing some tests on a hap ac2 i had laying around. my pc is the only connected device
im trying to setup ether5 for winbox access but its not even getting ip via dhcp with the following config as soon as I enable VLAN filtering, set bridge PVID = 10 and enable ingress filtering (GUI). I also tried to set an ip manually (192.168.1.x) while connected to ether5 but i still cant connect to winbox
What I typically recommend,
is take an unused etherport let say ether5
rename it ether5-access
Remove ether5 from the bridge
add ether5-access to the LAN interface list as a member
give ether5-access an IP address of 192.168.5.2 network 192.168.5.0
Then setup your pc/laptop with ivp4 fixed of 192.168.5.5 with gateway of 192.168.5.1 and netmask 255.255.255.0
and you should then be able to access the router, and config the router regardless of what happens on the bridge…
(assumes LAN users have full access to the router via the input chain)