The static IP address of the switch is the management interface. Not sure if the problem is related to this. I left that as default ticked in this VLANs tab. All ports can communicate with each other - no isolation. I have no port isolation configuration set up. If you tick the box for any row that means it will take into consideration any port isolation rules you have set up on the switch. In the VLANs tab image you will see a column 'Port Isolation'. The switch has a static IP in the subnet 192.168.1.0/24 - would this be the problem?Ģ.

I want to get it right this time.Ī couple of things occur to me but I'm not sure if they are the problem:ġ. The switch is online so this is not really an option. It is difficult to experiment with this by just trying different options because when I get locked out I have to use the serial port to gain access again, reset to factory default and then load a saved configuration. When I try to connect to the management port I make sure that the connecting device is in that subnet. On the VLANs tab (see below the port marked in blue) the port is included as a member of that VLAN only: It is enabled for VLAN egress filtering and for ingress it will accept either tagged or untagged packets for the VLAN. The proposed management VLAN port is set up for the port marked in blue as belonging to VLAN 1005. In MT SwOS VLANs are set up with two main tabs, VLAN and VLANs.

I'll offer more information on the setup below. I have not been working with MT equipment for long but, to the best of my knowledge, the VLANs config is set up correctly (apart, of course, from this problem of the management VLAN not working). Thanks for the suggestions taurex I really need to lock down access to the switch with this management VLAN.

Switch os mikrotik