Feature request: move all configuration related to one physical interface to another.
E.g. you have a router with two hardware switches or with ports inside/outside switch.
You have configured e.g. ether8 which is on switch2 with all kinds of options (address, dhcp server, firewall config, etc)
and you decide it would be better to move all this to ether4 which is on switch1, e.g. because you want to free up a port
that is on switch2, to do hardware switching to the other ports on that switch. It would be convenient when this could
be done with a single command, just like an interface can be renamed with a single command and it is reflected everywhere
in the config. After issuing that command and plugging the cable from port 8 to port 4, all functionality would remain the same.
For practical purposes (what would happen to the config that was on port 4), maybe the easiest implementation would
be in the form of “swap interface configurations” What was on ether4 will be on ether8 and vice-versa.
When adding an adress in large adress-list is a PITA when an address already exits. The the script is stopped an you can work with on-error to seek sequential through the list use set to update it timeout on the dynamic address. This takes ages when you have to seek each time.
On the moment you get collision it would be a pleasure to be able to directly use set on that entry to set the expire time in the on-error.
I find that Userman is a really good choice to build a hotspot service for a company, but i think, as installer, that there is something missing, few things like embedded sms verification (and not the script), and the one that i found more interesting, make the userman database readable (just think about a company with a newsletter). All could be added to make userman like a serious radius server (chr would allows more performance for anought clients). more competitive !
Thats all 
Regards from an Italian user
Please add the ‘Comments’ column and the ‘Add/Edit Comment Button’ which is currently missing in WinBox 3.11 under
Routing =>BGP => Networks
Routing => BGP => Aggregates
Interestingly it is available in Routing => OSPF => Networks, but missing in all of the other tabs
While I personally prefer the CLI for configuration, WinBox is nice to get a quick overview.
Thanks
Please add SMB support to the fetch tool or the ability to limit FTP accounts to specific folders to the FTP server. The SMB server is considerably more advanced than the FTP server on Mikrotik and makes it easier to limit clients to a specific folder.
/queue tree elements can now only match on “packet marks”, when multiple packet marks are specified they are OR’ed.
Please add the capability to also match on the “packet priority” field, and make it an AND match with the packet marks.
(so if a queue tree element is specified with both packet marks and a priority, it will only be used when one of the specified packet
marks is present AND the priority field of the packet is as specified)
Alternatively, introduce the option of doing an AND match on packet marks. It is already possible (although cumbersome)
to add packet marks based on the packet priority field.
We are deploying Mikrotik virtual appliances to centralize and replace several disparate VPN solutions. We need a way to hand out our domain suffix to VPN clients so they won’t have to use Netbios broadcast to resolve names. Currently, without domain suffix setting, accessing hosts by hostname takes about 5 seconds longer than it does on our existing legacy VPN solutions. I Googled the issue and see people complaining about this all the way back to 2010. However I do not see it anywhere in this Feature Request thread. Longstanding issue - please help!!
David
Normis add /31 address for PTP links.
/ip address add interface=ether1 address=192.0.2.2/32 network=192.0.2.3
Do You maybe have in plans to make more detailed user group list? Different user access to i.e. wireless, firewall filter, nat rules, ip addresses, dhcp and etc. I imagine it may be hard to add databases and additional cunfiguration to every configuration field. Maybe any possibility to add at least additional wireless user option. Clients sometimes wants to change wifi name, password, but we do not want to allow to change other options with given password.
Being able to customize the hAP WPS button behavior, like having it trigger a script.
(our use case would be to easily turn the Wi-Fi on/off)
Hey, Mikrotik team!
Please extend “netwatch” funtionality a little bit. It is a nice feature, but so undeveloped.
It will be nice to have an option to set amount of ping to send before change status to down and at its frequency.
… and routing table/vrf 
Make Address List from DHCP lease table!!
For example - select multiple LEASE entries and put them in address list (then you can use for firewall)!! Something like in wirelless - you can add entries from registration table to access list!!
Thansk!
Lease script doesn’t work for you in this case?
Looks like he needs it in WinBox (one-time context menu like ‘Make static’ or something)
By the way, if your leases are static, you can just set ‘Address List’ for them
..and the possibility to set source address (e.g. remote ipsec hosts)
Netwatch can trigger a script.
Example - my netwatch:
/tool netwatch
add comment="Watch Dog" down-script="log info "Netwatch missed a ping to 192.0.2.254 - starting 5 minute timeout script" ; /system script run NetWatchBoot-192.0.2.254" host=192.0.2.254 timeout=1s500ms
Example - My script called by netwatch:
/system script
add name=NetWatchBoot-192.0.2.254 owner=admin policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive source=":local addresstoping 192.0.2.254;
:local addresstoping 192.0.2.254;
:local interface "wlan1";
:local continue true;
:local counter 0;
:local maxcounter 28;
:local sleepseconds 10;
:local goodpings 0;
:log error "-----> Tom's Netwatch-Script-Warning - Netwatch could not ping $addresstoping - Will begin further testing in $sleepseconds seconds - and will continue for $maxcounter times $sleepseconds seconds";
:while ($continue) do={
:set counter ($counter + 1);
:delay $sleepseconds;
:if ([/ping $addresstoping interval=1 count=1] =0) do={
:log info "----->ping to $addresstoping failed on attempt $counter of $maxcounter -- Will try again in $sleepseconds seconds";
} else {
:log warning "-----> ping success on to $addresstoping attempt $counter of $maxcounter <----- No Further testing needed --- Program will exit -----";
:set continue false;
:set goodpings ($goodpings +1);
/interface wireless monitor $interface once without-paging do={
:local status $"status";
:local band $"band";
:local freq $"frequency";
:local wprotocol $"wireless-protocol";
:local noise $"noise-floor";
:local signal $"signal-strength";
:local snr $"signal-to-noise";
:local thruput $"p-throughput";
:log info "-----> Status: $status --- Band: $band --- Frequency: $frequency --- WProtocol: $wprotocol --- NoiseFloor: $noise";
:log info "-----> Optional Info if Available ---> SignalStrength: $signal --- SNR: $signal --- PThroughput: $throughput";
/interface wireless monitor $interface once
:local txr $"tx-rate";
:local rxr $"rx-rate";
:local sstr $"signal-strength";
:local signoise $"signal-to-noise";
:local curdistance $"current-distance";
:local txccq $"tx-ccq";
:local rxccq $"rx-ccq";
:log info "-----> TxRate: $txr --- RxRate: $rxr --- SignalStreng: $sstr --- SignalToNoise: $signoise --- CurrentDistance: $curdistance --- TxCcq: $txccq --- RxCcq: $rxccq";
};
}
:if ($counter=$maxcounter) do={:set continue false;}
}
:if ($"goodpings" = 0 ) do={
:log info "-----> Rebooting in 15 seconds";
:delay 5;
/file print file=ScriptRebootReason
/file set ScriptRebootReason.txt contents="Rebooted by Toms script on $[/system clock get date] at $[/system clock get time]"
:log error "-----> Rebooting in 10 seconds";
:delay 5;
:log error "-----> Rebooting in 5 seconds";
:delay 5;
:log error "-----> Rebooting now";
:delay 1;
/system reboot
/system reboot
/system reboot
/system reboot
}
With the above - a netwatch ping failure will trigger my script "NetWatchBoot-192.0.2.254"
The script will retry the ping for (:local maxcounter 28) 28 times
While pausing (:local sleepseconds 10;) 10 seconds between pings
If the script gets a ping response, the script aborts - and make a log.
If the script loops through the count-down and does not get a ping, the script will reboot the Mikrotik - and make a file named ScriptRebootReason just prior to the reboot.
I am sure this netwatch & script procedure could be modified to do many things you may want when netwatch triggers.
In my case, I have this netwatch & script on all of my Mikrotik client devices and all of my internal core network Mikrotik devices. The IP address 192.0.2.254 is an RFC IP address and is OK to use for in-house (non-external-Internet-Routed). If I want to reboot every Mikrotik everywhere on my network, all I need to do is disable the 192.0.2.254 device a few minutes. Presto - everything everywhere will auto-reboot. This is good for keeping Mikrotiks on-line when the network might have a problem.
North Idaho Tom Jones
Selectable auth mechanisms for RADIUS-based AAA on system login.
currently it varies based on the access vector, and Winbox requires chap which requires reversible cryto / plaintext password store.
Or add LDAP auth client, but I’m sure simply allowing MS-CHAPv2 / PAP as auth mechanisms for existing RADIUS would be a much easier solution.
+1