The VLAN interfaces giving the CPU to access VLANs in /interface vlan must be attached to the parent interface not members, so bridge not ether17.
That setup will work, but will not use hardware switching.
That makes sense, there isn't an equivalent of the NWay copper link negotiation for fibre.It was on fiber, come to think of it, not copper.
That syntax is incorrect. As mentioned above, and in the description of routes here https://wiki.mikrotik.com/wiki/Manual:P ... operties_2, it should be 192.168.10.0/24 0.0.0.0 50Already tried that with 192.168.10.0/24 50
.... dynamic route distance is still 1
It's enough that I've lost switching possibility for ether1 after some prior upgrade (from 6.3x.x to 6.4x).
All zeros for the host address is somewhat unusual, so may be a bug.Example what I am trying that is not working: winbox to IPv6 Mikrotik ---> [2605:4e40:0:1fe::]:8295 (this does not work)