From: dusty Date: 2007-10-31T00:35:05+09:00 Subject: Re: Ruby Radius Dictionary On Oct 26, 10:30 pm, Aby azid Abu bakar wrote: > I'm still new with radius protocol. Does the dictionary in radius client > have to be the same as dictionary in Radius Server?. I checked packet.rb > and found comment that the coding is referring to RFC 2138. The > dictionary in the Radius server is following the RFC 2865. Could this be > the problem? > > Thanks > > -- > Posted viahttp://www.ruby-forum.com/. The dictionary is there to map the code in the packet to a friendly name. So, it doesn't really need to be the same, unless you are using it to convert that code to text and then comparing the two. If you stick with simply the code, then you are OK. But, most people use the dictionaries. I'd read RFC2865. Radius actually has some of the easier to read RFC's, that really explain the protocol well. Here is another thing you could try. Download and install FreeRadius (www.freeradius.org). That software comes with a bunch of dictionaries. You'll notice in them, they use $INCLUDE to include other dictionaries. That isn't going to work here, but you should be able to copy/paste or cat a few of them together. It also comes with a command line program called radclient that you can use to send radius packets to the radius server and it will give you a full print out of the return packet, including all the attributes. I would use that to inspect the packet and see what attributes are coming back to you. Then find that attribute in one of the many dictionaries, then just copy that whole dictionary over to your ruby program. Of course, you could always use tcpdump and take a look at the packet with wireshark (ethereal). I believe that also uses the freeradius dictionaries. Hope that is helpful.