Skip to content
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

sendmmsg() and recvmmsg() fail with bad address #434

Open
MPK1 opened this issue Nov 16, 2022 · 0 comments
Open

sendmmsg() and recvmmsg() fail with bad address #434

MPK1 opened this issue Nov 16, 2022 · 0 comments

Comments

@MPK1
Copy link

MPK1 commented Nov 16, 2022

Description

When trying to transmit a 8GB file using the -j and -g parameters, the connection fails. The handshake seems to complete according to the debug logs. The following errormessage is printed:

12:56:42.361 [WARN] sendmmsg failed: Bad address
12:56:42.361 [WARN] engine: error sending packet for regular connection CF436FAFAB812484 - close it; src: 0.0.0.0:47305; dst: 10.0.0.2:4433; errno: 14

When using the exact same configurations but omitting the -j -g in both commmands, everything works as it should.
Using just one of the two options or on just one endpoint leads to the same error.

Environment:

  • Two machines with Debian Bullseye (Linux 5.10.0-8-amd64, x86_64)
  • One machine running the http_client, the other one running the http_server
  • Machines connected with direct 10G link. IP addresses 10.0.0.{1,2}, hostname server in /etc/hosts of the client
  • Client started with ./http_client -p file -7 download -H server -s server:4433/file -G logs -j -g
  • Server started with ./http_server -s 10.0.0.2:4433 -r www -c server,certs/cert.pem,certs/priv.key -G logs -j -g

Are there any known issues with those options?
Thank you for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant