I haven't been paying attention to this whole thread, but thought I'd
throw my two cents in.
I was never able to get amanda to work through a firewall using NAT.
The way NAT works in the Elron Commander firewall, and most other ones,
I think, is by arbitrarily reassigning port numbers to keep
I haven't been paying attention to this whole thread, but thought I'd
throw my two cents in.
I was never able to get amanda to work through a firewall using NAT.
The way NAT works in the Elron Commander firewall, and most other ones,
I think, is by arbitrarily reassigning port numbers to keep
yes, i solved this by patching this file security.c
it's a dirty hack, but in my setup it doesn't worry me...
*** security.c Mon Dec 4 22:45:01 2000
--- ../../amanda-2.4.2p2-patched/common-src/security.c Thu Mar 14
18:58:51 2002
***
*** 227,233
/* next, make sure
Well, in my situation I just compiled Amanda to use a restricted portrange
for both the tcp and udp connections and setup the firewall with a special
NAT rule to pass packets from the amanda server to our clients unchanged.
I can't help you with the Elron Commander because I'm not familiar with
Ok, if you run this:
nslookup `hostname`
on the amanda server, does that resolve? ...
That may not be relevant.
Amanda does not use DNS (directly). All it does is call gethostbyname(),
which is a standard system call that does the right thing, depending
on how you have configured your
We tried it both ways. The backup server actually refers to another
machine on the NAT range for its DNS, so when it pings the names of the
machines with NAT addresses, it will get responses from their NAT IPs.
We also added them manually to the /etc/hosts file on the backup server to
point to
If the server can't back up itself, I'd start there. I just checked on my
system and IP's seem to work, at least with amcheck, so perhaps that will
solve your problem. If you used the FBSD port (/usr/ports) system on your
server to build Amanda, I think it automatically required FQDN for the
Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides
at 192.168.0.18. It is unable to back itself up. We have a DNS server
set up for the NAT addresses at 192.168.0.10 that is referred to in
/etc/resolv.conf as the only DNS server for the Amanda server. However
the Amanda
Ok, if you run this:
nslookup `hostname`
on the amanda server, does that resolve? In the resolv.conf file, are
there 'domain' and 'search' entries? You can ping all the internal
machines, correct? What about some other service like ssh?
As a last resort, you could run tcpdump while running
Yes. We can run nslookup from the amanda server on the hostnames of any
of the machines with NAT addresses we want it to backup and they resolve
to the proper NAT addresses.
The file /etc/resolv.conf has a domain and a nameserver entry, no search
entry, unless thats a synonymous term with
If, for example, you setup your internal machines to have domains like
'host.private.daily.umn.edu', you would want your resolv.conf to look like
this:
domain private.daily.umn.edu
search private.daily.umn.edu daily.umn.edu
nameserver x
It all depends how you've setup your internal DNS,
We began using NAT addresses on our network a few months ago, but at first
we kept all of our systems that were backed up by amanda outside the NAT
range. As time moved on we started bringing some of them inside, and it
seemed that the easiest way to get both the inside (translated) and
outside
On Mon, 18 Mar 2002, Lee Parsons wrote:
We began using NAT addresses on our network a few months ago, but at first
we kept all of our systems that were backed up by amanda outside the NAT
range. As time moved on we started bringing some of them inside, and it
seemed that the easiest way to
Can I use IP addresses in the disklist files rather than the FQDNs? If I
could do that then I wouldn't have to worry about DNS to begin with. I
haven't seen anything explicitly say we can or cannot but every disklist
file I've seen always has the FQDN. Although the other thing I notice i
that
14 matches
Mail list logo
