net: Dial with specified source address selects wrong scoped destination address #11837
Comments
/cc @pmarks-net |
This issue would not be critical for go1.5 because it implements new Dial using connect-by-name method that tries each IP address until one succeeds. |
Looks like there are two problems here:
|
I don't think so. If the net package abandons taking that responsibility, users could not implement an application which needs to be run on multi-homed nodes. I think that source and/or destination address selection is part of IP routing, and we've introduced the feature for fancy connect-by-name method in go1.5. Seems like we need to make the feature work correctly for both [dst:name, src:literal] and [dst:name, src:wildcard] cases. |
CL https://golang.org/cl/20586 mentions this issue. |
When running TestDialRoutingToBlackhole in golang.org/cl/12561, we see the following on various platforms:
"dial tcp 192.168.0.2:0->[2404:6800:4004:807::1011]:80" looks clearly wrong.
The text was updated successfully, but these errors were encountered: