Looks like this is fixed in recent curl versions.

I guess this commit did it: 090b55c100be4364ac035b5a1b7440cf94e71904 / bug 1189

---
** [bugs:#974] Error binding to ipv4 interface when target has ipv4+ipv6**
**Status:** closed-later
**Created:** Mon Nov 08, 2010 04:13 AM UTC by fiderallalla
**Last Updated:** Fri Jun 21, 2013 01:43 PM UTC
**Owner:** nobody
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.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.