Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Immediate connect fail for X.X.X.X: Invalid argument
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Aaron Bernardino via curl-users <curl-users_at_cool.haxx.se>
Date: Wed, 24 Feb 2021 17:03:44 +0000
Figured it out. It was this sysctl flag - "net.ipv4.conf.all.route_localnet"
________________________________
From: Aaron Bernardino
Sent: Tuesday, February 23, 2021 3:00:05 PM
To: curl-users_at_cool.haxx.se
Subject: Immediate connect fail for X.X.X.X: Invalid argument
Using curl 7.59.0 inside a cri-o container in Kubernetes, I'm seeing the following error:
Immediate connect fail for X.X.X.X: Invalid argument
This is when specifying argument --interface 127.0.0.1. I don't encounter the error when not specifying --interface or specifying it with the non-loopback address/hostname instead. I'm also not able to use the interface name (i.e. eth0, lo).
It just hangs
The curious thing is that I don't encounter this w/ Docker in another Kubernetes cluster. I'm not sure if
there is something different w/ the containe networking in both of my environments but I think curl is
immediately responding back with an error when trying to do the socket connection. So the request hasn't been sent out yet.
Looking for tips on why curl would return an immediate error when the loopback interface is used.
Thanks
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2021-02-24
Date: Wed, 24 Feb 2021 17:03:44 +0000
Figured it out. It was this sysctl flag - "net.ipv4.conf.all.route_localnet"
________________________________
From: Aaron Bernardino
Sent: Tuesday, February 23, 2021 3:00:05 PM
To: curl-users_at_cool.haxx.se
Subject: Immediate connect fail for X.X.X.X: Invalid argument
Using curl 7.59.0 inside a cri-o container in Kubernetes, I'm seeing the following error:
Immediate connect fail for X.X.X.X: Invalid argument
This is when specifying argument --interface 127.0.0.1. I don't encounter the error when not specifying --interface or specifying it with the non-loopback address/hostname instead. I'm also not able to use the interface name (i.e. eth0, lo).
It just hangs
The curious thing is that I don't encounter this w/ Docker in another Kubernetes cluster. I'm not sure if
there is something different w/ the containe networking in both of my environments but I think curl is
immediately responding back with an error when trying to do the socket connection. So the request hasn't been sent out yet.
Looking for tips on why curl would return an immediate error when the loopback interface is used.
Thanks
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2021-02-24