->>In response to your message<<-
  --received from Dustin J. Mitchell--
>
> On Fri, May 23, 2008 at 4:31 PM, Paul Yeatman
> <pyeatman AT mamacass.ucsd DOT edu> wrote:
> > 1211573838.146757: amandad: security_getdriver(name=bsdudp) returns NULL
> > 1211573838.146772: amandad: critical (fatal): no driver for security type 
> > 'bsdudp'
> >
> > I believe this "'bsdudp' driver" is specified in the plist file,
> > right?  Why am I lacking a "driver of security type 'bsdudp'"?
> 
> You probably didn't build it.  I would strongly recommend that you use
> bsdtcp, anyway.

Ah, right.  I needed to read up on WHATS NEW.

I still ran into a fair amount of trouble.

I recompiled AMANDA on the client side with the configure option
--with-bsdtcp-security (given your comment), loaded only the bsdtcp
plist file, and then couldn't connect from the server at all (at least
I was getting the no bsdudp driver error message on the client
previously).  I tried loading the bsdudp plist file on the
client side and retried an amcheck just to see what would happen yet
understandably got the same error message as above as indeed I had not
recompiled with the bsdudp security option.

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.  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'"

I didn't want the "client [to be] configured for auth=bsdudp" but it
wouldn't seem to work without it.  I also thought I had deliberately
specified the server to use bsdtcp not "bsd".  So, still confused about
why I am getting this report.

I'm at least glad to see something working at all . . . yet am possibly
still a ways off.

Paul