-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port_handler=slirp4netns not publishing multiple ports anymore #13643
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
network
Networking related issue or feature
Comments
I take a look |
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Mar 29, 2022
The slirp4netns port forwarder was not updated to make use of the new port format. This results in a problem when port ranges are used since it does not read the range field from the port. Update the logic to iterate through all ports with the range and protocols. Also added a system test for port ranges with slirp4netns, rootlesskit and the bridge network mode. Fixes containers#13643 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Mar 30, 2022
The slirp4netns port forwarder was not updated to make use of the new port format. This results in a problem when port ranges are used since it does not read the range field from the port. Update the logic to iterate through all ports with the range and protocols. Also added a system test for port ranges with slirp4netns, rootlesskit and the bridge network mode. Fixes containers#13643 [Fixed merge conflict] Signed-off-by: Paul Holzinger <pholzing@redhat.com>
paralin
pushed a commit
to paralin/podman
that referenced
this issue
Jun 3, 2022
The slirp4netns port forwarder was not updated to make use of the new port format. This results in a problem when port ranges are used since it does not read the range field from the port. Update the logic to iterate through all ports with the range and protocols. Also added a system test for port ranges with slirp4netns, rootlesskit and the bridge network mode. Fixes containers#13643 [Fixed merge conflict] Signed-off-by: Paul Holzinger <pholzing@redhat.com>
paralin
pushed a commit
to paralin/podman
that referenced
this issue
Jun 9, 2022
The slirp4netns port forwarder was not updated to make use of the new port format. This results in a problem when port ranges are used since it does not read the range field from the port. Update the logic to iterate through all ports with the range and protocols. Also added a system test for port ranges with slirp4netns, rootlesskit and the bridge network mode. Fixes containers#13643 [Fixed merge conflict] Signed-off-by: Paul Holzinger <pholzing@redhat.com>
kdrag0n
pushed a commit
to kdrag0n/passt-virtcontainer
that referenced
this issue
Nov 9, 2022
…cations Rebase the patch for Podman on top of current upstream, and: - add support for configuration of specific addresses for forwarded ports - by default, disable port forwarding, and reflect this in the man page changes - adjust processing to a new, incompatible format for port storage, which I couldn't actually track down to a specific commit, but that resulted in containers/podman#13643 and commit eedaaf33cdbf ("fix slirp4netns port forwarding with ranges") Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
network
Networking related issue or feature
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Using port_handler=slirp4netns to preserve the src IPs, podman v4.0.2 does not publish multiple ports anymore, only the first port seems to be forwarded. On v.3.4.4, publishing multiple ports does work.
Steps to reproduce the issue:
podman run -p 2379-2380:2379-2380 --network slirp4netns:port_handler=slirp4netns -it alpine /bin/sh
verify open ports, e.g. using netstat -tnl | grep :23
Describe the results you received:
tcp 0 0 0.0.0.0:2379 0.0.0.0:* LISTEN 1024868/slirp4netns
Describe the results you expected:
tcp 0 0 0.0.0.0:2379 0.0.0.0:* LISTEN 1024868/slirp4netns
tcp 0 0 0.0.0.0:2380 0.0.0.0:* LISTEN 1024868/slirp4netns
Additional information you deem important (e.g. issue happens only occasionally):
podman ps correctly shows: 0.0.0.0:2379-2380->2379-2380/tcp
It works on podman 3.4.4
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)
Yes
The text was updated successfully, but these errors were encountered: