From db924b7a9a2444496dbeded384d2c53683a6bb33 Mon Sep 17 00:00:00 2001 From: Eric Bollengier Date: Tue, 26 May 2009 13:51:35 +0000 Subject: [PATCH] ebl Add documentation for new directives DirSourceAddress and FDSourceAddress --- docs/manuals/en/concepts/newfeatures.tex | 41 +++++++++++++++++++++++- docs/manuals/en/install/dirdconf.tex | 9 ++++++ docs/manuals/en/install/filedconf.tex | 9 ++++++ 3 files changed, 58 insertions(+), 1 deletion(-) diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index 254712c2..36f67ba3 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -2,7 +2,46 @@ %% -\chapter{New Features} +\chapter{New Features in 3.0.2} + +This chapter presents the new features added to the development 3.0.2 +versions to be released as Bacula version 3.0.2 sometime in 2009. + +\section{Source Address} +\index[general]{Source Address} + +A feature has been added which allows the administrator to specify the address +from which the director and file daemons will attempt connections from. This +may be used to simplify system configuration overhead when working in complex +networks utilizing multi-homing and policy-routing. + +To accomplish this, two new configuration directives have been implemented: +\begin{verbatim} +FileDaemon { + FDSourceAddress=10.0.1.20 # Always initiate connections from this address +} + +Director { + DirSourceAddress=10.0.1.10 # Always initiate connections from this address +} +\end{verbatim} + +Simply adding specific host routes would have an undesirable side-effect: any +application trying to contact the destination host would be forced to use the +more specific route, possibly diverting management traffic onto a backup VLAN. +Instead of adding host routes for each client connected to a multi-homed backup +server (for example where there are management and backup VLANs), one can +use the new directives to specify a specific source address at the application +level. + +Additionally, this allows the simplification and abstraction of firewall rules +when dealing with a Hot-Standby director or storage daemon configuration. The +Hot-standby pair may share a CARP address, which connections must be sourced +from, while system services listen and act from the unique interface addresses. + +This project was funded by Collaborative Fusion, Inc. + +\chapter{New Features in 3.0.0} \label{NewFeaturesChapter} \index[general]{New Features} diff --git a/docs/manuals/en/install/dirdconf.tex b/docs/manuals/en/install/dirdconf.tex index 1c972fc0..b07fbbfd 100644 --- a/docs/manuals/en/install/dirdconf.tex +++ b/docs/manuals/en/install/dirdconf.tex @@ -304,6 +304,15 @@ resource. directive only permits a single address to be specified. This directive should not be used if you specify a DirAddresses (N.B. plural) directive. +\item [DirSourceAddress = \lt{}IP-Address\gt{}] + \index[fd]{DirSourceAddress} + \index[fd]{Directive!DirSourceAddress} + This record is optional, and if it is specified, it will cause the Director + server (when initiating connections to a storage or file daemon) to source + its connections from the specified address. Only a single IP address may be + specified. If this record is not specified, the Director server will source + its outgoing connections according to the system routing table (the default). + \item[Statistics Retention = \lt{}time\gt{}] \index[dir]{StatisticsRetention} \index[dir]{Directive!StatisticsRetention} diff --git a/docs/manuals/en/install/filedconf.tex b/docs/manuals/en/install/filedconf.tex index e33b4165..c969770b 100644 --- a/docs/manuals/en/install/filedconf.tex +++ b/docs/manuals/en/install/filedconf.tex @@ -186,6 +186,15 @@ only IPv4 resolutions will be permitted, and likewise with ip6. dotted quadruple. If this record is not specified, the File daemon will bind to any available address (the default). +\item [FDSourceAddress = \lt{}IP-Address\gt{}] + \index[fd]{FDSourceAddress} + \index[fd]{Directive!FDSourceAddress} + This record is optional, and if it is specified, it will cause the File + daemon server (for Storage connections) to bind to the specified {\bf + IP-Address}, which is either a domain name or an IP address specified as a + dotted quadruple. If this record is not specified, the kernel will choose + the best address according to the routing table (the default). + \item [SDConnectTimeout = \lt{}time-interval\gt{}] \index[fd]{SDConnectTimeout} \index[fd]{Directive!SDConnectTimeout} -- 2.39.2