Brillant! Now I see why you're the Amanda admin. The machine *is*
multi-homed (while none of my working clients are). However, it's not as
clear-cut as that.
It has one physical interface and one virtual interface. All the Amanda
traffic should be coming and going over the physical interface.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.0.120 netmask ffffff80 broadcast 192.168.0.127
ether 0:0:0:0:0:0
hme0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.10.50 netmask ffffffc0 broadcast 192.168.10.63
# cat /etc/hosts
#
# Internet host table
#
127.0.0.1 localhost
192.168.0.1 host1
192.168.10.1 host2
As you can see, there are two networks co-existing on the same wire. Host2
is a website address; Amanda is supposed to be working via host1. Forward
and reverse DNS resolve to host1 and 0.1, respectively.
FWIW, I think you're on the right track.
Scott Ripley
DNS/VPN Administrator, HIR-Communications
U.S. House of Representatives
202.226.2833
mailto:scott.ripley AT mail.house DOT gov
> -----Original Message-----
> From: Amanda Admin [mailto:amanda AT denverdata DOT com]
> Sent: Thursday, September 04, 2003 1:03 PM
> To: Ripley, Scott; amanda-users AT amanda DOT org
> Subject: RE: service looping/terminating
>
> >
> > I've reinstalled many times, with many options on and off, I've
> rebooted,
> > HUP'd and kill -9'd every possible suspect. Since the service is being
> > denied at the door, there are no amanda debug files, and all the
> > server says
> > is that the request timed out. Snooping the traffic shows that
> > the client is
> > sending back a message that the destination is unreachable.
>
> Longshot, but might this client be multi-homed?
>
> Maybe the amanda server is calling the client one name, but /etc/hosts or
> DNS returns a different name for the same address?
>
> Doug
|
