Paul Vander Griend wrote:
Hi,
We are trying to get Amanda to work over a firewall but are
having a lot of trouble. Could anyone tell me what amanda
requires to successfuly backup over a firewall? Right now I
allow machines on the firewalled network to talk to the amanda
server on port 10080.
From: Paul Bijnens [EMAIL PROTECTED]
Subject: Re: Amanda Over Firewall
To: [EMAIL PROTECTED]
Cc: amanda-users@amanda.org, [EMAIL PROTECTED]
Paul Vander Griend wrote:
Hi,
We are trying to get Amanda to work over a firewall but are
having a lot of trouble. Could anyone tell me what
Hi,
We are trying to get Amanda to work over a firewall but are
having a lot of trouble. Could anyone tell me what amanda
requires to successfuly backup over a firewall? Right now I
allow machines on the firewalled network to talk to the amanda
server on port 10080. What other traffic is
On Thu, Sep 08, 2005 at 01:45:24PM -0700, Paul Vander Griend wrote:
Hi,
We are trying to get Amanda to work over a firewall but are
having a lot of trouble. Could anyone tell me what amanda
requires to successfuly backup over a firewall? Right now I
allow machines on the firewalled
the use of port ranges through the
firewall. Amanda needs three sets of ports opened in a firewall:
UDP/10080, TCP/10082, TCP/10083 - the well-known services that
connect clients to Amanda services
the UDP port Range - a set of ports for Amanda to exchange
information between
Two years ago, I wrote here about problems getting Amanda to work through a firewall
using NAT which couldn't be turned-off. I finally gave up in frustration, despite the
helpful advice of the folks here, and set up two separate backup systems, one inside
and outside the firewall. Adding to my
Andreas Sundstrom wrote:
Paul Bijnens wrote:
Kaushal Shriyan wrote:
Can I allow amanda backup server to talk through firewall for accessing
amanda client host, Is there any way out
The general answer is to recompile amanda with a dedicated portrange
and open those ports in the firewall. See
Kaushal Shriyan wrote:
Can I allow amanda backup server to talk through firewall for accessing
amanda client host, Is there any way out
The general answer is to recompile amanda with a dedicated portrange
and open those ports in the firewall. See the explanation in
docs/PORT.USAGE
On Tuesday 13 July 2004 00:48, Kaushal Shriyan wrote:
Can I allow amanda backup server to talk through firewall for
accessing amanda client host, Is there any way out
Any help
You'll have to open up some high numbered ports. I think its in the
docs as to which ones, and which protocol.
I
Paul Bijnens wrote:
Kaushal Shriyan wrote:
Can I allow amanda backup server to talk through firewall for accessing
amanda client host, Is there any way out
The general answer is to recompile amanda with a dedicated portrange
and open those ports in the firewall. See the explanation in
docs
Following up on myself...
Paul Bijnens wrote:
Personnally I use a third option (until I get my firewall upgraded
to use the amanda netfilter modules). My firewall does simple
connection tracking and NAT.
I commented out this block in common-src/security.c
230 /* next, make sure the remote
Paul Bijnens wrote:
Following up on myself...
Again :-)
Paul Bijnens wrote:
Using the standard ip_conntrack module, you have to live with the
standard rather short UDP connection tracking timeout (5 minutes I
believe).
It is 3 minutes.
From
Can I allow amanda backup server to talk through firewall for accessing
amanda client host, Is there any way out
Any help
--
Regards,
Kaushal Shriyan
Technical Engineer
Red Hat India Pvt. Ltd.
Tel : +91-22-22881326/27
Fax : +91-22-22881318
Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25
http://www.peopleware.be
http://www.mobileware.be
Kaushal Shriyan [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
13/07/2004 06:48
To
[EMAIL PROTECTED]
cc
Subject
Amanda Through firewall
Can I
I used the amanda faq-o-matic to recompile my amanda clients and server
(RPM form RH AS 3).
I also add the new port to /etc/services.
On the server, do I have to delete the 10080 port from the /etc/services
? Or is-it still used by amanda server to talk to client ?
Thank !!!
--
Frederic Medery
Good morning,
I would like to know how an amanda RPM can be installed with the option of a special
port range for firewalling rules. e.g udp port range 890-895. How exactly has the
syntax of the rpm command to look like? As I have already installed Amanda and
configured the amanda.conf file I
pascal thomas wrote:
I would like to know how an amanda RPM can be installed with the
option of a special port range for firewalling rules. e.g udp port
range 890-895. How exactly has the syntax of the rpm command to look
like? As I have already installed Amanda and configured the
amanda.conf
Hi, Paul,
on Dienstag, 23. März 2004 at 09:28 you wrote to amanda-users:
PB (Don't be afraid, you wont hear any noise during compilation, it's
PB quiet and easy :-) )
Seems to get the joke-of-the-week in here.
Quiet funny ;)
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL
On Monday 22 March 2004 18:56, Frank Smith wrote:
Besides the --with-tcpportrange= option, you probably also need the
--with-udpportrange= option as well, and open those udp ports on the
firewall. See PORTS.USAGE in the docs directory.
Thanks. I don't know exactly what my colleague changed
Stefan G. Weichinger wrote:
on Dienstag, 23. März 2004 at 09:28 you wrote to amanda-users:
PB (Don't be afraid, you wont hear any noise during compilation, it's
PB quiet and easy :-) )
Seems to get the joke-of-the-week in here.
Quiet funny ;)
[sound of crickets chirping]
I saw that in a
never get to the point where
a TCP connection is set up (I keep referring to we as it's not me who
administers the firewall).
I compiled Amanda myself, restricting the ports to use to 45000-45100. So I
think it should be sufficient to punch a hole in the firewall that allows
TCP traffic from
initiated by the Amanda server disappear, usually never
generating ICMP messages. Whatever we try, we never get to the point where
a TCP connection is set up (I keep referring to we as it's not me who
administers the firewall).
I compiled Amanda myself, restricting the ports to use to 45000
, we never get to the point where
a TCP connection is set up (I keep referring to we as it's not me who
administers the firewall).
I compiled Amanda myself, restricting the ports to use to 45000-45100. So I
think it should be sufficient to punch a hole in the firewall that allows
TCP traffic
Hi,
I have this unusual configuration where Amanda server is outside the
firewall and one client is inside the firewall.
The server and about ten clients are working fine. I just installed
the new client inside the firewall.
I'd like to know what I need to reconfigure using --with-portrange and
Wow, you and I are at almost the exact same place with the same problem.
I too am getting errors about port numbers that I didn't set up in the
configuration, when I compiled amanda.
I've been assuming that my firewall was translating port addresses in
addition to IP addresses, but this doesn't
Thanks to everyone who responded. I think I've tried everyone's
suggestions but none seem to work for me. I think this is more of an
issue of me trying to get my firewall configured.
I've currently compiled (both client and server) with
--with-udpportrange=850,855 --with-portrange=32800,32850
I'm having some trouble setting up an Amanda client sitting in a DMZ
of a firewall to talk to an Amanda server sittin inside a firewall.
I've tried to follow the answer in the FAQ and also read the various
posts on amanda-users. However, I can't get it to work and some
questions till linger:
Wow, you and I are at almost the exact same place with the same problem.
I too am getting errors about port numbers that I didn't set up in the
configuration, when I compiled amanda.
I've been assuming that my firewall was translating port addresses in
addition to IP addresses, but this doesn't
Here's how I did this.
The relevant portions of my configure line:
./configure --with-udpportrange=850,855 --with-portrange=32800,32850
I used this on both client and server
And my firewall (linux) looks like this: (IP numbers are not real)
Internet firewall
Hi all,
I'm using amanda-2.4.2p1 and I used to compile ./configure
--with-portrange=1000,1005 --with-udpportrange=850,854
--with-user=amanda --with-group=disk
but ... when I'm trying to do a backup my firewall response:
--cut--
DENY eth2 PROTO=6 207.245.14.66:3267 207.245.14.71:32886
--cut--
30 matches
Mail list logo
