How to disable/enable client radio remotely

RouterOS Beginner Basics
1

I’m looking for various ways to do this.

I was able to log in and disable the ethernet1 port. I can then get back in through winbox via mac as the ip address shows all 0’s. The client had been back feeding dhcp.

What are some other ways to disable/enable a radio remotely or is this the most obvious?

2

If you don’t mind losing CPE connectivity, you could prohibit the radio from registering on the AP.

/interface wireless access-list
add mac-address=00:15:6D:12:34:56 interface=all authentication=no

Otherwise your solution would work, but it’d be a bit troublesome to automate.

3

Write a script.

First line of the script will disable whatever interface you want, put in a :delay of however many seconds on and then enable it with the last line.

You can either schedule this to happen, have another script call it when it sees a fault, or run the script by logging into the device.

4

Thanks, I need to maintain radio link so I can turn it back on. I’d rather not have to drive out once the trouble is resolved. It should be a temporary solution.

I am more used to canopy which has an ethernet kill switch that leaves the radio up and is still accessible via ip. Looks like doing the above and logging in via mac in MK will work just fine. :slight_smile:

5

The solution I posted does not disable the radio link, just prohibits registration. The CPE will constantly scan for an AP which will allow it to connect. As soon as you remove the rule on the AP the CPE should gain access to the network again.

We use this solution in our network and it works well.

6

For demonstration and collaboration functions, two administrators can share a sitting. Additionally, an administrator can also remotely connect to the real console of a server by using the -console control.

7 



/interface wireless disable [find name="WLAN"]
:delay 30
/interface wireless enable [find name="WLAN"]

The script will turn off the radio and then turn it back on for you. Definitely test on a test box before putting it on a production box. I also understand, I wouldn’t want to drive out there if something gets messed up. It always makes me nervous disabling interfaces/services when I’m not on site to fix it if something goes wrong.