Hello, Le Thursday 26 March 2009 19:14:30 Steve Polyack, vous avez écrit : > I've created a patch that causes Bacula directors and file daemons to > bind to one of their listen addresses before initiating an outgoing > connection. When working in an heavily firewalled environment, this is > the desired behavior (all Bacula traffic will be coming and going on one > IP address). This allows for true separation of Bacula onto a separate > address for backup servers which have interfaces facing both a backup > network and a management network. > > You can read about the issue in this (and other similarly named) thread > http://www.mail-archive.com/[email protected]/msg15640.htm >l from 2006. More information here: > http://www.mail-archive.com/[email protected]/msg15776.htm >l > > Please feel free to criticize this. I'm willing to make necessary > changes to get this taken upstream. I thought about creating a separate > Dir and FD config resource, but it would require a lot of additional code. > > I've also taken the liberty to apply an existing comment wherever I came > across it: > /* > * This is the "old" way of opening a connection. The preferred way is > * now to do what this subroutine does, but inline. That allows the > * connect() call to return error status, ... > */ > BSOCK *bnet_connect(JCR * jcr, int retry_interval, utime_t > max_retry_time, ...
+ /* Deduce the source IP address from our list of daemon addresses */ + src_ipaddr = (IPADDR *) src_addr_list->first(); Why did you take the first address from this list ? Don't you think that it can create an asymetric routing configuration when using multiple network card or when using direct network attachment (with vlan) src_addr = (10.0.0.1, 192.168.1.1) (eth0, eth1) src_ipaddr = 10.0.0.1 incomming_addr = 192.168.1.1 It will give a socket with this configuration : src_ipaddr = 10.0.0.1 dst_addr = 192.168.1.1 Packets will use eth1 to go, and will be back by eth0... Does it make sens ? Bye ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
