On Feb 27, 2009, at 21:34, Alan DeKok wrote:
Doug Hardie wrote:
Thanks. Those are pretty obtuse comments. I finally figured out by trial and error you have to create those two sections as they are not in the file.
No.
From raddb/sites-available/README: The virtual servers do NOT have to be set up with the "sites-available" and "sites-enabled" directories. You can still have one "radiusd.conf" file, and put the server configuration there:
The contents that *used* to be in radiusd.conf are now in raddb/sites-available/default.
They were removed from radiusd.conf because (a) they were getting too big, and (b) it enabled example files per virtual server.
Actually a good idea. Its just not obvious. The previously mentioned README is very helpful. I think its in the wrong place. It should be in raddb where its easier to find. Perhaps there should also be an UPDATING file that points to it. The new structure needs a road map because things are quite difficult to find until you really understand the structure. I now have one module completely working and the other one most probably working. I don't have the complete environment on the test machine yet so it won't do everything yet. I hope to start updating the WIKI on Monday. My initial approach is to retain the existing module page but identify it as Version 1 and create a new one that is for Version 2. One significant change that took mw quite awhile to figure out was that the request arguments are addressed differently. You have to be careful in using the proper pointer for the data type. However, anything with an IPv4 address, e.g. Freamed-IP-Address, is handled quite differently. Version 1 would give you a string ("10.0.1.1") whereas Version 2 gives you the binary version as 4 bytes. I haven't checked all the other data types for changes like that. The other ones I use maintained the same format.