[Unbound-users] unbound does not use "outgoing-interface" for IPv6 TCP requests

W.C.A. Wijngaards wouter at NLnetLabs.nl
Fri Oct 8 12:59:06 UTC 2010

Hash: SHA1

Hi Hauke, Florian,

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?)

Best regards,

On 10/06/2010 10:56 PM, Florian Weimer wrote:
> * Hauke Lampe:
>> Does anyone else see that behaviour?
> I saw it on IPv4, too, it's not IPv6-specific at all.  I tried to fix
> it once, but IIRC, it required changes to library interfaces, so I
> gave up. 8-/
> _______________________________________________
> Unbound-users mailing list
> Unbound-users at unbound.net
> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users

Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/


More information about the Unbound-users mailing list