Hello all, I'm using freeradius 2.0.1 with mysql to authorize users for a wireless hotspot. I have a wireless router running CoovaAP firmware. I'm using Arch Linux, and everything is now working great, with ONLY ONE niggling problem remaining I have not modified the freeradius configs much. I added "VENDOR ChilliSpot 14559" to the dictionary file, which I hoped would make freeradius read the "dictionary.chillispot" dictionary. The file says "see man dictionary for the format of the dictionary files", but this man page is not installed. There is no indication in the radius log that it has read a vendor specific dictionary. When freeradius attempts to authorise a user in the appropriate group, a message: rlm_sql: Failed to create the pair: Invalid octet string "1024" for attribute name "ChilliSpot-Max-Total-Octets" is logged and the user is rejected. I am assuming that the attribute name is invalid, because the vendor specific attributes are not known to radius. I added it to the default realm in the "attrs" configuration file, but no good. So, what is wrong? How do I allow vendor specific attributes to be sent in a radius reply? Many thanks in anticipation. David
David Toms wrote:
I have not modified the freeradius configs much. I added "VENDOR ChilliSpot 14559" to the dictionary file, which I hoped would make freeradius read the "dictionary.chillispot" dictionary.
No, it won't.
The file says "see man dictionary for the format of the dictionary files", but this man page is not installed.
Where did you get the installation from? The dictionary files should be installed in a normal location (rpm, .deb, etc), OR in /usr/local/share/man. This last path is printed out if you're doing a manual install. Also, if you managed to read the comments in the raddb/dictionary file, it INCLUDES the other dictionary files. This gives you the path where they're installed, and the syntax that the server expects for including other dictionary files.]
I am assuming that the attribute name is invalid, because the vendor specific attributes are not known to radius. I added it to the default realm in the "attrs" configuration file, but no good.
Adding dictionary entries to another configuration file isn't helpful.
So, what is wrong? How do I allow vendor specific attributes to be sent in a radius reply?
You reference the dictionary file, just like the examples in the dictionary file you read in /etc/raddb. Alan DeKok.
Thanks for that. The manual page for dictionary was installed, but the "man" system itself is broken. It didn't help that the link to the "dictionary" manual on the website (http://www.freeradius.org/dictionary.txt) is also broken. I "DO" try to RTFM, but this is not always so easy! Anyway. I have it working now. On Wed, 12 Mar 2008 16:52:06 +0100 Alan DeKok <aland@deployingradius.com> wrote:
David Toms wrote:
I have not modified the freeradius configs much. I added "VENDOR ChilliSpot 14559" to the dictionary file, which I hoped would make freeradius read the "dictionary.chillispot" dictionary.
No, it won't.
The file says "see man dictionary for the format of the dictionary files", but this man page is not installed.
Where did you get the installation from? The dictionary files should be installed in a normal location (rpm, .deb, etc), OR in /usr/local/share/man. This last path is printed out if you're doing a manual install.
Also, if you managed to read the comments in the raddb/dictionary file, it INCLUDES the other dictionary files. This gives you the path where they're installed, and the syntax that the server expects for including other dictionary files.]
I am assuming that the attribute name is invalid, because the vendor specific attributes are not known to radius. I added it to the default realm in the "attrs" configuration file, but no good.
Adding dictionary entries to another configuration file isn't helpful.
So, what is wrong? How do I allow vendor specific attributes to be sent in a radius reply?
You reference the dictionary file, just like the examples in the dictionary file you read in /etc/raddb.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
David Toms wrote:
It didn't help that the link to the "dictionary" manual on the website (http://www.freeradius.org/dictionary.txt) is also broken.
Where is that link from? http://www.freeradius.org/radiusd/man/dictionary.html
I "DO" try to RTFM, but this is not always so easy!
Well, there is *some* documentation for FreeRADIUS... it may not be all good, but it's getting better. Alan DeKok.
The broken link was on http://www.freeradius.org/usage.html. All the links on that page pointing to manual entries seem to point to ".txt" not ".html" pages. I think the documentation is pretty good. It is a complex product, and people like me shouldn't really be trying to configure it without understanding it better. But I know it can do EXACTLY what I want, so I have to try.... Thanks for prompt response D On Wed, 12 Mar 2008 22:07:14 +0100 Alan DeKok <aland@deployingradius.com> wrote:
David Toms wrote:
It didn't help that the link to the "dictionary" manual on the website (http://www.freeradius.org/dictionary.txt) is also broken.
Where is that link from?
http://www.freeradius.org/radiusd/man/dictionary.html
I "DO" try to RTFM, but this is not always so easy!
Well, there is *some* documentation for FreeRADIUS... it may not be all good, but it's getting better.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
Alan DeKok -
David Toms