Binding amanda to specific interface
I'm trying to run Amanda on FreeBSD on a machine with multiple IP's bound to the ethernet interface. Amanda seems to insist on picking the alias interface rather than the primary interface and there doesn't seem to be a switch to control the behaviour. Is there one and I just missed it? Mark Radabaugh Amplex (419) 720-3635
Re: Binding amanda to specific interface
> As for the local addresses chosen for outgoing "connections", well > normally the kernel makes the right choice depending on your routing > table > > -- > Greg A. Woods > Outgoing. Amanda picks the 'wrong' one in this case - though I can see why it picked it. This is only causing trouble as we need to renumber the network and can't do it all at once. Some of the machines (including the Amanda tape server) have multiple IP addresses during the transition and we can't keep forward/reverse DNS completely consistent. If Amanda picks the 'old' IP address to connect from then the client 'fails' the RDNS lookup and dies. Mark Radabaugh Amplex (419) 720-3635
Re: Binding amanda to specific interface
> BTW, it's not really that hard at all to keep your reverse DNS fully > consistent for multi-homed hosts reachable on multiple subnets, though > of course it does help to have a well considered naming plan. > > -- > Greg A. Woods > The problem is the forward lookup rather than the reverse DNS. If you give 2 different IP addresses to the same hostname BIND will round-robin the 2 addresses - returning the first address on one query and the second on the next. I think the simplest way to solve this is to go ahead and change the IP address of the client to the new IP address since it doesn't appear that Amanda has a switch to force the source address. I have to break down and do it one of these days anyway :-) Mark Radabaugh Amplex (419) 720-3635
Re: Binding amanda to specific interface
> BTW, it's not really that hard at all to keep your reverse DNS fully > consistent for multi-homed hosts reachable on multiple subnets, though > of course it does help to have a well considered naming plan. > > -- > Greg A. Woods > The problem is the forward lookup rather than the reverse DNS. If you give 2 different IP addresses to the same hostname BIND will round-robin the 2 addresses - returning the first address on one query and the second on the next. I think the simplest way to solve this is to go ahead and change the IP address of the client to the new IP address since it doesn't appear that Amanda has a switch to force the source address. I have to break down and do it one of these days anyway :-) Mark Radabaugh Amplex (419) 720-3635
