It's already fixed with this script:Since 2013 MikroTik promises to fix bugs with v7 (recursive ipv6 nexthops etc)
There is only arm and head, it lacks all the rest of the body!2 years ago the ROS 7.0 was on alpha 134:
https://mobile.twitter.com/mikrotik_com ... 4195920896
Why don't you just use RADIUS? I wrote a TACACS server for dial-up connections early in 1996 ... switched to RADIUS around year 2000.I would be cool if TACACS/TACACS+ would be supported in next ROS version. Is it planned in ROSv6/ROSv7 or not?
It is what I am doing already since a while!Until then I'll sit on my chair and wait while clicking refresh button on mikrotik download pageRouterOS v7 is currently in early alpha and there is no scheduled release date yet.
Just a small advice: if you need NAT on IPv6 you are doing something wrong...For more than 3 years I'm waiting for v7 as I really need IPv6 NAT and this feature is there since 3.9.0 Linux kernel (but v6 has 3.3.5).
The comparison isn't appropriate. There has ever been a stable and good windows release?[...] and the product was released as Windows Vista, arguably the biggest disappointment ever in Windows releases [...]
You have never been a programmer. Test software is far from perfect. Complex software can easily include deadly bugs. If you don't want your device to lock up, don't use RC, there are other two branches that suit you better.I have every right to complain if the software locks up my router !!
I think that the most important things are:What we all want is:
better fixing/ vertical adjusting
Closed antenna design => no snow and dust etc...
What we are asking is not an exotic feature, it's basic IPv6 functionality...It is no trivial task developing a new routing engine, adding major new features and testing all the corner cases, all the while maintaining the existing code base and back porting drivers so you can release new hardware.
Wonderful! Good job Mikrotik!What's new in 6.34.1 (2016-Feb-02 14:08):
*) interface - fixed stats that were 8x smaller;
*) traffic-monitor - fixed stats that were 8x smaller;
*) smips - properly detect smips boards for winbox & webfig.
Is it too much asking for a v6.34.1 with the fix? Using an RC in production environment sounds a bit scary...Graphing and SNMP related issues are fixed in 6.35rc3 version:
*) interface - show stats properly in bits not bytes;
Probably graph counters show less traffic because the code that hides traffic generated by the new backdoor includes also normal packets... (just kidding).After several months and after a lot of rc release of new major version is full of basic errors. (GRAPH, SNMP, etc.)
Yeah!! Very useful!6.33rc16 will be released today.
*) ppp - added on-up & on-down scripts to ppp profile
Confirmed, it happens to me too, tested on 6.24 through 6.30.2.Another bug:
Selecting multiple routing filters and trying to move them up or down, will only move one random rule of those selected instead of all of them.
Most of my CCRs don't have the NTP package installed, and they all crashed badly.Am i right to say that only CCRs with NTP package installed and configured was affected?
This bug has been fixed twiceWe have plans to release v6.29 during this week.
*) queue tree: some queues would stop working after some configuration changes;
*) queue tree: some queues would stop working after some configuration changes.
I have more than 20 in production and never had any single issue.Is anyone else seeing this or is it just a run of bad luck with the new CCR-1009's?
I can confirm that the issue with CCR1009 routers is fixed on 6.17.We just published v6.17, which includes CCR1009 fix for port issues that caused crash. No other changes included, thanks everybody for quick reports that allowed us to immediately release a fix!
[/quote]I hope you read this:
http://forum.mikrotik.com/viewtopic.php ... 50#p432113
Of course, everything can be done... but using the "area" information it doesn't require any maintenance at all!Really you can change and mantain MAC address between each replace....
I am using a CCR-1036 with 3 peers with a full view and as a route-reflector for ~50 RR clients. One core is constantly at 100% CPU and BGP updates are very slow. Hope it can be parallelized.+1!! Any news about it?Are there any plans to make the BGP process multi processor capable?
Sure, but if you add "KiB" at the end (that it is what "/ip dns export verbose" outputs), the command is not accepted, it's a (small but annoying) bug."/ip dns set cache-size=2048"
If your customers flap (which is something quite common, expecially when they change configurations), with dampening active, you avoid to propagate flaps to the peers.this dampening is protecting your infrastructure not the others from your BGP announces ?
Can you pass IPv6 network routes to attached PPPoE clients assigned through Radius?It works here (ROS 5.4). I just miss dynamic ipv6 address-lists.I am impatient to see full IPv6 PPPoE-server support in ROS. I would allow me to throw away several ciscos.