Open rlpowell opened 2 years ago
Additional info:
In case it matters: --network slirp4netns:port_handler=slirp4netns,outbound_addr=192.168.123.132 also does not work.
$ rpm -q slirp4netns
slirp4netns-1.1.12-2.fc34.x86_64
Perhaps an issue of libslirp ? https://gitlab.freedesktop.org/slirp/libslirp
https://gitlab.freedesktop.org/slirp/libslirp/-/issues/14 implies that this is working is libslirp, but I have no idea how to test that myself in the context of slirp4netns
Anyone able to confirm this?
I encountered this using podman; I don't use slirp4netns directly. This is copied verbatim from https://github.com/containers/podman/issues/13074 where it was closed as not a podman issue:
Description
My host's default IP is 192.168.123.137, but this routes weirdly, so for systems running as servers I need to use a different source IP, like so:
When I do this and perform basic testing with nc (i.e. something like
ncat -e /bin/cat -k -u -l 8888
), then if it's TCP (the nc command does not have the -u), then the response packet comes out, correctly, with 192.168.123.132 as the source IP. With the -u (UDP), though, it comes out with 192.168.123.137 as the source IPDescribe the results you expected:
I expected slirp4netns:outbound_addr to work the same for both TCP and UDP
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
This is the latest version for my platform, and this issue is not mentioned in the troubleshooting guide.