As a guy who is always aiming the future of internet, I think Mikrotik team should give some more focus on improving IPv6 funcionality in RouterOS, because IPv6 is right here, right now, it is working, and it is already the new Internet Standard; so, I've opened this topic for suggestions, and debate about how RouterOS' IPv6 can become better. Here is what I miss when using IPv6 on RouterOS implementation:
- VRF (i.e., also mark-routing and routing-mark) support for IPv6 (I've seen a long long time ago (about 7 years or more) an old topic with someone answering that Mikrotik team can't have VRF implementations because of Linux Kernel not properly supporting it on IPv6);
- Radius integration with DHCPv6-PD delegated prefix, and IPv6 Firewall Address-list manipulation in Radius, it is useful in many ways (this is actually what freezes me on implementing IPv6, the inability to properly work this functions with Radius server);
- Customizable lease-time for dynamic DHCPv6 servers, created by pool, for example (the actual 'default' is 3d 00:00:00);
- /127 implementation (as I said before, harmful or not, it will continue to be optional, but having it, makes Mikrotik compatible with more network scenarios, and equipment);
- IPv6 VPN services support (I don't know what exactly work or not with IPv6 addresses, but, I remember trying to configure SSTP with IPv6 address, and failing).
Any suggestions, clarification, agreement or disagreement are welcome, even better if it comes from Mikrotik team.
Re: Customers suggestions to RouterOS' IPv6 module
It will be fixed with RouterOS v7 (TM)
Re: Customers suggestions to RouterOS' IPv6 module
I have to add that: the option to define preferred source address for each routing is very interesting too, and I miss it when I use private IPv6 to do point-to-point (fc00::/7), and the router tries to generate traffic to internet using fc00::/7, and, of course, it fails. Example:
With the example above, when I try to ping IPv6 internet using router, it uses the IP fc00::2 (that is private) instead of using 2001:db8::c001. With the following, it will work correctly:
Code: Select all
/ipv6 addres add address=2001:db8::c001/64 comment="Public network" interface=ether1;
/ipv6 address add address=fd00::2/126 comment="Private serial link" interface=ether2;
/ipv6 route add gateway=fd00::1 distance=254 comment="Default route to private gateway";Code: Select all
/ipv6 addres add address=2001:db8::c001/64 comment="Public network" interface=ether1;
/ipv6 address add address=fd00::2/126 comment="Private serial link" interface=ether2;
/ipv6 route add gateway=fd00::1 distance=254 pref-src=2001.db8::c001 comment="Default route to private gateway";
Re: Customers suggestions to RouterOS' IPv6 module
IMHO IPv6 is a dead concept.
Either IPv8 comes to life or I will die before being forced to use IPv6...
Either IPv8 comes to life or I will die before being forced to use IPv6...
Re: Customers suggestions to RouterOS' IPv6 module
I feel sorry for your cancer, man. But, perhaps, before you die, you should read this: https://tools.ietf.org/html/rfc8200. The relevant concept about it is: "the IP version 6 is the new internet standard."
Re: Customers suggestions to RouterOS' IPv6 module
What is the forecast for release of version 7?It will be fixed with RouterOS v7 (TM)
These features are extremely important to many ISPs.
Re: Customers suggestions to RouterOS' IPv6 module
Heh, you're new.
"Fixed in v7" is a euphemism for "it will be a while", or less optimistic, "it will never happen".
"Fixed in v7" is a euphemism for "it will be a while", or less optimistic, "it will never happen".