As far as we can tell, this is because the encapsulated source IP uses the 6to4 prefix, presumably this is a legit client. We traced this to https://elixir.bootlin.com/linux/v4.19.6/source/net/ipv6/sit.c#L622, which means that the packet is dropped after this message is logged.
The configuration for our tunnel:
11: sit1@ethX: <NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/sit 108.Y.Y.Y brd 0.0.0.0
We're seeing the following in dmesg:
As far as we can tell, this is because the encapsulated source IP uses the 6to4 prefix, presumably this is a legit client. We traced this to https://elixir.bootlin.com/linux/v4.19.6/source/net/ipv6/sit.c#L622, which means that the packet is dropped after this message is logged.
The configuration for our tunnel:
It seems like it might be possible to work around this using
ip tunnel 6rd dev sit1 6rd-prefix fc00::/32
(see https://elixir.bootlin.com/linux/v4.19.6/source/net/ipv6/sit.c#L771), but that seems hacky.cc @arthurfabre who did the debugging on this.
Have you encountered this issue as well? Is there a better way to fix this / are we doing something wrong?