VLAN IDs weird after upgrade

RouterOS Beginner Basics
1

Recently I’ve upgraded my two RB951 from 6.37.4 to 6.38.1. While they work just fine (I’ve had some issues if I only upgraded one, it wouldn’t talk to the other), I’ve spotted some curious behaviour.

My setup includes a few VLANs and every switched port has slightly different VLAN setup. Some ports are trunk ports while other are mixed trunk/access and their definition is like this:

set 0 vlan-mode=secure
set 1 vlan-mode=secure
set 2 default-vlan-id=42 vlan-header=add-if-missing vlan-mode=secure
set 3 vlan-mode=secure
set 4 default-vlan-id=2 vlan-header=add-if-missing vlan-mode=secure
set 5 vlan-header=add-if-missing vlan-mode=fallback

If I focus on the port number 3 and check it’s definition in the web GUI, page Switch → Port in the properties table “Default VLAN ID” is said to be 4294967295 for this port. If I click the port to get configuration page, the “Default VLAN ID” filed name is red and the value is the same insane value. If I remove this setting (by clicking up-arrow on the right side of field name), the port starts to misbehave … I can’t tell the exact way of misbehaviour as I usually loose connectivity to the device itself, while some traffic still seems to be flowing through.

I don’t remember what was the setting in ROS 6.37.4 (and previous), but my gut feeling is that the setting was empty (that somehow makes sense according to what I wanted to do on that particular port).

A side question: on the port 5 (that’s switch cpu) the mode is fallback … I don’t really undestand the peculiarity of that particular setting, should I define a default VLAN ID there?

2

See the documentation page http://wiki.mikrotik.com/wiki/Manual:Switch_Chip_Features for a description of what “secure” and “fallback” means.
The number 4294967295 is the maximum 32-bit unsigned integer. When it appears, it usually indicates a misrepresentation of the number -1
as this signed 32-bit integer has the same bit pattern. And -1 is often used in cases where “not in use” is meant.
I have reported that there are some user interface errors like this in the 6.38rc and now 6.38 version and they promised to look at it but
it apparently still has not been completely fixed. Just ignore fields that have this problematic values and if it leads to configuration entering
problems use the command-line or winbox interface instead.

3

Thanks for the feedback about WebGUI bugs, I feel much better now :slight_smile: . I would rather use winbox for the management as well but I have problems to run it on any of my windows boxes. I can only get it working in linux with wine … and linux is either in virtual machine on my windows box or on a linux machine that always sits on the other side of RB device which badly needs managerial kick and is thus unaccessible just then. Either way it’s PITA.

I’m thinking about that “VLAN mode=fallback” setting and I’m starting to understand that I’ve set that just to keep myself from locking me out from management (pseudo) interface of the RB device :confused: