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 communicating with sd
> daemon on the remote bacula server. I've been through all configuration
> options to no avail. Unfortunately, binding sd on the server to private net
> only is not an option since it also has numerous other clients configured,
> that are only accessible via external net (desktop boxes all around the
> building, etc). Is there any solution? I am running bacula 1.36.1.
>
I had a similar problem and solved it by making the SD listen on the
'backup network' address only. I then added routing entries on the
servers that dont have direct access to this address telling them they
could find the backup network via the SD machine.
When those machines try to reach the SD this routes them to the
appropriate box.
I only had a handful of these machines so adding this to each wasn't hard.
Cheers,
Troy.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
