nsd users - Jul 2009 - outgoing-interface: in nsd.conf

Hi,

I'm just wondering how the outgoing-interface: statement should work in 
NSD configuration. According to the man pages, it should work in an access 
control list style.

I can make it work as long as I set a single IP address to the statement. 
However, if I use a subnet address it doesn't work. In the log I have a 
following line:

xfrd: could not bind source address:port to socket: Cannot assign requested
address

In the config, I have set "outgoing-interface: 10.10.10.0/24" and one
of
the 
IP addresses on the server interface is 10.10.10.84. The ability to use a 
subnet address instead of individual address would be very important, 
because we are generating the configuration automatically and it should be 
applicable to both of our servers.

Regards,

Antti

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Antti,

It seems to work here fine. Could you try it again with checking enabled?
> ./configure --enable-checking
> make (&& make install)
> nsd -L 2 -F 0xffff -c <your nsd.conf>
> dig @<your nameserver> axfr <your zone>
It will provide more information about why NSD could not bind to the
local subnet. Also, you could add verbosity: 2 (or higher) in your
nsd.conf for more information.

You can send the debug logs off-list.

Best regards,

Matthijs Mekking
NLnet Labs

Antti Ristim?ki wrote:
> Hi,
> 
> I'm just wondering how the outgoing-interface: statement should work in
> NSD configuration. According to the man pages, it should work in an
> access control list style.
> 
> I can make it work as long as I set a single IP address to the
> statement. However, if I use a subnet address it doesn't work. In the
> log I have a following line:
> 
> xfrd: could not bind source address:port to socket: Cannot assign
> requested address
> 
> In the config, I have set "outgoing-interface: 10.10.10.0/24" and
one of
> the IP addresses on the server interface is 10.10.10.84. The ability to
> use a subnet address instead of individual address would be very
> important, because we are generating the configuration automatically and
> it should be applicable to both of our servers.
> 
> Regards,
> 
> Antti
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJKaFQNAAoJEA8yVCPsQCW5QKsH/1YBRtzyHqsIC2NrcYbWkn0Q
drWpphU1DQhqbsgmkmio39SX2i+qg0cz6ths5g5yzaj7LCp2/YUpLOfJC+zEA2al
F1b0Vwr0fK0HeL/sIvXKyQ2i6BKgOGZr+EgmL6gdUeYWU51kUQ7XaoE3VWQSoTYw
F9C4JyBjIVtv3Q+45FluKtjZK0c2rrI89Fo2XObLxzB5k9GoANyVmRdr3vaZlSsa
2ABXFSxNbjxeggcoLsy1mFC7MuG7yFln2abh0hFBm3xSsrddwbckY7OgUYYVasYQ
FluBXmTHfQclUQvrZuk5sYSu5UgubY2Lwpy1itav5aPR/oVSc9SM+KumlgJjIBk=LA5z
-----END PGP SIGNATURE-----