I'm unsure here. But I have two suggestions:

1. "system": we had it just there a few years ago. Then, at some point, it vanished from there and there must have been a reason for this.
2. "interfaces wireless": as it is a setting affecting all wireless LAN interfaces but would not be needed by anyone not using WiFi. So for the non-WiFi folks, this setting would stay out of their way.

I sent you a message on Slack, as a person with >10 Pull Requests, for us you are contributor and as such eligible for LTS images access.

I get it, not a bug then. Sad, but very understandable.

@alainlamar what's the preferred CLI command?

please see https://blog.vyos.io/community-contributors-userbase-and-lts-builds

https://github.com/vyos/vyos-1x/pull/3447

I finally managed to narrow this down further. This problem is caused by enabling the extended nexthop capability. FRR intentionally sends RAs when this capability is enabled, althought so far I don't understand why. I opened a discussion in the FRR repo: https://github.com/FRRouting/frr/discussions/15994

This would be a great feature to have. I ran into this the other day and found out via slack single-quotes works, but only for a one-liner. ex. set route-target vpn import '65000:1 65000:2'.

This will be possible after subtask T6006, for 1.5; backport can be considered at that time, but for now limit tags to Circinus.

Just so I dont get the vocabulary wrong here...