wifiwave2 configuration.country on slave

I was on my iphone in the Mikrotik app and noticed in the Quicket that a guest wifi table entry (interface?) had the country set to Afganistan.

I’m in the United Stated.

So I went into Winbox and the master table entry is set to United States, but the slave entry does not have a field for Country.

So I went to terminal and tried to enter it.

[admin@630-hAPax3] /interface/wifiwave2> set Guest-2ghz configuration.country="United States"
no such item

I then tried several other countries and received the same response.

It would be reasonable for the slave entries to take the country from the master.

But the app’s quickset-type access specifically shows the wrong country.

So I went back to the app and set the slave in the Quick setup to “United States”

Winbox then shows the following log entry:

device changed by tcp-msg(winbox):admin@192.168.2.120 (/interface set Guest-2Ghz; /queue interface set Guest-2Ghz; /interface wifiwave2 set [ find ] configuration.country="United States"; /interface wifiwave2 actual-configuration set Guest-2Ghz configuration.country="United States")

Bug or feature?
Screenshot 2023-09-20 at 5.05.36 AM.jpg

Setting country correctly is important for AP to adhere with local regulations about permitted frequency channels and permitted Tx power. And when configuring virtual wifi interfaces, country informaiton is only meaningful on master interface, that’s the interface which drives radio chip; virtual interfaces are piggy-backing on master interface. And it’s only logical that setting country on virtual wireless interfaces is not possible (because it should not override setting on master interface).

The secondary effect of setting country is to show that info over the air to clients. I guess this is where problem lies. Either ROS sends out wrong value (or not - after all, Afghanistan was de-facto ruled by US between 2001 and 2021 :wink:) or ROS sends invalid value and then client interprets it incorrectly.
If this bothers you enough, create a supout.rif and open a ticket with support. The response might be interesting.

Thanks for the detailed explanation. Makes perfect sense.

It doesn’t bother me at all.

Just trying to figure out why I’m getting lots of wifi disconnects.

For troubleshooting, I removed the virtual child/slave wireless interfaces and was able to connect with stability to the main wifi1.

There are quite a few threads on wifi issues that go back quite some time and include quite a lot of troubleshooting dead-ends.