We were also wrote below, please support IPv6 environment in Japan.
I am not even able to get for a hand to the user without this.
http://forum.mikrotik.com/t/7-0/79347/1
We understand that it’s a special situation, but please realize whether.
After that, I want you to also update the Kernel as SDN future measures.
And I want you to correspond to OpenvSwitch and OpenFlow1.3. OpenFlow is now very popular in Japan, to be able to use OpenFlow in CCR and cost-effective, because you can appeal strongly to the user.
Best regards.
+1
This function is mandatory in IPv6 environment in Japan.
MPLS TE Fast Re-Route
MPLS TE Link Protection
MPLS TE Link-Node Protection
MPLS TE behavior similar to Cisco Class Based Tunnel Selection
MPLS TE Diffserv-Aware tunnels
MPLS Segment Routing extensions to OSPF/ISIS
ISIS
Multicast separation of RPF table calculation into individual routing table and all things involved with that
Multicast BSR fixes
Multicast Anycast-RP
Multicast MSDP
64-bit for x86
Fast-Path indicator on each interface. Which traffic handlers are enabled or not enabled.
Graceful Restart for OSPF/BGP/PIM/ISIS (if ever implemented)
BGP multicast address family
Cisco IP SLA/Juniper RPM functionality
LLDP and LLDP-MED with integration into SNMP
BIG +1 from me on these two.
CCR Update presentation from MUM US '14 suggests improvements (complete rewrite?) to VRFs which sound like my other main request so hopefully with this effort we’ll see VRFs given better support with regards to RADIUS VSAs.
Just need a bit more effort with L2TP to make it work better with Mikrotik customers that buy wholesale PPPoE/PPPoA DSL services from aggregators delivered as L2TP.
+1000000
DHCP/RADIUS Improvements
-
Use dhcp.dictionary for DHCP-Radius
-
On DHCP renew check “running” settings against returned VSA’s. If any VSA’s have changed then update/add/remove relevant FIB/Queue/AddressList entries. On RouterOS 5/6 entries are added on a Request, then during renews only additional VSA’s are actioned, any updated/removed ones are not reflected in the running configuration of the router.
-
When running redundant DHCP servers/gateways (Authoritative Delay/Delay Threshold/VRRP), allow the option to have BOTH Authoritive and Non-Authoritive DHCP insert running settings from VSA’s, this will allow the primary to fail and have the secondary take over with the same FIB/Queue/AddressList entries. Currently this does not work, if the primary DHCP Server/Gateway fails the Backup will become Master but none of the VSA settings will exist, and due to the above issue will never be created, causing a potential lack of service when running from the Backup router due to lack of FIB entries, or potential other issues due to lack of Queues or Address-List entries.
-
Make default behavior of RADIUS VSA’s on RouterOS compliant with RFC2865
Zero handoff roaming between capsman units,
Also wolud love to see load balancing also between bands from 2,4ghz to 5ghz as on aruba networks becouse now I have to buy really expensive Aruba acess points to do this.
I also vote for more Radius-Attributes/Replies such as:
- local-address
- dns-server
- VRF/routing-table
IKEv2 for IPSec
It would better if we can make the Webfig skins work better in V7.
Now there are bugs on particularly the Quick Set page.
I was configuring a RB951 for a client and I wanna give him only the right to change his guest network password on the Quick Set page when he logs in from Webfig. So I tick off all other pages. But then on the Quick set page there are ton of stuff to tick off. And they seem to come from different mode settings of the router. And even I tick them off, the page still wouldn’t work properly.
Not sure if this is the right place to post about this. My apologies if I’m wrong…
Queues.
will be nice if in simple queue be possible add ip ‘‘from-to’’ like 192.168.3.10-192.168.3.64
Thanks.
I need this too for easy VPN from Windows Phone 8.1
It should be possible everywhere where ip address field is used as condition or restriction.
I actually just miss one “feature” in RouterOS 5/6 and it would be awesome to have this in 7: IPv6! .
The current state of IPv6 in RouterOS 6 is maybe partly usable for home users, soho applications, etc. But in no way is it safe or depending on the configuration even possible to use MirkoTik for service provider applications with more than one router.
The reason I put feature in “” is because you cannot name it feature when they officially support ipv6 and 50% of all protocols and services are not or only partly working for ipv6, then those are bugs!
Just to name some missing “features” / bugs in IPv6.
- IPv6 bgp recursive next-hop. This is a must for any redundant IPv6 service provider backbone! static routes are no alternative!
- ipv6 blackholing - there must be a way to blackhole the prefix I announce to my upstreams. I simply don’t want any TTL exceeded and routing loops! unreachable routes are no alternative!
- efficient ipv6 routing table lookups on cli (e.g. /ipv6 route print where dst-address=8.8.8.0/24)
- testing of ipv6 functions and protocols prior to release! basic stuff like VRRP working in one release and then totally unusable in the next release… come on…
besides IPv6 it would be really great to have working VRF implementation and be able to use it to separate the management plane from the production / customer traffic. currently there aren’t any really VRF aware management services like ntp,netflow,ssh,winbox,etc.
In general, I really suggest that MikroTIk reconsider their strategy about software releases and pricing. I would be happy to pay 50% more for the bigger routers like CCRs and in return have a more stable software, means that they differ between bug fix releases and feature releases and also test and bugfix before a release. I mean I totally understand that new features sometimes show bugs not before production use, but stuff that’s there for years and suddenly don’t work in a 6.x release, come on, you can do this better!
Pls Add functionality to NetWach like this:
Down script, if not available within X times.
Up script if available within Z times.
Now X and Z = 1.
-
Support for SHA2 Hashs.
CAs starting to only hand out SHA2 certificates and browsers will drop SHA1 soon. I’m kinda wondering why this hasn’t already been brought up… -
Openflow 1.3
This might be a bigger problem, but it would really be a big advantage being able to integrate RouterOS in SDN environments. I don’t know anything about the code-base but maybe it’s possible to add an ovs client and help them with the OF development?
You can already use sha256 and sha512 in ipsec phase1. Depending on requirements can be added to other facilities as well.
MAC Address List Support 
thanks mrz for the info.
I will give that a try. Since I won’t have time this year I will give it a look next year.
What I currently need this (SHA2) for is for VPN connections (sstp, pptp, openvpn). Since October my CA only hands out SHA2 certificates.