EoIPv6 Tunnel problem

RouterOS General
1

I use EoIPv6 to set up a remote LAN.
I use PPPOE dial-up, and getting an IPV6 address is all normal.
I have set it up correctly, but the tunnel established by EoIPv6 often fails. After finding out the reason, the global IPv6 address is not used to establish the tunnel, but the local address is used. But ICMPv6 uses the correct global address. This tunnel usually fails after the router is restarted and cannot be repaired automatically.


13:16:40 firewall,info output: in:(unknown 0) out:wlan-client, proto 97, fe80::4e5e:cff:fef2:9407->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 2 
13:16:44 firewall,info output: in:(unknown 0) out:wlan-client, proto ICMP (type 128, code 0), 2408:8221:301d:9f78::8080->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 16 
13:16:45 firewall,info output: in:(unknown 0) out:wlan-client, proto 97, fe80::4e5e:cff:fef2:9407->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 2 
13:16:49 firewall,info output: in:(unknown 0) out:wlan-client, proto ICMP (type 128, code 0), 2408:8221:301d:9f78::8080->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 16 
13:16:50 firewall,info output: in:(unknown 0) out:wlan-client, proto 97, fe80::4e5e:cff:fef2:9407->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 2 
13:16:54 firewall,info output: in:(unknown 0) out:wlan-client, proto ICMP (type 128, code 0), 2408:8221:301d:9f78::8080->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 16 
13:16:55 firewall,info output: in:(unknown 0) out:wlan-client, proto 97, fe80::4e5e:cff:fef2:9407->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 2 
13:16:59 firewall,info output: in:(unknown 0) out:wlan-client, proto ICMP (type 128, code 0), 2408:8221:301d:9f78::8080->2409:8a4b:2b5:4b70:ba69:f4ff:fe03:72fb, len 16
2

Stupid question, have you set the local-address property of the /interface eoipv6?

3

The local address is left blank. Even if I set it as a global address, ROUTEROS will still use the link-local address of the FE80 address.
Only when I create a new tunnel, or disable the tunnel, and restart ROUTEROS then enable the tunnel, can work normally.

4

The local address is left blank. Even if I set it as a global address, ROUTEROS will still use the link-local address of the FE80 address.
Only when I create a new tunnel, or disable the tunnel, and restart ROUTEROS then enable the tunnel, can work normally.

5

If RouterOS ignores the local-address parameter set to the global address even after you disable and re-enable the tunnel after setting the local-address value, it is a bug, so in that state (local-address set to a global IPv6 address but sending from a wrong one after disabling and re-enabling the tunnel), create supout-rif and send it to support@mikrotik.com.