Increased latency when using bridge network with v5 about podman HOT 5 CLOSED

One thing unclear to me though is why the previous version of podman (v4.9.4) is still working with passt-0^20231204.gb86afe3-1.el9.x86_64? There's some kind of "compatibility matrix" between podman and pasta? (Again, assume I don't know much these stuff).

Because podman 5 switched the default from slirp4netns to pasta. https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/

Out of curiosity, do you have references to the pasta issues you're referring to?

No there are so many different ones that I honestly cannot tell without searching for a long time.
You can search in https://passt.top/passt/bugs and here issues with the pasta label
https://github.com/containers/podman/issues?q=is%3Aissue+label%3Apasta

from podman.

Using passt-0^20240510.g7288448-1.el9.x86_64 seems to resolve the issue. It's not available yet in CentOS repos though but I guess it's a matter of time.

Right, yes, I just happened to rebase the CentOS Stream 9 package from Fedora yesterday:
https://gitlab.com/redhat/centos-stream/rpms/passt/-/commit/a6dcc340e56451a98089b23eddc6efb32ae236a6

but it might need a bit before mirrors pick up the new build.

Out of curiosity, do you have references to the pasta issues you're referring to?

It might be this by the way: https://passt.top/passt/commit/?id=d989eae308c2ea2032fc91cc04fb02dffe4a4b63

from podman.

I assume you run rootless. I would guess the delay is the dns resolution? Can you check by connecting directly to a ip?

If it is dns please check /etc/resolv.conf on your host and in the container and provide the output.
My best guess is the issue is with pasta

pasta 0^20231204.gb86afe3-1.el9.x86_64

This version is old and there have been several dns fixes in the meantime so I suggest you try this with a nwer pasta (passt) version installed, i.e. from https://copr.fedorainfracloud.org/coprs/sbrivio/passt/

from podman.

(Warning: you may assume I know pretty much nothing in network "stuff" 😅 )

I would guess the delay is the dns resolution? Can you check by connecting directly to a IP?

Right! Using IP, there's no delay.

If it is dns please check /etc/resolv.conf on your host and in the container and provide the output.

In the container:

search subdomain.mycompany.net
nameserver 10.76.96.26
nameserver 10.76.128.15
options timeout:2

In the host:

domain subdomain.mycompany.net
search subdomain.mycompany.net
nameserver 10.76.96.26
nameserver 10.76.128.15
options timeout:2

(Obviously, the IP of the nameservers are internals to our network.)

My best guess is the issue is with pasta

Currently, we have passt-0^20231204.gb86afe3-1.el9.x86_64 installed. We do not have pasta.

Using passt-0^20240510.g7288448-1.el9.x86_64 seems to resolve the issue. It's not available yet in CentOS repos though but I guess it's a matter of time.

Thanks! 👏

One thing unclear to me though is why the previous version of podman (v4.9.4) is still working with passt-0^20231204.gb86afe3-1.el9.x86_64? There's some kind of "compatibility matrix" between podman and pasta? (Again, assume I don't know much these stuff).

Out of curiosity, do you have references to the pasta issues you're referring to?

from podman.

Great, thanks a lot @Luap99 for the explanations and solution!

from podman.