On Fri, 8 Oct 2010, W.C.A. Wijngaards wrote:
So right now unbound uses the OS. It creates a TCP socket and connects
to the destination. The OS then decides what interface to send this
from. Your route table is consulted by the OS to decide this.
It does not use the configured outgoing interface for TCP.
In the interest of prevention of feature bloat, I would like to ask,
apart from thanking you for reporting the oddity, if such code is really
necessary? (and would random sampling then be sufficient?)
I think it should be able to do so. People who bind/listen unbound to one IP on
their multihomed machine do have an expectation of this, and will likely put
firewall rules in place to limit to that one IP. unbound would currently not
work
in such a setup.
Paul
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
