Re: [Help-gnu-radius] Received invalid reply digest from server

[Nicholay P. Chuprynin]

Thank you, now it works OK.
Shared key in client.conf wasn't the same as in clients.
But after reading the README I expected radauth to use the key I specified
in the parameters, like this:
radauth -s localhost:KEY ...
Maybe README should be adjusted to reflect this point?
Changes in pgsql.struct may also worth mentioning somethere in the docs..

Thank a lot,
Nicholay

On Mon, 18 Feb 2002, Sergey Poznyakoff wrote:

> It means that the digest the server sealed its reply with, does not
> match the one computed by the client. Usually this indicates that
> the client and server are using different shared keys. To check
> this, examine your raddb/clients on the server and raddb/client.conf
> on the client machine. Both should contain the same value for the
> shared key.

> > And what is the minimal setup (tables, values) of radius database should I
> > perform to test radius authentication? I'm afraid I missing something
> 
> Change to the subdirectory db in the distribution and run
> 
>        make pgsql.struct
> 
> This will produce file `pgsql.struct', describing the default
> authentication and accounting tables. You will need to make
> following changes to this file: replace line
>  active              enum ('Y','N')
> with
>  active char default 'Y' not null
> and line
>  op                  enum('=','!=','<','>','<=','>=') default NULL
> with
>  op character(2) default NULL
> 
> Then, feed this file as an input to psql -d <DATABASE_NAME> to create
> the tables.