Feature requests

Added another request: logging of interface status changes.

Rough example: 29 Oct 2010 16:02 +10:00 Interface ether1 changed from no link to connected 100/full (auto)

This is extremely useful in other managed switches so that you can see if a particular device is losing physical connection or changing speed/duplex for no good reason.

We already have that in RC2

Good stuff!

Apologies for the duplicate, but did not see this anywhere in the changelog.

I posted about it in the 5.0rc2 thread, but, it seems its simple in what it logs (up/down status without speed and duplex).

Edit: Actually, would I have to make logging more verbose, perhaps, in order to get speed/duplex logged?

in what cases does your link speed change without unplugging the cable? is it really so often that you need special log entry?

Er, not without unplugging. I mean when I unplug the cable and plug it back in.

On 5.0rc2 on RB532 (mipsle), this is all I get by default (no speed+duplex info logged; only down/up status):

/log print

10:12:18 interface,info ether3 link down
10:12:22 interface,info ether3 link up

If there is a way to get it to show the speed and duplex, I’m not sure how to do it at the moment.

yep, it would be nice… like on managed switches:

2010-10-27 22:25:28 INFO(6) Port 3 link up, 1000Mbps FULL duplex
2010-10-27 22:25:01 INFO(6) Port 3 link down

Not often, but handy to know when customer is calling you asking about bad link performance :slight_smile:

If you’ve already gone to the trouble of putting in logging of up/down status: whats the harm in also putting in speed, duplex and auto/manual negotiation also?

My request is for a “Auto Roll back” option for upgrades?

(1) full backup is stored on the router,
(2) after uploading upgrade you reboot but…
(3) if for whatever reason the new upgrade caused loss of connectivity or you may have forgotten to change a setting before you clicked reboot …
(4) having a default 5min countdown to restore on reboot,the router will automatically restore the original configuration back,
(5) if no loss of connectivity you can stop the countdown to restore original OS,
(6) the roll back file remains stored on the router, this for fast restore if say after a few days the upgrade has created new issues?

What i am suggesting is similiar to video adapters when you change display setting it automatically restores back after 15seconds if “use” new setting are not clicked,
If you cannot access the router to stop the countdown then wait 5mins and your router will auto roll back to the original OS before upgrade and connectivity should be restored?

mpls ecmp support ( forward using two or more destinations even using mpls)
bgp support ldp

Win box

Drop down box for last 10 (or more) IP addresses visited

Ability to use more options of the VPN server (like those normally speficied in the .conf file of the OpenVPN server when running on Linux)
For me presonally the following option would be really nice:

push “redirect-gateway”

It has been discussed here:
http://forum.mikrotik.com/t/openvpn-server-options/41772/1

I would like to set the timeout for pppoe-client connection, which sometimes takes longer to connect. If it is possible to set a time delay that is used to connect each time after a disconnect.

http://forum.mikrotik.com/t/i-can-not-connect-isp-using-pppoe/41959/1

pppoe client connection by winxp

pppoe-client can not connect by RouterOS.

pppoe-client disconnect modem before RouterOS will receive packet

We have some sites that are very noisy RF environments, and they occasionally screw up ethernet links. We’ve tried various remedies, which I won’t go into here, as this isn’t the appropriate thread for it, but it would be handy to have logging of the speed/duplex for us as well.

It will be good if RouterOS will have integrated brute force protection and filter.

It does

http://wiki.mikrotik.com/wiki/Bruteforce_login_prevention

I would be nice that in /ip service I could set more ip address or one addres-list

use firewall in that case

I sorted the feature requests by number of votes: http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/Feature_Requests

thanks, much clearer now.