☰

[wiki] Note about MikroTik link-local address bug that needs further investigation (via fd42:2703:1211:100:cafe::44)

IEDON.DN42 Wiki Mirror(176) committed 2026-07-17 11:30:10 +0000 commit 4c3ec068c68e65103b7f7cf8d360ee95b6dfa785

				howto/mikrotik/modern-style.md
			
          @@ -69,6 +69,8 @@ Kioubit is using fe80::ade0 on the remote end of the tunnel. We also chose a lin

           add address=fe80::2762/128 interface=DN42-KIOUBIT advertise=no

           ```

          +**⚠ Note: as of 7.23.2, there seems to be a bug when reusing the same link-local address on multiple tunnels. TCP seems to work fine, but RouterOS will route all responses to ICMP pings through the first tunnel which has that link-local address assigned!**

          +

           If you're using an IPv4 address, you can attach it to the loopback interface. This allows the address to be reused for multiple peering connections, without being "owned" by any of the wireguard interfaces.

           ```

           /ip/address

...	...	@@ -69,6 +69,8 @@ Kioubit is using fe80::ade0 on the remote end of the tunnel. We also chose a lin
69	69	add address=fe80::2762/128 interface=DN42-KIOUBIT advertise=no
70	70	```
71	71
	72	+⚠ Note: as of 7.23.2, there seems to be a bug when reusing the same link-local address on multiple tunnels. TCP seems to work fine, but RouterOS will route all responses to ICMP pings through the first tunnel which has that link-local address assigned!
	73	+
72	74	If you're using an IPv4 address, you can attach it to the loopback interface. This allows the address to be reused for multiple peering connections, without being "owned" by any of the wireguard interfaces.
73	75	```
74	76	/ip/address