Re: (RADIATOR)

Hello Neale - On Fri, 05 Nov 1999, Neale Banks wrote: > For some reason, I can't get this to be prefered over > > Summarising the config file: > > > > Filename %D/users > AddToReply cisco-avpair="ip:addr_pool=second_pool" > > > I would be very int

Re: (RADIATOR) Here is a LARGE email outlining the problems I'm haivng w/ AuthBY Unix/System

Thanks Tom - On Sat, 06 Nov 1999, tom minchin wrote: > On Fri, Nov 05, 1999 at 11:58:28AM -0800, Jason Godsey wrote: > > > > Here I run radiator w/ AuthBY unix and system, showing mixed > > results, if authby system worked w/ shadow on linux, I'd be > > all set, or if authby unix had a seperat

Re: (RADIATOR) Authorization Problems

Hugh Irvine wrote: > Cisco's are very picky about the attributes they receive in an Access-Accept - > They *require* that the Service-Type in the reply match the Service-Type in the > request. In the debug output we can see that the Service-Type = Framed-User > arrives in the Access-Request, but t

radiator@open.com.au

Hello Mark - On Fri, 05 Nov 1999, Mark Stokan wrote: > Howdy All. > > Can anyone point me to dictionary entries for the > following vendor attributes? > > > ERR: Attribute number 66 (vendor 529) is not defined in your dictionary > ERR: Attribute number 67 (vendor 529) is not defined in your d

Re: (RADIATOR) Here is a LARGE email outlining the problems I'm haivng w/ AuthBY Unix/System

On Fri, Nov 05, 1999 at 11:58:28AM -0800, Jason Godsey wrote: > > Here I run radiator w/ AuthBY unix and system, showing mixed > results, if authby system worked w/ shadow on linux, I'd be > all set, or if authby unix had a seperate directive for passwordfilename, > shadowfilename, and groupfile

(RADIATOR) Here is a LARGE email outlining the problems I'm haivng w/ AuthBYUnix/System

Here I run radiator w/ AuthBY unix and system, showing mixed results, if authby system worked w/ shadow on linux, I'd be all set, or if authby unix had a seperate directive for passwordfilename, shadowfilename, and groupfilename it'd work also :) [root@jason raddb]# tail -n 2 /etc/passwd /etc/

RE: (RADIATOR) Authorization Problems

> > Cisco's are very picky about the attributes they receive in > an Access-Accept - > They *require* that the Service-Type in the reply match the > Service-Type in the > request. In the debug output we can see that the Service-Type > = Framed-User > arrives in the Access-Request, but the repl

(RADIATOR)

For some reason, I can't get this to be prefered over Summarising the config file: --8<-- Secret secret DefaultRealm example.com Secret secret DefaultRealm example.com