IPv6 does not work after the upgrade

RouterOS General
1

Hello,

I have recently upgraded to 6.1 (from 6.1 beta something ) and I experienced the very same behaviour like earlier with IPv6 during earlier upgrades. I dare not to say from what version but for sure it existed during the 5.x versions.

The use case is the following:

  • I use he.net ipv6 tunnel that is set up correctly and works perfect
/interface 6to4 add comment="Hurricane Electric IPv6 Tunnel Broker" disabled=no local-address=83.250.119.8 mtu=1280 name=sit1 remote-address=216.66.80.90
/ipv6 route add comment="" disabled=no distance=1 dst-address=2000::/3 gateway=2001:470:27:5b6::1 scope=30 target-scope=10
/ipv6 address add address=2001:470:27:5b6::2/64 advertise=yes disabled=no eui-64=no interface=sit1
  • after the upgrade the sit interface shows outgoing traffic, but no incoming. The remote gw is not reachable. Disabling/enabling the interface does not help. The reboot does not help either.
  • after several hours I make a reboot and suddenly the ipv6 traffic flows perfect like before the upgrade.
  • This happens after every upgrade.

I do not run some core business on that he.net ipv6 tunnel, but i can imagine if somebody else does this is a critical issue.
Also it might happen with other sit interfaces too.

Could you please investigate.
Thank you.

Regards,
Z

2

Same problem here, ran in to this after upgrading to 6.1 from 5.2. I haven’t had the time to investigate it yet.

3

Same problem here, but I haven’t yet had the time to investigate it.

4

after 6.4 upgrade the sit1 tunnel does not work (even waiting for few hours)

5

I think I find a pattern.
If there is no outbound traffic while the tunnel is negotiated during boot, it will work, but if there is a high IPv6 outgoing traffic while the tunnel is not established yet - for some reason the packets go out Tx>0 but Rx=0

I solved it on a simple way: Unplug the local-master port. Make a cold reboot of the RB and when everything is up and functional, plug back the local-master and voila it works.

I would appreciate if somebody could be fix this issue.
…as long the network is not IPv6 critical - it has a low prio, but more and more use IPv6 and I am missing also the “dancing kame”.

Thank you.
Regards,
Z