>
> That is not a common thing for a client to do. It makes more sense to
> leave routing decisions up to the kernel. Normally, a client allows the
Sure it is. named(8) is one of those many programs that takes into
account HA and highly scalable configurations. It's got all kinds of
crazy options for binding listening sockets for incoming requests and
specifying the source _port_ and _address_ for outbound connections:
Example:
options {
directory "/";
listen-on { 1.2.3.4/32; };
query-source address 2.4.5.6 port 12346;
transfer-source 7.8.9.1;
notify-source 2.3.3.5;
All kinds of control.
~BAS
> kernel to select both interface and port for the client socket. Some
> clients allow binding to a particular port when needed for firewall
> reasons. For example, named can be configured to bind its client socket
> to port 53 when making client connections to a remote DNS server, but it
> still doesn't bind to a particular interface as that would restrict routing.
>
> I think this would have to be a feature request and a decision would
> have to be made whether or not to implement it.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
