This PR adds IPv6 support. I still need to refactor some code esp. the 2 hacks needed.
At least, we have something working!
Activity
296@guillaumerose: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@guillaumerose: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@guillaumerose: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@guillaumerose: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Is pr still in progress or stale?
Is pr still in progress or stale?
Is pr still in progress or stale?
Is pr still in progress or stale?
Hey folks,
thanks for continuing to work on this PR slowly but steadily :) I am on MacOS 26.6 (M4) and just like @arikon I too was able to successfully test IPv6 connectivity from Podman machine using @karta0807913's ipv6 branch. I did the following
Build gvproxy from karta0807913's ipv6 branch
$ git clone [git@github.com](mailto:git@github.com):karta0807913/gvisor-tap-vsock.git
$ cd gvisor-tap-vsock
$ git checkout remotes/origin/ipv6
$ make gvproxy
$ cp ./bin/gvproxy /opt/homebrew/Cellar/podman/6.1.0/libexec/podmanCreate a new Podman machine and test
❯ podman machine init --user-mode-networking
❯ podman machine start
Starting machine "podman-machine-default"
❯ podman machine ssh
Connecting to vm podman-machine-default. To close connection, use `~.` or `exit`
Fedora CoreOS 44.20260720.3.1
core@localhost:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
... snipped ...
2: enp0s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 5a:94:ef:e4:0c:ee brd ff:ff:ff:ff:ff:ff
altname enx5a94efe40cee
inet 192.168.127.2/24 brd 192.168.127.255 scope global dynamic noprefixroute enp0s1
valid_lft 3587sec preferred_lft 3587sec
inet6 fd00::2/128 scope global dynamic noprefixroute
valid_lft 28790sec preferred_lft 14390sec
inet6 fd00::cbc1:5d43:11a6:f605/64 scope global dynamic noprefixroute
valid_lft 86389sec preferred_lft 14389sec
inet6 fe80::de09:6b:f24d:d197/64 scope link noprefixroute
valid_lft forever preferred_lft forever
$ curl -6 ifconfig.io
2607:f750:a54:xxxx:xxxx:xxxx:xxxx:xxxx
$ ping6 google.com
PING google.com (2607:f8b0:4009:80d::200e) 56 data bytes
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=2 ttl=64 time=0.374 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=3 ttl=64 time=0.371 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2085ms
rtt min/avg/max/mdev = 0.175/0.306/0.374/0.093 msUsing gvproxy without building from karta0807913's IPv6 branch leads to Podman machine acquiring only IPv4 address.
@cfergeau @guillaumerose @gbraad Is it possible to proceed with the merging from @karta0807913's ipv6 branch or is there anything else that is needed? Please advise.
Thanks
Hey folks,
thanks for continuing to work on this PR slowly but steadily :) I am on MacOS 26.6 (M4) and just like @arikon I too was able to successfully test IPv6 connectivity from Podman machine using @karta0807913's ipv6 branch. I did the following
Build gvproxy from karta0807913's ipv6 branch
$ git clone [git@github.com](mailto:git@github.com):karta0807913/gvisor-tap-vsock.git
$ cd gvisor-tap-vsock
$ git checkout remotes/origin/ipv6
$ make gvproxy
$ cp ./bin/gvproxy /opt/homebrew/Cellar/podman/6.1.0/libexec/podmanCreate a new Podman machine and test
❯ podman machine init --user-mode-networking
❯ podman machine start
Starting machine "podman-machine-default"
❯ podman machine ssh
Connecting to vm podman-machine-default. To close connection, use `~.` or `exit`
Fedora CoreOS 44.20260720.3.1
core@localhost:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
... snipped ...
2: enp0s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 5a:94:ef:e4:0c:ee brd ff:ff:ff:ff:ff:ff
altname enx5a94efe40cee
inet 192.168.127.2/24 brd 192.168.127.255 scope global dynamic noprefixroute enp0s1
valid_lft 3587sec preferred_lft 3587sec
inet6 fd00::2/128 scope global dynamic noprefixroute
valid_lft 28790sec preferred_lft 14390sec
inet6 fd00::cbc1:5d43:11a6:f605/64 scope global dynamic noprefixroute
valid_lft 86389sec preferred_lft 14389sec
inet6 fe80::de09:6b:f24d:d197/64 scope link noprefixroute
valid_lft forever preferred_lft forever
$ curl -6 ifconfig.io
2607:f750:a54:xxxx:xxxx:xxxx:xxxx:xxxx
$ ping6 google.com
PING google.com (2607:f8b0:4009:80d::200e) 56 data bytes
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=2 ttl=64 time=0.374 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=3 ttl=64 time=0.371 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2085ms
rtt min/avg/max/mdev = 0.175/0.306/0.374/0.093 msUsing gvproxy without building from karta0807913's IPv6 branch leads to Podman machine acquiring only IPv4 address.
@cfergeau @guillaumerose @gbraad Is it possible to proceed with the merging from @karta0807913's ipv6 branch or is there anything else that is needed? Please advise.
Thanks
Hey folks,
thanks for continuing to work on this PR slowly but steadily :) I am on MacOS 26.6 (M4) and just like @arikon I too was able to successfully test IPv6 connectivity from Podman machine using @karta0807913's ipv6 branch. I did the following
Build gvproxy from karta0807913's ipv6 branch
$ git clone git@github.com:karta0807913/gvisor-tap-vsock.git
$ cd gvisor-tap-vsock
$ git checkout remotes/origin/ipv6
$ make gvproxy
$ cp ./bin/gvproxy /opt/homebrew/Cellar/podman/6.1.0/libexec/podmanCreate a new Podman machine and test
❯ podman machine init --user-mode-networking
❯ podman machine start
Starting machine "podman-machine-default"
❯ podman machine ssh
Connecting to vm podman-machine-default. To close connection, use `~.` or `exit`
Fedora CoreOS 44.20260720.3.1
core@localhost:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
... snipped ...
2: enp0s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 5a:94:ef:e4:0c:ee brd ff:ff:ff:ff:ff:ff
altname enx5a94efe40cee
inet 192.168.127.2/24 brd 192.168.127.255 scope global dynamic noprefixroute enp0s1
valid_lft 3587sec preferred_lft 3587sec
inet6 fd00::2/128 scope global dynamic noprefixroute
valid_lft 28790sec preferred_lft 14390sec
inet6 fd00::cbc1:5d43:11a6:f605/64 scope global dynamic noprefixroute
valid_lft 86389sec preferred_lft 14389sec
inet6 fe80::de09:6b:f24d:d197/64 scope link noprefixroute
valid_lft forever preferred_lft forever
$ curl -6 ifconfig.io
2607:f750:a54:xxxx:xxxx:xxxx:xxxx:xxxx
$ ping6 google.com
PING google.com (2607:f8b0:4009:80d::200e) 56 data bytes
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=2 ttl=64 time=0.374 ms
64 bytes from 2607:f8b0:4009:80d::200e: icmp_seq=3 ttl=64 time=0.371 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2085ms
rtt min/avg/max/mdev = 0.175/0.306/0.374/0.093 msUsing gvproxy without building from karta0807913's IPv6 branch leads to Podman machine acquiring only IPv4 address.
@cfergeau @guillaumerose @gbraad Is it possible to proceed with the merging from @karta0807913's ipv6 branch or is there anything else that is needed? Please advise.
Thanks
This pull request is a draft
Merging is unavailable until it is marked ready for review.
@guillaumerose: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.