On Tue, May 27, 2008 at 6:33 PM, Paul Yeatman
<pyeatman AT mamacass.ucsd DOT edu> wrote:
> So then I recompiled the client for both --with-bsdudp-security and
> --with-bsdtcp-security and loaded both plists.  The server was still
> unable to connect in any way to the client.
>
> Then I realized the problem was with my Red Hat Enterprise amanda
> server which uses its stable albeit older version (2.4.4p3) of AMANDA
> and one which does not use the new bsdtcp authentication.  So, I then
> went about recompiling AMANDA on the server side as well using the
> latest 2.6.0p1 version compiling with both --with-bsdudp-security and
> --with-bsdtcp-security.  I wanted to leave both options open but
> possibly it is conflicting to use both.

Nope -- they can coexist with no problem.

> I'm still not sure on this.  I
> still could make no connection with the client.  So then I recompiled
> the server to use only bsdtcp authentication and I could FINALLY
> connect with the client yet with the following error message
>
>        "client configured for auth=bsdudp while server requested 'bsd'"

This is the key.  You'll need to add
  auth "bsdtcp"
to the dumptypes you're using (probably easiest to just add it to the
global dumptype).

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com