At 10:09 AM 12/11/2001 -0500, Jeremy McNamara wrote:
Pardon my newbieness again.
I have figured out how to get VoIP authenticating with FreeRadius but in
the detail (and -X) log the VSAs are still encoded (hex?). Steel-belted
radius displays them in a human readable form and our billing system
Chris Parker wrote:
What attributes are these?
Example from a detail file:
Mon Dec 10 17:42:59 2001
NAS-IP-Address = edited to protect the innocent
Vendor-Specific = 0x19da02093020302f322f31
NAS-Port-Type = Async
User-Name = 567
Called-Station-Id = edited to protect the innocent
Jeremy McNamara [EMAIL PROTECTED] wrote:
Example from a detail file:
Mon Dec 10 17:42:59 2001
NAS-IP-Address = edited to protect the innocent
Vendor-Specific = 0x19da02093020302f322f31
So you've got to tell the server to *use* the dictionary which
defines those attributes. Without
[EMAIL PROTECTED] wrote:
So you've got to tell the server to *use* the dictionary which
*Confused* How do i tell the server to *use* the Dictionary.cisco file?
Jeremy McNamara
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
At 10:32 AM 12/11/2001 -0500, Jeremy McNamara wrote:
Chris Parker wrote:
What attributes are these?
Example from a detail file:
Acct-Input-Packets = 0
Acct-Output-Packets = 0
Service-Type = 0
Vendor-Specific =
[EMAIL PROTECTED] wrote:
Jeremy McNamara [EMAIL PROTECTED] wrote:
*Confused* How do i tell the server to *use* the Dictionary.cisco file?
It should be using the cisco dictionaries by default.
See: raddb/dictionary
man 5 dictionary
$INCLUDE dictionary.cisco IS in the
Jeremy McNamara [EMAIL PROTECTED] wrote:
$INCLUDE dictionary.cisco IS in the raddb/dictionary file and it looks like
FreeRadius is using the dictionary.cisco file because we can authenticate VoIP
calls but for some reason in the detail file those same VSAs are not getting
decoded when they
Vendor-Specific =
0x19da1830683332332d636f6e662d69643d3632363636332033323331333936352036313030333033312033353030
To me, that syas the NAS is generating VSA's for vendor code 0x19da,
or 6618.
That isn't Cisco, and I don't know what it is.
sheeesh... Ok we figured it out...
Jeremy McNamara [EMAIL PROTECTED] wrote:
I have created a dictionary file for Quintum (which is attached)
that may look surprisingly like the Cisco file.
Thanks. I've added it to the set of standard dictionary files.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
