*) fetch - added "as-value" output format; Assuming this is still the same functionality as described at https://wiki.mikrotik.com/wiki/Manual:Tools/Fetch#Return_value_to_a_variable , I am surprised to find that when I do this: /tool fetch mode=https host="mikrotik.com" url=&quo...

Thanks for clarifying EdPa ‒ indeed, the description really didn't make that behaviour clear! I see now the behaviour essentially provides that of a trunk's 'native VLAN' to borrow Cisco/others' parlance. The change you've made to the wiki is definitely an improvement, thanks, but may I suggest an a...

Thanks for your response EdPa. That certainly makes sense, and I would have assumed it to work this way had it not been for the line in your documentation that reads as follows, taken from the table at https://wiki.mikrotik.com/wiki/SwOS/RB250_RB260#VLAN_Tab : Switch will treat both untagged and &qu...

Thanks for your reply. Certainly I see the need to tag on the trunk port, no question about that. However from my screenshots and the docs I would expect, as you suggest, for the traffic to be thrown down the trunk untagged (and thus not work, dependent on the pvid at the other end anyway). As I say...

Hi, I'm hopeful this is an easy one for someone. I'm struggling to understand why egress packets are being VLAN tagged in a particular circumstance. I have an old-model 260GS running SwOS 1.17. I have a computer attached to an access port, and then a (incorrectly configured IMO) trunk port heading o...

Spotted the following on Superuser today, and it accurately describes what I’m seeing on the last couple of releases (potentially since 6.41.0) – the WiFi interface will just ‘stop’ at random, nothing in registration table, 0/0 tx/rx. Restarting the interface or doing something like using the ‘Scann...

I've also observed this with a CAPsMAN security config – with the group key update set to one hour, it seems to occur every 40s or so (watching in Wireshark). If I unset the value to restore the default, it happens every five minutes.

There are various topics on these forums already which touch on problems with iOS devices in combination with ROS WiFi. Of these, this one is the most similar to the issue I'm experiencing. I thought I'd start a new thread as times have changed, and quite a lot of its content turned out not to be ve...