Score:1

Forwarding ipv6 link local destined traffic not working

in flag

Setup:

VM (eth0) -> hostveth -> ContainerVeth

eth0 and hostveth are in VM network namespace while containerveth is in different namespace

sysctl ipv6 forwarding and iptables FORWARD chain are allowed. Checked filter table and no rule to block link local ipv6.

Request coming from outside of VM to Linux pod (container). Pod receives a request from linklocal ip and it responded back to the request with linklocal ip as dst ip . The response reached VM (took tcpdump on hostveth) but its not getting forwarded to VM eth0. This forwarding worked for other ipv6 destined addresses. Please let me know if i'm missing something. Happy to provide more details. Thanks in Advance!

Michael Hampton avatar
cz flag
How did you alter the traffic?
user3550166 avatar
in flag
IP routing. Added ipv6 default gw to route from veth to eth0
kr flag
Packets with Link local addresses cannot be forwarded between interfaces/links. It’s explicitly not allowed by the standard. See https://www.rfc-editor.org/rfc/rfc4291.html#section-2.5.6
user3550166 avatar
in flag
Thanks sander. is there any workaround/way we can achieve this?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.