Failed to add duplicate client problem
We have a vpn gateway with different URLs for different user groups. For each URL a specific radius server has to be defined. Up to now those different radius servers have been installed on different machines. When trying to consolidate those servers within different virtual servers on one single machine freeradius refuses to start with the "Failed to add duplicate client xx to clients list. Maybe there's a duplicate? " message. Yes, there is a duplicate and it is on purpose. Is there a way to cirumvent this? Mit freundlichen Grüßen Norbert Wegener
Wegener, Norbert wrote:
We have a vpn gateway with different URLs for different user groups. For each URL a specific radius server has to be defined. Up to now those different radius servers have been installed on different machines. When trying to consolidate those servers within different virtual servers on one single machine freeradius refuses to start with the "Failed to add duplicate client xx to clients list. Maybe there's a duplicate? " message. Yes, there is a duplicate and it is on purpose. Is there a way to cirumvent this?
List the clients under different virtual servers, and have the virtual servers listen on different IP addresses. The list of clients is based off of a virtual server. Within each virtual server, the client IP addresses *must* be unique. If you post your config, my guess is that you have *global* clients, and then are defining the same client IP twice. Alan DeKok.
If you post your config, my guess is that you have *global* clients, and then are defining the same client IP twice.
The clients are read from an sql database. As every client has a corresponding server attached in that database it could be assumed that every client is local to the that virtual server. This obviously is not true. Having distinct sql*conf files for each server and different nas_query in dialup*.conf solves the problem. Thank you. Norbert Wegener - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Wegener, Norbert wrote:
If you post your config, my guess is that you have *global* clients, and then are defining the same client IP twice.
The clients are read from an sql database. As every client has a corresponding server attached in that database it could be assumed that every client is local to the that virtual server. This obviously is not true.
Ah... that code isn't written. The "add client" routine needs to catch the case of SQL adding clients with servers. It doesn't do that right now.
Having distinct sql*conf files for each server and different nas_query in dialup*.conf solves the problem. Thank you.
OK. We'll take a look at fixing it in the next release. Alan DeKok.
participants (2)
-
Alan DeKok -
Wegener, Norbert