Re: [Help-gnu-radius] USR Total Control - attribute not found

[Michael Samanov]

Hi!

----- Original Message -----
From: "Sergey Poznyakoff" <address@hidden>
To: "Michael Samanov" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, September 25, 2002 10:55 AM
Subject: Re: [Help-gnu-radius] USR Total Control - attribute not found


> > I installed gnu-radius 0.96.3 as the replacement of radius-cistron. The
> > things are great, but strangely it doesn't recognize some vendor
specific
> > attributes. It doesn't write them into the 'details' but simply ignores
> > them. Here's an example of 'detail' output:
> [...]
> > So, my question: why the radius doesn't recognize these attributes?
>
> Most probably, the dictionary file for usr (raddb/dict/usr) is out of
> date. Unfortunately I have not got any USR equipment to test it. Your
> help will be greatly appreciated.

I would be glad if I could be helpful. Unfortunatelly, I'm not familar with
the Radius protocol, nevertheless, let's argue. Below are what I see without
the USR dictionary imported:

        Vendor-Specific = V429\000\000\220\043\000\000\000\023
        Vendor-Specific = V429\000\000\000\154\000\000\000\023
        Vendor-Specific = V429\000\000\000\231\000\000\000\003
        Vendor-Specific = V429\000\000\000\307\000\000\000\001
        Vendor-Specific = V429\000\000\220\031\000\000\000\000
        Vendor-Specific = V429\000\000\220\032\000\000\000\000
        Vendor-Specific = V429\000\000\220\033\000\000\000\000
        Vendor-Specific = V429\000\000\220\035\000\000\000\023

V - vendor-specific attribute flag
429 - USR Total Control

Now I need some help. Does the string \000\000\220\043 pretend to be
0x00009023 or, on the contrary, 0x23900000? In the first case it's
USR-Connect-Speed, otherwise, it's unknown.

Further, does the next 4 bytes are \0\0\0\023 0x00000013 (19) or 0x13000000
(318767104)? In the first case it means 38400_BPS, otherwise it's unknown,
too.

Etc.

I translated all the responces without the errors with the dictionary given
provided that:

1) vendor-ID 429 is string '429' not numeric 429;
2) order of the bytes is networking (htonl(3), ntohl(3));
3) the attributes and the integer values are 4 bytes long.

Sincerely yours,
  Michael (mailto:address@hidden)