Hi,

we run some experiments with ipv6 on version "5.0beta6" at the moment. I don't know if any of those issues are already discussed here. If so, please ignore

1) ssh via ipv6 "connection refused", only telnet is working.

-> I thought SSH via ipv6 should already work?

2) /ping www.six.heise.de
while resolving ip-address: could not get answer from dns server

-> Apparently /ping is only resolving A-Records?

3) /ipv6 firewall filter> print stats
input does not match any value of chain

-> seems to be a Bug. I cannot see the statistics for the rules

4) How about Isatap-Router Support? I've seen that this is possible on Linux since 2.6.25. Are there plans to support this feature on Mikrotik?

5) Are there plans to enrich the IPv6-Filter-Options, for instance (from ip6tables):

eui64:
This module matches the EUI-64 part of a stateless autoconfigured IPv6 address. It compares the EUI-64 derived from the source MAC address in Ehternet frame with the lower 64 bits of the IPv6 source address. But "Universal/Local" bit is not compared. This module doesn't match other link layer frame, and is only valid in the PREROUTING, INPUT and FORWARD chains.

rt:
Match on IPv6 routing header
--rt-type [!] type
Match the type (numeric).
--rt-segsleft [!] num[:num]
Match the 'segments left' field (range).
--rt-len [!] length
Match the length of this header.
--rt-0-res
Match the reserved field, too (type=0)
--rt-0-addrs ADDR[,ADDR...]
Match type=0 addresses (list).
--rt-0-not-strict
List of type=0 addresses is not a strict list.

regards
Oliver

Access to the router via any other method but telnet over v6 is not working and no timeframe has been set by MT to support this, The same thing applies for ping and a host of other tools within routeros. v6 support within ROS is fairly young and buggy at this point. Have you e-mailed MT support with your filter bugs and requests?

Please read over http://forum.mikrotik.com/viewtopic.php?f=1&t=44440 as I have been trying to get MT to come out and give us an idea of what and when v6 items will be supported in ROS however the only offical response is that v6 hasnt been getting enough request from clients and dev time is being spent on the nv2 wireless protocol and SMP support, To which I have said that this is very disappointing as v4 is less than a year away from running out. E-mail MT support and let them know you need these things fixed

I have been trying to get MT to come out and give us an idea of what and when v6 items will be supported in ROS however the only offical response is that v6 hasnt been getting enough request from clients

I suspect that many router manufacturers are going to be caught off guard when the consumer demand starts, and that won't happen until users suddenly realise that that can't get IPv4 Addresses any more.

At least with Y2K we had a specific date when the shit would hit the fan so to speak.

I have been trying to get MT to come out and give us an idea of what and when v6 items will be supported in ROS however the only offical response is that v6 hasnt been getting enough request from clients

I suspect that many router manufacturers are going to be caught off guard when the consumer demand starts, and that won't happen until users suddenly realise that that can't get IPv4 Addresses any more.

At least with Y2K we had a specific date when the **it would hit the fan so to speak.

In my view what MT's doing is a bit ass-about-face, By the time your clients are asking for it you should really have a mature and stable offering. v6 is coming even if MT wants to burry it's head in the wireles-sand untill "Clients ask us for v6". Its quite critical for MT to have a stable feature-rich v6 offering by the time the last /8 is handed out from IANA and given MT's history in getting the kinks worked out this would be sometime near the end of ROS v5 based on the v3 to v4 to v5 jumps. They have a decent base of v6 in ROS v4 right now but it lacks a number of deal-breaker features of which only 2 have been included in the v5 beta so far and one of them seems to be broken/half done (pppoe + routes)

Cisco, Juniper, Alcatel all have a pretty good v6 offering right now that I can buy tomorrow if I wanted that's supported, Tested and feature rich but I'd really not want to do that with a 1000+ MT device network. I hold out hope and a good first step would be Telnet/SSH/API/Winbox/WWW access to ROS over v6 along with the ROS tools like Bandwidth Test etc, Then fix/define ROS's v6 PPPoE support along with DHCPv6 and then work on the core tech like MPLS etc

The last thing I want to see if D-Day come along where the last /8 is handed out to the RIR and then have MT try to cobble a decent feature set into ROS only to find it's a buggy mess and I'm all out of v4

Or perhaps MT's take is we should run ISP's behind a single public v4 address and to hell with v6

firewall working here on 5.0 build

firewall working here on 5.0 build

Code: Select all

[admin@hs] /ipv6 firewall filter> print all stats   
Flags: X - disabled, I - invalid, D - dynamic 
 #   CHAIN                                                                                         ACTION                  BYTES           PACKETS        
 0   input                                                                                       accept                  14720           203 

works here as well, but "stats" is documented under "print" without filter expression:
It would be good if this works analogous to "/ip fire filter stats"

thanks
oliver

will see to it. Either this or updated manual on how to use stats modifier, as IPv4 has same, but works without naming a filter.