Re: freeradius 2.1.0 default mysql schema don't have nasidentifier table
And the reason is? i thought nasidentifier is quite important attribute. Anyway thanks for reply. ----- Original Message ---- From: Alan DeKok <aland@deployingradius.com> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Sent: Tuesday, September 23, 2008 8:28:22 PM Subject: Re: freeradius 2.1.0 default mysql schema don't have nasidentifier table piston wrote:
freeradius 2.1.0 default mysql schema don't have nasidentifier table. And the mysql query in dialup.conf also don't have nasidentifier value.
It is purposely left out the nasidentifier?
Yes. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
piston wrote:
And the reason is? i thought nasidentifier is quite important attribute. Anyway thanks for reply.
This is the first time in almost 10 years that anyone has said it's important. And if it is important for you, you can edit the configuration to add it. Alan DeKok.
Hi,
This is the first time in almost 10 years that anyone has said it's important.
There may be (few) places where it is important. E.g. we get accouting tickets from a DSL provider through a NAT on their side, and all accounting tickets have the same Client-IP-Address and no NAS-IP-Address. NAS-Identifier is the only attribute that enables us to see from which device exactly the ticket comes from - and the device coincides with geographic location, and it helps in debugging if we can tell where a probem originates.
And if it is important for you, you can edit the configuration to add it.
And I did exactly that. :-) Anyway, it would be a small change to the schema and queries... I also wouldn't mind having it in by default. But I don't care enough to submit a patch. Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473
Hi,
And I did exactly that. :-) Anyway, it would be a small change to the schema and queries... I also wouldn't mind having it in by default. But I don't care enough to submit a patch.
I think the issue is an UPDATE/UPGRADE issue - if the queries are liek that by default - ie schema change - then people running SQL servers must add the new records...or it'll fail. so, either the engine spews out error messages if fields dont exist, OR theres a dirty big UPGRADING text file and accompanying upgrade-1.1-2.0.sql file for each platform etc. in either case, people wont read the errors and they certainly wouldnt read that text file. hmm, back to square one. perhaps a line or 2 in the config file which cause the server to stop if they havent been commented out - soo many projects already go that route. alan
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
piston -
Stefan Winter