Re: (ASCEND) radiusd

[Tim Basher <basher@ces.cwru.edu>]

> When I run the new daemon it complains
>
> Invalid type on line 410 of dictionary
>
> This turns out to be the first reference to "abinary".
...
> What on earth am I doing wrong?
 
Are you building the software in the "radiusd" or "ascendd" directories?
The "radiusd" directory is the original unmodified Livingston 1.16 source
code, which does not support "abinary".  The "ascendd" directory is the
more recent Ascend version, which does support "abinary".  You can check
the output of the "radiusd -v" command to verify this.
 examples:
   (radiusd) ./radiusd: RADIUS version 1.16 95/01/06
   (ascendd) ./radiusd: RADIUS version 1.16 (plus Ascend extensions) 1997/12/22

Do you see "BINARY_FILTERS" the output of the "radiusd -v" command?
BINARY_FILTERS is the compile time option that enables support for "abinary".
If you do not include the "-DBINARY_FILTERS" option in the Makefile CFLAGS 
list then your daemon will not include support for "abinary" data types.
 example "radiusd -v":
   (ascendd) NOSHADOW BINARY_FILTERS ASCEND_SECRET ASCEND_LOGOUT sun SOLARIS

Are you using the version of software you just built?
Try giving an explicit path "./radiusd" to make sure you are not picking
up a different version found somewhere in your path.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>