Greetings: I've no idea how to apply the patch Jean-Louis posted (sorry, Jean-Louis), so I've already created individual host routes for four of my servers (two linux and two windoze) using the command format 'route add -host *hostname*dev eth *x*'. They now show up as UH entries in the routing table on the Amanda server.
I then added the appropriate lines in the .amandahosts file on each of the linux clients and changed the server config using the ZWC Config Utility. This allows the clients to accept commands from the hostname associated with the unique IP addresses of the specific interfaces. Then I ran an amcheck to make sure everything checked cleanly and it does. Now we'll wait until my weekly backup run over the weekend and hope things perform smoothly. Thanks all!! Neil On Tue, Nov 27, 2012 at 3:21 PM, Nathan Stratton Treadway < [email protected]> wrote: > On Tue, Nov 27, 2012 at 07:20:28 -0500, Jean-Louis Martineau wrote: > > The interface in amanda only help to manage the bandwidth for each > > interface by amanda. > > But it is the system that choose which interface to use. > > The route must be configured at the network level. > > Neil mentioned in an earlier thread on this list that his Amanda server > is running Linux, so for what it's worth...: > > I've done this sort of per-destination routing under Linux using the "ip > route" command, e.g. > > ip route add dev eth1 to 10.0.0.0/24 via 192.168.0.1 src 192.168.0.101 > > I've never used it to control connections for Amanda, but if you (Neil) > don't want to apply the src-ip patch that Jean-Louis posted, you should > be able to do what you want by having a separate route command for > individual Amanda client hosts pointing to the interface you'd like to > use for that client. > > You probably wouldn't need the explict "src XXX" on the commands in your > case. (When I was doing this, I only had "eth1" with multiple IP numbers > assigned to it, but since you have multiple interfaces I'm thinking it > would be sufficient just to use the route to point to the proper > interface and let Linux assign the source IP automatically based on > that.) > > And since all your hosts are on your local subnet, you probably don't > need the "via XXX" either. So it might be as simple as > > ip route add dev eth1 to 192.168.0.10/32 > ip route add dev eth2 to 192.168.0.11/32 > > , etc. > > Hope that helps. > > Nathan > > > > > > > ---------------------------------------------------------------------------- > Nathan Stratton Treadway - [email protected] - Mid-Atlantic region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 >
