Bugs item #2990815, was opened at 2010-04-22 12:04
Message generated for change (Settings changed) made by codemonkey535
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2990815&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: libcurl
Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Paul (codemonkey535)
Assigned to: Daniel Stenberg (bagder)
>Summary: "interface" option does not work on an IPv6 VLAN

Initial Comment:
Attempting to bind a curl operation to take place using a VLAN interface specified by name does not work.

I am using libcurl 7.20.1 on a linux 2.6.31 kernel.

Do the following to create a VLAN:
vconfig add eth0 2
ifconfig eth0.2 up
ifconfig eth0.2 add fc00::2/64

Then assuming there is a web server at fc00::1 also on VLAN 2
> curl -g --interface eth0.2 http://[fc00::1]/index.html
should work but instead it reports
"cannot bind to eth0.2"

If instead I bind to the interface by using its IP address
> curl -g --interface fc00::2 http://[fc00::1]/index.html
then it seems to work.

And a third option which also works is to not specify the interface but to allow the routing table to determine which interface to use.
> curl -g http://[fc00::1]/index.html

However, neither of options 2 or 3 are good enough for my application since it is theoretically possible for the same local IP address to exist on different VLANs (which breaks option 2) or for the same remote IP address to be accessible via different VLANS (which breaks option 3)

If using an IPv4 address scheme it seems to work in both cases: interface IP or interface name.

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

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