> > > The only way to prevent this behavior as I see it is to add static routes
> > > on both internal network client and DIR/SD server to route all traffic
> > > to/from external interface to internal one transparently for bacula
> > > services. For this to work I would also need to enable routing
> Now I got it ;-). This may work if I edit hosts files on all of my dual-NIC
> clients as well as on bacula server by substituting external IP address with
> internal one for machines' own hostnames. This however will screw up hosts
> resolution for all network applications and no doubt will have
On Tuesday 21 August 2007 06:49:27 pm Kenny Dail wrote:
> > > I use the client's hosts file to take care of directing the client to
> > > the right address.
> >
> > This does not work for SD. There is no way to tell file client on which
> > host SD resides. There is no such configuration option for
> > I use the client's hosts file to take care of directing the client to
> > the right address.
>
> This does not work for SD. There is no way to tell file client on which host
> SD resides. There is no such configuration option for FD. It gets this
> information from director and I can't confi
On Tuesday 21 August 2007 04:47:41 pm Kenny Dail wrote:
> > On Friday 17 August 2007 04:46:24 pm you wrote:
> > > > where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
> > > > server's external address; 192.168.0.{253,200} are the corresponding
> > > > private addresses. As you ca
> On Friday 17 August 2007 04:46:24 pm you wrote:
> > > where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
> > > server's external address; 192.168.0.{253,200} are the corresponding
> > > private addresses. As you can see, while fd daemon on client has indeed
> > > been bound to
Ivan Adzhubey wrote:
> Hi Martin,
>
> On Friday 17 August 2007 04:46:24 pm you wrote:
>>> where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
>>> server's external address; 192.168.0.{253,200} are the corresponding
>>> private addresses. As you can see, while fd daemon on client
Hi Martin,
On Friday 17 August 2007 04:46:24 pm you wrote:
> > where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
> > server's external address; 192.168.0.{253,200} are the corresponding
> > private addresses. As you can see, while fd daemon on client has indeed
> > been bound t
> On Thu, 16 Aug 2007 16:36:48 -0400, Ivan Adzhubey said:
>
> Hi,
>
> I am having trouble with my dual-NIC servers: it seems there is no way to
> force bacula client on a remote server use a particular fixed
> interface/address for data transfers. Even though I have set FDAddress to a
> pr
Hi,
> where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
> server's
> external address; 192.168.0.{253,200} are the corresponding private
> addresses. As you can see, while fd daemon on client has indeed been bound to
> the private address, it still uses external one for com
10 matches
Mail list logo
