Bugs item #3105028, was opened at 2010-11-08 05:13
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3105028&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: bad behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: fiderallalla (fiderallalla7)
Assigned to: Nobody/Anonymous (nobody)
Summary: Error binding to ipv4 interface when target has ipv4+ipv6

Initial Comment:
Let's assume there are two interfaces:
eth0: ipv4 AND ipv6: 1.1.1.1 / 2001:.....
eth1: only ipv4: 2.2.2.2

curl --interface 2.2.2.2 <host>
fails when <host> has both ipv6 and ipv4 adresses:

curl: (45) bind failed with errno 22: Invalid argument

To prevent that, one has to manually specify --ipv4 / -4,
In my opinion this should be implied, since we are binding to an ipv4-only interface and it makes no sense preferring ipv6 over ipv4.

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2010-11-11 15:20

Message:
You didn't state what version or OS you use.

The idea is however that the resolved IP is what dictates what
interface/address to bind the local end to. Can you please try the current
git/tomorrow's daily snapshot and see how it works?

If it still fails, can you please A) show us the full -v output and B)
show use the "curl -V" output.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3105028&group_id=976
Received on 2010-11-11