Repository navigation
ateomnet: worker pod netns enables IPv4 forwarding only, dropping actor IPv6 traffic #945
Description
Sub-task of #246, part of bowei's step 3.
EnableIPv4Forwarding writes /proc/sys/net/ipv4/ip_forward and has no IPv6 counterpart (internal/ateomnet/net.go:206). Actor packets enter the worker pod on a veth and are forwarded to eth0, so with net.ipv6.conf.all.forwarding left at 0 every IPv6 packet an actor sends is dropped by ip6_forward() — including the actor's own DNS queries.
On an IPv6-only cluster this is a hard failure: TestActorEgress returns 504, reproduced 4/4. The netns setup also has no IPv6 veth addressing and no v6 nftables rules, per the existing TODO at net.go:243.
Activity
ateomnet: enable IPv6 forwarding in worker pod netns
atunnel: restrict the actor egress listener to IPv4
atunnel: restrict the actor egress listener to IPv4
atunnel: restrict the actor egress listener to IPv4
atunnel: name the egress listen helper for its family
atunnel: restrict the actor egress listener to IPv4
atunnel: accept actor egress on both address families
ateomnet: enable IPv6 forwarding in the worker pod netns
ateomnet: enable IPv6 forwarding in the worker pod netns
ateomnet: enable IPv6 forwarding in worker pod netns
ateomnet: enable IPv6 forwarding in worker pod netns
ateomnet: enable IPv6 forwarding in worker pod netns