Re: [RadiusNT] Can't get 3com VSA IES_NEXT_HOP_GATEWAY to work

Dale E. Reed Jr. ( (no email) )
Mon, 16 Aug 1999 10:19:52 -0700

Kelly Peterson wrote:
> We are using RadiusNT version 2.5.124 and our HiperARCs are running version
> 4.1.59-6 firmware. I have added the following line to the dictionary file:
> ATTRIBUTE IES-Next-Hop-Gateway 36872 ipaddr

You can't do this. The Attribute ID is NOT 26872, its 26. Inside
attributes 26 is the VendorID (429 in this case) and the VendorType
(36872 in this case). However, RadiusNT only supports VSA in ODBC mode,
which doesn't use the Dictionarty file at all. You would need to add
this to the RadAttributes table.

> And have created a user that looks like this in our users file:
> xstoptest Password="test",
> User-Service-Type=Framed-User,
> Framed-Protocol=PPP,
> Framed-Address=,
> Framed-Netmask=,
> Idle-Timeout=1800,
> Port-Limit=1,
> IES-Next-Hop-Gateway=,
> Session-Timeout=36000,
> On the HiperARC I have enabled the SEND_UNSOLICITED_ARP feature.
> I called 3com and they say that our radius server is not sending the VSA
> correctly to the HiperARC. Below is the output on monitor radius for the
> xstoptest user in hex. Any help would be appreciated!

You need to configure RadiusNT for ODBC mode and then you can do this.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list (including removal) go to: