Re: Binding amanda to specific interface
[ On Sunday, February 23, 2003 at 23:14:37 (-0500), Mark Radabaugh wrote: ] Subject: 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. If you're talking about the listening side, well Amanda itself doesn't listen on any sockets -- that's done by inetd and on FreeBSD you have to have separate inetd instances listening on each different IP#. 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 +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
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
Re: Binding amanda to specific interface
[ On Monday, February 24, 2003 at 20:09:07 (-0500), Mark Radabaugh wrote: ] Subject: Re: Binding amanda to specific interface 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. That still shouldn't be a problem. I ran amanda on a network that was multi-homed with two IP subnets on the same ethernet for a very long time and had no problem with it (using ~/.amandahosts). -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
