ipv6 egress traffic not working

kubernetes-sigs / ip-masq-agent

Manage IP masquerade on nodes

Apache License 2.0

217 stars 70 forks source link

ipv6 egress traffic not working #58

Closed ragunathan23 closed 3 years ago

ragunathan23 commented 4 years ago

Hi, Running k8s cluster with calico as CNI. We have a usecase to connect to ipv6 device from the pod which is configured with ipv4.

Added ip-masq-agent to masquerade daemonset
It created the iptables for masquerading in the host machine
Able to ping the ipv6 device from the container of the ip-masq-agent
Unable to reach the ipv6 device from the container of other workloads in the same cluster. Getting connect: Network is unreachable when running ping6

ganeshr2 commented 4 years ago

the configuration provided in the master repo is obsolete and does not work for ipv6 usecase - pls use the latest container from gcr and try and let me know below example -

    image: gcr.io/google-containers/ip-masq-agent-amd64:v2.5.0
    args:
        - --masq-chain=IP-MASQ
        - --enable-ipv6=true

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

bowei commented 3 years ago

/remove-lifecycle stale

kundan2707 commented 3 years ago

/kind bug

MrHohn commented 3 years ago

cc @anfernee @sdmodi

anfernee commented 3 years ago

ip-masq-agent runs on hostNetwork: true which means it runs in the host network namespace. That's why you can ping ipv6 device from there. It could be a calico issue. but to be able to correctly triage it, can you run ip6tables-save on your machine and share the result to see if any iptables rules are missing?

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

fejta-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

k8s-ci-robot commented 3 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/ip-masq-agent/issues/58#issuecomment-860128665): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.