Here is the dump and you can see what I am talking about.

Mapping VSA is not too much an issue Yes you are right about the 256  dic file but the in/out traffic is encoded ith in/out vioce these need to be parse


On 7/13/06, Thor Spruyt < [EMAIL PROTECTED]> wrote:
How about adding a dictionary will all 256 numbers?

----- Original Message -----
From: Robert Dukes
To: FreeRadius users mailing list
Sent: Thursday, July 13, 2006 9:26 PM
Subject: Re: (no subject)


Sorry, Ok I use Alvarion Su radios that has  radius accounting option. but
the radios send some VSA  that is not reconizable in the radius.
Breezenet/Breezecom/Alvarion VSA's. These NASs send
Ethernet port data in VSAs (up to 11 per accounting request) but
unfortunately dont use the same attribute numbers each time. Instead,
the attribute number increments each time, then wraps at 256. Radiator
automatically maps the fist one in a packet to Breezecom-Attr1, the
second to Breezecom-Attr2 etc through to Breezecom-Attr11.

I can send a dump log if you want


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



--
Robert Dukes
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to