I would like to know what is the demand for Ipv6 support in RouterOS and how far you would like it to be supported. So if you are interested, please post something. Also you can post what exactly you expect from Ipv6 in RouterOS. Any kind of response on this topic is very welcome
We will be very pleased to see IPv6 working on Mikrotik.
(but at first please make BGP → ospf distribution runnable)
I think it is going to a must for routing OS-
So, go on!
Please don’t forget QoS at wireless level also.
IPv6 is becoming critical for us, while i’m still picking a few things up the abilty to run a pure ipv6 network with no ipv4 stack would be great. For legacy clients the ablity to run a ipv4 LAN with a ipv6 realworld ip would be needed and likewise the ablity to map RW ipv4 ip’s to the networks ipv6 address would be also needed to allow clients running ipv6 to access ipv4 resources and still retain their own ipv4 address
We are currently working with a client on a bid for a build…one of their requirements is that the network be capable of IPv6, or at a minimum a garanteed upgrade path to IPv6 via software/firmware. We are sort if counting on Mikrotik to have this at some point as Mikrotik will be our preferred platform for this network (and most others too).
I think by adding this it will only give Mikrotik a leading edge over the competition as well. At some point, it’ll be required anyway (as far as being competitive). We will need it sooner than later.
So, I vote yes please 
It is for the time being a requierment that make difference between last time equipemnts and futur equipment ready for scalability an QoS handling.
It is seen more and more in Minimun Technical requierements for massive networks, public projects…
It’s becoming a must. When you have not this feature and have no plan to implement it in your equipments, you are simply through out from discussion!
Agreed, IPV6 now a “required feature” on large bids, whether or not the end customers actually end up using it or not.
i.e. without it, bids to certain customer requirements are going to get harder and harder and sometimes impossible as the months go by.
Regards
minimum;
Basic addresses,
basic static routing,
ipcp6 support to all ppp(!!)
ipv6 type packet filter firewall
tools support (e-mail, ping, traceroute)
bridge filter ability to filter basic ipv6 options
cool;
bgp support
ospf6 support
rip6 support
ipv6 exclusive access
ip services access
mac-telnet
winbox access
frosting;
firewall stateful tracking of tcpv6
Hi normis, sten is right about the feature we would like to see but I would also add MIPv6 which is an important feature.
Also consider that IPv6 is going to be mandatory for large bids, so take into account as an important and very urgent need!
I’d like to see ipv6, at least basic routing and ospf6.
I have no clue what MIP6, perhaps it’s what i am about to suggest as a “minimum” thing (it’s so immensly important for successful ipv6 networking); The functionality of BSD’s “rtadvd”, that is, to broadcast prefixes for host autoconfiguration. Technically it’s probably ethernet multicasted, but i have not taken the time to verify that. 
With Vista having a fully functional ipv6 implementation, I’d expect demand for it to grow massively after the release as there is a functional end user device out for it to the masses…
Time for me to start reading up I guess! 
And still, nobody here is sure what they are requesting. Any specific needs yet?
(Btw “Vista” means Chicken in Latvian. The new windows name is hilarious here.)
I’m still learning IPV6 myself so i cant list exactly what i want but i would like to be able to run a pure IPV6 stack, with all the services needed like DHCP etc and PPP if its needed (I douno is PPP has a place in IPv6) and dynamic routing is also a must
What would also be nice is the ablity to map v6 to v4 address so if a AAAA dns lookup fails the client network can still access v4 resources with a Realworld v4 IP
Exactly my feeling as well. What ‘specifically’ is there to request? IPv6, is IPv6, will stay IPv6. Perhaps I just don’t know enough about it yet to be educated enough.
ipv6 over ipv4 tunnels will be good, but yeah. What is needed to run a ipv6 network? ipv6 applications I would guess… dhcp, bind, bgp, etc etc etc etc… Maybe I’m just missing the point though
Hi normis, yes we have specific needs, but I need to contact you off the forum for our needs. Mainly what we need is IPv6 support…
Thank you
On my opinion ipv6 kernel/packages must be optional(means if you want - you install it), and separate. Because they will make i think system bigger and slower, which is critical for embedded applications.
therefore, I ask all of you here. We wish to hear what everyone needs, so that we can make it better for everyone. off-list will be of no use to everyone else.
then I will try to summarize:
IPv6 total support for the same features we have on IPv4 (including firewalling and more important ROUTING!)+ MIPv6
Cheers
I’d also like to see IPv6 support in MikroTik.
Most useful to me, would be a feature or method that would allow a MT router to act as a v4 to v6 gateway (via a v6 tunnel broker or similar). Then, clients sitting behind the router could use both public IPv4 and public IPv6 (via v6 tunnel) resources [[edit]] until a v6 upstream provider is available in the future. [[/edit]]
Hope that makes sense. 