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 --------------------------------------