Morning,
Jean-Louis Martineau schrieb:
Yes you only need to allow connection to port 10080.
This isn't added to the wiki right now, isn't it? At least I didn't saw it
there.
Just some more questions about that:
* destination-port is 10080 udp, thats clear. But from with source ports is
the
Dustin J. Mitchell schrieb:
> On Wed, Jul 18, 2007 at 12:27:48AM +0200, Stefan G. Weichinger wrote:
>> Any experience with amanda-server on OS X?
>> Any infos regarding this newer than the mentioned link above?
>
> http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_o
On Wed, Jul 18, 2007 at 04:42:30PM +0200, Marc Muehlfeld wrote:
> Jon LaBadie schrieb:
> > With the increasing use of pre-built amanda binaries and
> > the ever increasing concern for security, isn't it about
> > time to make port usage a run time parameter?
>
>
> This was introduced in 2.5.2 (no
Marc Muehlfeld wrote:
Jean-Louis Martineau schrieb:
Since you are using amanda-2.5.2p1, I suggest you use the bsdtcp auth.
It will require no firewall rules.
Where do I don't need firewall rules? I guess, I at least need to
allow connecting the server to the clients. But did the other require
Thanks for all replies which highlight that I had not given an
important piece of information: I am using the pre-built binaries as in
amanda-backup_server-2.5.2p1-1.suse10.0.i586.rpm
There was one reply from Jean-Louis Martineau, which looks like
appropriate for my case and I will try that. Othe
Jean-Louis Martineau schrieb:
Since you are using amanda-2.5.2p1, I suggest you use the bsdtcp auth.
It will require no firewall rules.
Where do I don't need firewall rules? I guess, I at least need to allow
connecting the server to the clients. But did the other required rules can be
removed
Since you are using amanda-2.5.2p1, I suggest you use the bsdtcp auth.
It will require no firewall rules.
Port 10082 and 10083 are not use in 2.5.2 and above, your server need
them only if you have older client (amrecover).
To use bsdtcp auth:
- change your dumptype to have: auth "bsdtcp"
- c
Jon LaBadie schrieb:
> With the increasing use of pre-built amanda binaries and
> the ever increasing concern for security, isn't it about
> time to make port usage a run time parameter?
This was introduced in 2.5.2 (not sure, if it was allready in 2.5.0/2.5.1):
reserved-udp-port int,int
# Defa
On Wed, Jul 18, 2007 at 03:16:24PM +0200, Marc Muehlfeld wrote:
> Hi,
>
> Charles Stroom schrieb:
> > amcheck reports no problem.
>
> amcheck doesn't use the full source/destination portrange like amdump.
>
>
>
> > On the client, I have opened TCP/UDP port 10080, and TCP
> > ports 10082 and 10
Hi,
Charles Stroom schrieb:
> amcheck reports no problem.
amcheck doesn't use the full source/destination portrange like amdump.
> On the client, I have opened TCP/UDP port 10080, and TCP
> ports 10082 and 10083, because I seem to have seen something like that
> when googling.
You need only
> my server (fiume) and my client (stremen) both have a firewall and the
> client fails to be backed up (the server goes fine). amcheck reports
> no problem. On the client, I have opened TCP/UDP port 10080, and TCP
> ports 10082 and 10083, because I seem to have seen something like that
> when go
Greetings,
my server (fiume) and my client (stremen) both have a firewall and the
client fails to be backed up (the server goes fine). amcheck reports
no problem. On the client, I have opened TCP/UDP port 10080, and TCP
ports 10082 and 10083, because I seem to have seen something like that
when
12 matches
Mail list logo
