Re: rlm_sql, readclients=yes: multiple NASes with same IP
Hi,
On Wed, Apr 11, 2007 at 06:17:13PM +0200, Alan DeKok wrote:
For me at the moment it's easier to persuade freeradius
just to ignore such duplicities when reading clients by following simple
patch:
No. Your DB configuration is wrong, and needs to be fixed.
Maybe you need to put your NAS IP + port combination into a
different table. But whatever the case, duplicate NAS IP's are wrong,
and will not be supported.
== my apologizes; forget about this silly patch. No matter what's in
the nas table. When using mysql we can always give freeradius what he
wants. IOW: to make the unique list of nases just change the nas_query
in /etc/freeradius/sql/mysql-dialup.conf:
default:
SELECT id, nasname, shortname, type, secret FROM ${nas_table}
unique nases modification:
SELECT id, nasname, shortname, type, secret FROM ${nas_table} group by
nasname
I hope this helps someone.
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Milan Holub
holub (at) thenet (dot) ch
--
TheNet-Internet Services AG,
im Bernertechnopark, Morgenstr. 129
CH-3018, Bern, Switzerland
031 998 4333, Fax 031 998 4330
http://www.thenet.ch
http://wlan.thenet.ch
--
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: rlm_sql, readclients=yes: multiple NASes with same IP
Milan Holub wrote: We are having multiple NASes on the same IP distinguished only by different port(eg. multiple instances of nocat wlangw running on differet ports). No. NASes are distinguished by IP. Nothing else. There is no way in RADIUS to have multiple NASes on the same IP with different ports. I believe that for communication of the NAS with radius only the IP is deciding for radius. Yes. I know this can be solved outside radius by creating another bind table in DB(binding multiple ports to one unique nas record) and changing existing applications for viewing accounting data(php+mysql). I have no idea what you mean by that. FreeRADIUS will look up the NAS by IP, and never by port. What you put in the DB for ports is irrelevant, and will never affect server behavior. i.e. What you use the ports for is up to you, and does not affect the server. For me at the moment it's easier to persuade freeradius just to ignore such duplicities when reading clients by following simple patch: No. Your DB configuration is wrong, and needs to be fixed. Maybe you need to put your NAS IP + port combination into a different table. But whatever the case, duplicate NAS IP's are wrong, and will not be supported. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
