eoip in RouterOS 7.2rc7 broken?

[iossol]

I have made a test between RB3011/RouterOS 6.49.5 and a CHR/RouterOS 7.2rc7

When I create eoip (ipv4) interfaces on both sides and assign private IPv4-Adresses to both ends, I can ping them as expected.
When I assign IPv6 (fd::1/126 - fd::2/126) to both ends, I can not ping the other side.

Doing the same with eoipv6 works as expected, IPv4 and v6 Packets will use the tunnel, with eoip (IPv4) only IPv4-Packets goes through the tunnel

[mhugo]

I have made a test between RB3011/RouterOS 6.49.5 and a CHR/RouterOS 7.2rc7

When I create eoip (ipv4) interfaces on both sides and assign private IPv4-Adresses to both ends, I can ping them as expected.
When I assign IPv6 (fd::1/126 - fd::2/126) to both ends, I can not ping the other side.

Doing the same with eoipv6 works as expected, IPv4 and v6 Packets will use the tunnel, with eoip (IPv4) only IPv4-Packets goes through the tunnel

We saw same from 7.1.5 and 7.2rc7 on 317 to 6.49.5. All up no traffic. Rolled back to ROS 6 as the customer dident want to give us 10 minutes to make supouts so dont have more data.

/M

[aoakeley]

I have made a test between RB3011/RouterOS 6.49.5 and a CHR/RouterOS 7.2rc7

When I create eoip (ipv4) interfaces on both sides and assign private IPv4-Adresses to both ends, I can ping them as expected.
When I assign IPv6 (fd::1/126 - fd::2/126) to both ends, I can not ping the other side.

Doing the same with eoipv6 works as expected, IPv4 and v6 Packets will use the tunnel, with eoip (IPv4) only IPv4-Packets goes through the tunnel

I am running 7.2 with an ipv4 EoIP tunnel and this seems to be working OK for me.

• using ipv4 at each end to create the tunnel,
• sending ipv6 traffic down the tunnel
• This is between CHR and 1100AHx4
• I can ping fd::1 ↔ fd::2 when assigned to each end of the EoIP Tunnel
• I can route IPv6 traffic to the internet down this tunnel.