With Free Radiuds you have the choice
set ascend to old
and then use X-Ascend-Ip-Pool or something like that
(read the dictionary.ascend) as your attribute
or set acend to vendor specific
and then use Ascend-Ip-Pool
as your attribite
Rob
On Sunday 09 September 2001 18:34, you wrote:
> > Look at which *attribute* is being sent. i.e. Ascend defined some
> > of the base (1..255) attributes for their own use. Later, they went to
> > VSA's.
> >
> > Hmm... radclient should *really* have a 'hex' mode, for printing the
> > packets in hex. That way, you can just look at them, and see the
> > difference.
>
> Problem solved! I used ntradping and discovered that the freeradius
> server was sending back a vendor code (and a slightly different response)
> in its reply, but the Cistron server was not. Freeradius returns:
>
> vendor Ascend Ascend-VSA-Assign-IP-Pool=1
>
> while Cistron returns:
>
> Ascend-Assign-IP-Pool=1
>
> The problem was actually with the Ascend MAX where I had "Auth Compat Mode"
> set to OLD. To work with freeradius it apparently needs to be set to
> "VSA".
>
> Now the SQL logging module doesn't seem to be reporting the correct port
> number (it always says 0) even though "with_ascend_hack=yes" is set in
> radiusd.conf and the detail file. I'm guessing isn't meant to affect
> logging? So I'm off to debug that problem now.
>
> Thanks,
> Ron
>
> --
> Ron Chinn
> Partner/Unix Admin
> Amalgamated Systems, LLC
> Tel: (573)364-5452
> Fax: (573)364-7763
> Email: [EMAIL PROTECTED]
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
