reading hosts from NAS table not working on 2.2.6?
Hello, Anyone knows what could be wrong? We are trying to move from an older version to a newer version (2.2.6.) But can't get hosts reading from NAS table to work..And it has always been working. After recompiling and installing...Now hosts from the NAS table is read but not working anymore.. Debug at server start says it is reading all the hosts from database nas table but all requests gets rejected anyway. #############Radius debug . . . . Thu Apr 30 12:16:57 2015 : Info: rlm_sql (sql-smartedge-bng): Attempting to connect rlm_sql_mysql #49 Thu Apr 30 12:16:57 2015 : Info: rlm_sql_mysql: Starting connect to MySQL server for #49 Thu Apr 30 12:16:57 2015 : Info: rlm_sql (sql-smartedge-bng): Connected new DB handle, #49 Thu Apr 30 12:16:57 2015 : Debug: rlm_sql (sql-smartedge-bng): Processing generate_sql_clients Thu Apr 30 12:16:57 2015 : Debug: rlm_sql (sql-smartedge-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas_smartedge Thu Apr 30 12:16:57 2015 : Debug: rlm_sql (sql-smartedge-bng): Reserving sql socket id: 49 TThu Apr 30 13:09:46 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=10.173.5.11,shortname=labb0,secret=redback Thu Apr 30 13:09:46 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 10.173.5.11 (labb0, server=smartedge-bng) to clients list . . . . . Thu Apr 30 12:16:57 2015 : Debug: rlm_sql (sql-smartedge-bng): Released sql socket id: 49 When sending a test from the local server echo "User-Name = 'alex_smartedge', NAS-Identifier = 'labb0', NAS-IP-Address = '10.173.5.11'" | radclient -x -s -c 1 -r 1 -t 3 10.173.5.11:1812 auth redback Thu Apr 30 12:48:50 2015 : Error: Ignoring request to authentication address 10.173.5.11 port 1812 from unknown client 10.173.5.11 port 60611 Thu Apr 30 12:48:50 2015 : Info: Ready to process requests. If i add local server to client.conf instead then it works client labb0{ ipaddr = 10.173.5.11 netmask = 32 secret = redback require_message_authenticator = no nastype = other virtual_server = smartedge-bng #coa_server = coa } echo "User-Name = 'alex_smartedge', NAS-Identifier = 'labb0', NAS-IP-Address = '10.173.5.11'" | radclient -x -s -c 1 -r 1 -t 3 10.173.5.11:1812 auth redback Sending Access-Request of id 168 to 10.173.5.11 port 1812 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 rad_recv: Access-Accept packet from host 10.173.5.11 port 1812, id=168, length=115 DHCP-Max-Leases = 1 Qos-Policing-Profile-Name = "default_qos_policing_policy" Qos-Metering-Profile-Name = "default_qos_metering_policy" Context-Name = "BASIC" Total approved auths: 1 Total denied auths: 0 Total lost auths: 0 #############Radius debug rad_recv: Access-Request packet from host 10.173.5.11 port 60305, id=168, length=49 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 192.168.6.5 Thu Apr 30 13:03:33 2015 : Info: server smartedge-bng { Thu Apr 30 13:03:33 2015 : Info: # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/smartedge-bng Any clues on what could be wrong? I can't see anything weird in the test conf? server smartedge-bng { authorize { bla... bla... sql-smartedge-bng preprocess perl-smartedge-bng } authenticate { bla... bla... perl-smartedge-bng } accounting { bla... bla... sql-smartedge-bng perl-smartedge-bng } } ### sql.conf ### ##default sql { bla... bla... readclients = yes nas_table = "nas" $INCLUDE sql/${database}/dialup.conf } sql sql-smartedge-bng { bla... bla... readclients = yes nas_table = "nas_smartedge" $INCLUDE sql/${database}/dialup-smartedge-bng.conf } sql server2 { bla.. bla.. $INCLUDE sql/${database}/server2.conf } sql server3 { bla.. bla.. $INCLUDE sql/${database}/server3.conf } etc. etc. ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person
On Apr 30, 2015, at 7:20 AM, Alexander Silveröhrt <Alexander.Silverohrt@itux.se> wrote:
Anyone knows what could be wrong?
We are trying to move from an older version to a newer version (2.2.6.) But can't get hosts reading from NAS table to work..And it has always been working.
There were issues in 2.2.5 which meant that some configurations worked by accident. That was cleaned up in 2.2.6, so that it behaves as documented, and as intended. So... it *should* work. It works for other people, and it works in my tests, I'd say try it with a simple test system, based on the default configuration. Alan DeKok.
Hi,
We are trying to move from an older version to a newer version (2.2.6.) But can't get hosts reading from NAS table to work..And it has always been working.
I've seen the same thing - asked a question on this list but have been too busy to follow-up with debug work etc - s the affected system is still on 2.2.4 (as 2.2.5 had other known bugs/issues) - I've been spending more time looking at 3.0.x migration work instead. the issue looks related to the change made in 2.2.6 "When clients are loaded from SQL, allow them to be tied to a virtual server" now....our SQL NAS entries *were* tied to a virtual server..... which is interesting because I think this change was related to some other requirement which then messed up clients loaded globally and NOT within a virtual server. thats my hunch anyway. alan
On Apr 30, 2015, at 11:48 AM, A.L.M.Buxey@lboro.ac.uk wrote:
I've seen the same thing - asked a question on this list but have been too busy to follow-up with debug work etc - s the affected system is still on 2.2.4 (as 2.2.5 had other known bugs/issues) -
The changes were made as a result of bugs you reported with the older systems. As it turns out, the "virtual server" field in SQL was pretty much ignored. That's bad. The fix was to actually use the "virtual server" field. The code was tested with, and without, virtual servers. If it doesn't work, then there's some other un-tested corner case which is being hit. We'll need to know what that case is before fixing anything. Alan DeKok.
Hi,
The fix was to actually use the "virtual server" field. The code was tested with, and without, virtual servers. If it doesn't work, then there's some other un-tested corner case which is being hit. We'll need to know what that case is before fixing anything.
yep. agreed. and I havent had anytime to run any debugs etc for this system...and since we're not hitting anything nasty on the 2.2.x production servers that is specifically fixed in 2.2.6 theres been no pressure to get to that release. alan
Hi,
The fix was to actually use the "virtual server" field. The code was tested with, and without, virtual servers. If it doesn't work, then there's some other un-tested corner case which is being hit. We'll need to know what that case is before fixing anything.
actually, this one should be fairly easy to nail down....so with latest 2.2.7 FR radiusd -X - showing the SQL naslist being read in rlm_sql (staffbase): Read entry nasname=192.168.16.1,shortname=testbox,secret=top-secret rlm_sql (staffbase): Adding client 192.168.16.1 (testbox, server=eduroam) to clients list ..and then the radiusd -X shows this when the client tries talking: Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 18335 Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 44450 Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 63884 with 2.2.4 this config worked alan
On Apr 30, 2015, at 5:59 PM, A.L.M.Buxey@lboro.ac.uk wrote:
..and then the radiusd -X shows this when the client tries talking:
Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 18335 Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 44450 Ignoring request to authentication address * port 1812 from unknown client 192.168.16.1 port 63884
with 2.2.4 this config worked
How many listen sections do you have? Where else are your clients defined? My guess is that you don't have a "listen" section associated with the virtual server. But you do have a global "listen" section, which has its own set of clients. So when you add clients to the virtual server, they aren't used by any "listen" section. If you have a "listen" section tied to a virtual server, then the clients from SQL will be associated with that virtual server, and the associated "listen" section will pick them up. That's what didn't work in 2.2.4. I supposed I could fix the code so that if there's no "listen" section in a virtual server, then the client is associated with the global list of clients. That's easy enough to do, and probably meets most peoples expectations. Alan DeKok.
Hi,
How many listen sections do you have? Where else are your clients defined?
just the one. in the main radiusd.conf (well, i have the listen {} in buffered-sql, control-socket and inner-tunnel)
My guess is that you don't have a "listen" section associated with the virtual server. But you do have a global "listen" section, which has its own set of clients. So when you add clients to the virtual server, they aren't used by any "listen" section.
right
If you have a "listen" section tied to a virtual server, then the clients from SQL will be associated with that virtual server, and the associated "listen" section will pick them up. That's what didn't work in 2.2.4.
yes - this was to allow duplicate clients to be defined differently in seperate virtual servers (which isnt something I want/need ;-) )
I supposed I could fix the code so that if there's no "listen" section in a virtual server, then the client is associated with the global list of clients. That's easy enough to do, and probably meets most peoples expectations.
that sounds about right....to ensure behaviour stays the same as you migrate from earlier 2.x releases alan
On Apr 30, 2015, at 6:40 PM, A.L.M.Buxey@lboro.ac.uk wrote:
I supposed I could fix the code so that if there's no "listen" section in a virtual server, then the client is associated with the global list of clients. That's easy enough to do, and probably meets most peoples expectations.
that sounds about right....to ensure behaviour stays the same as you migrate from earlier 2.x releases
Please try the v2.x.x branch from git. I've pushed a fix. It's ~3 lines of code, so it shouldn't affect anything else. Alan DeKok.
I will try the fix soon.. With a basic with no VR servers the NAS table is read and used and its working. ### radius debug Fri May 1 05:22:36 2015 : Info: rlm_sql (sql): Connected new DB handle, #29 Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Processing generate_sql_clients Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Reserving sql socket id: 29 Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Read entry nasname=10.173.5.11,shortname=labb0,secret=redback Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Adding client 10.173.5.11 (labb0, server=<none>) to clients list Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Released sql socket id: 29 ### echo "User-Name = 'alex_smartedge', NAS-Identifier = 'labb0', NAS-IP-Address = '10.173.5.11'" | radclient -x -s -c 1 -r 1 -t 3 10.173.5.11:1812 auth redback Sending Access-Request of id 62 to 10.173.5.11 port 1812 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 rad_recv: Access-Accept packet from host 10.173.5.11 port 1812, id=62, length=115 Qos-Metering-Profile-Name = "default_qos_metering_policy" DHCP-Max-Leases = 1 Qos-Policing-Profile-Name = "default_qos_policing_policy" Context-Name = "BASIC" Total approved auths: 1 Total denied auths: 0 Total lost auths: 0 ### radius debug rad_recv: Access-Request packet from host 10.173.5.11 port 49659, id=62, length=49 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 Sending Access-Accept of id 62 to 10.173.5.11 port 49659 Qos-Metering-Profile-Name = "default_qos_metering_policy" DHCP_Max_Leases = 1 Qos-Policing-Profile-Name = "default_qos_policing_policy" Context-Name = "BASIC" Also noticed this new behaviour that each VR server checks the NAS table and then checks the other VR servers hosts as well and only ads clients to current VR server if the hosts doesn't exist in other VR servers or a shared variable?(at least thats what it looks like from the debug)..? Why is that there? Its a VR server? Shouldn't it be independant and be able to use its on set of hosts no matter they exist in other VR servers or in a global variable or not? Here is a log from a 3 VR server setup. First is working and reads the hosts from the NAS table the rest seems to be ignored . . Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-cisco-bng): Attempting to connect rlm_sql_mysql #49 Fri May 1 04:44:17 2015 : Info: rlm_sql_mysql: Starting connect to MySQL server for #49 Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-cisco-bng): Connected new DB handle, #49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Processing generate_sql_clients Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Reserving sql socket id: 49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Released sql socket id: 49 . . . . Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-asr-bng): Attempting to connect rlm_sql_mysql #49 Fri May 1 04:44:17 2015 : Info: rlm_sql_mysql: Starting connect to MySQL server for #49 Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-asr-bng): Connected new DB handle, #49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Processing generate_sql_clients Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Reserving sql socket id: 49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.78 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.22 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.20 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.5 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.23 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.24 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 10.11.12.222 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.13 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.14 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.25 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.5.101 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.26 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.40 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.27 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.28 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Released sql socket id: 49 . . . . Fri May 1 04:44:18 2015 : Info: rlm_sql (sql-smartedge-bng): Connected new DB handle, #49 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Processing generate_sql_clients Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Reserving sql socket id: 49 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.78 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.22 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.20 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.5 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.23 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.24 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 10.11.12.222 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.13 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.14 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.25 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.5.101 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.26 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.40 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.27 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.28 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Released sql socket id: 49 The only way to get around this was to create 3 different NAS tables one for each VR server and not use hosts that existed in the other tables. Then there was no warningsand hosts got read correctly but all requests still ignored of course. Will see if your fix solved things now. Best regards Alex ________________________________________ Från: Freeradius-Users [freeradius-users-bounces+alexander.silverohrt=itux.se@lists.freeradius.org] för A.L.M.Buxey@lboro.ac.uk [A.L.M.Buxey@lboro.ac.uk] Skickat: den 1 maj 2015 00:40 Till: FreeRadius users mailing list Ämne: Re: reading hosts from NAS table not working on 2.2.6? Hi,
How many listen sections do you have? Where else are your clients defined?
just the one. in the main radiusd.conf (well, i have the listen {} in buffered-sql, control-socket and inner-tunnel)
My guess is that you don't have a "listen" section associated with the virtual server. But you do have a global "listen" section, which has its own set of clients. So when you add clients to the virtual server, they aren't used by any "listen" section.
right
If you have a "listen" section tied to a virtual server, then the clients from SQL will be associated with that virtual server, and the associated "listen" section will pick them up. That's what didn't work in 2.2.4.
yes - this was to allow duplicate clients to be defined differently in seperate virtual servers (which isnt something I want/need ;-) )
I supposed I could fix the code so that if there's no "listen" section in a virtual server, then the client is associated with the global list of clients. That's easy enough to do, and probably meets most peoples expectations.
that sounds about right....to ensure behaviour stays the same as you migrate from earlier 2.x releases alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person
Same problem after recompiling and installing freeradius-server-2.x.x. from git I guess? Since all clients got ignored for this VR server at start...i guess it makes sense it rejects the request.. It would have made sense if a request worked for the first VR server that actually didn't ignore the clients following the debug in my earlier email? But now i tested that as well and all VR servers ignores all requests read from the NAS. Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Processing generate_sql_clients Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Reserving sql socket id: 49 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.78 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.22 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.20 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.5 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.23 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.24 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 10.11.12.222 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.13 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.14 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.25 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.5.101 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.26 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.40 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.27 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 06:34:43 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.28 Fri May 1 06:34:43 2015 : Debug: rlm_sql (sql-smartedge-bng): Released sql socket id: 49 Fri May 1 06:34:43 2015 : Info: Ready to process requests. ##### root@itop1:/usr/local/etc/raddb/sites-enabled# echo "User-Name = 'alex_smartedge', NAS-Identifier = 'labb0', NAS-IP-Address = '10.173.5.11'" | radclient -x -s -c 1 -r 1 -t 3 10.173.5.11:1812 auth redback Sending Access-Request of id 169 to 10.173.5.11 port 1812 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 radclient: no response from server for ID 169 socket 3 Total approved auths: 0 Total denied auths: 0 Total lost auths: 1 ##### Rad debug Fri May 1 06:35:22 2015 : Error: Ignoring request to authentication address 10.173.5.11 port 1812 from unknown client 10.173.5.11 port 36790 Fri May 1 06:35:22 2015 : Info: Ready to process requests. ^C ###freeradius-server-2.x.x. /usr/local/lib/libfreeradius-radius-020208.so Best regards Alex ________________________________________ Från: Freeradius-Users [freeradius-users-bounces+alexander.silverohrt=itux.se@lists.freeradius.org] för Alexander Silveröhrt [Alexander.Silverohrt@itux.se] Skickat: den 1 maj 2015 05:31 Till: FreeRadius users mailing list Ämne: SV: reading hosts from NAS table not working on 2.2.6? I will try the fix soon.. With a basic with no VR servers the NAS table is read and used and its working. ### radius debug Fri May 1 05:22:36 2015 : Info: rlm_sql (sql): Connected new DB handle, #29 Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Processing generate_sql_clients Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Reserving sql socket id: 29 Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Read entry nasname=10.173.5.11,shortname=labb0,secret=redback Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Adding client 10.173.5.11 (labb0, server=<none>) to clients list Fri May 1 05:22:36 2015 : Debug: rlm_sql (sql): Released sql socket id: 29 ### echo "User-Name = 'alex_smartedge', NAS-Identifier = 'labb0', NAS-IP-Address = '10.173.5.11'" | radclient -x -s -c 1 -r 1 -t 3 10.173.5.11:1812 auth redback Sending Access-Request of id 62 to 10.173.5.11 port 1812 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 rad_recv: Access-Accept packet from host 10.173.5.11 port 1812, id=62, length=115 Qos-Metering-Profile-Name = "default_qos_metering_policy" DHCP-Max-Leases = 1 Qos-Policing-Profile-Name = "default_qos_policing_policy" Context-Name = "BASIC" Total approved auths: 1 Total denied auths: 0 Total lost auths: 0 ### radius debug rad_recv: Access-Request packet from host 10.173.5.11 port 49659, id=62, length=49 User-Name = "alex_smartedge" NAS-Identifier = "labb0" NAS-IP-Address = 10.173.5.11 Sending Access-Accept of id 62 to 10.173.5.11 port 49659 Qos-Metering-Profile-Name = "default_qos_metering_policy" DHCP_Max_Leases = 1 Qos-Policing-Profile-Name = "default_qos_policing_policy" Context-Name = "BASIC" Also noticed this new behaviour that each VR server checks the NAS table and then checks the other VR servers hosts as well and only ads clients to current VR server if the hosts doesn't exist in other VR servers or a shared variable?(at least thats what it looks like from the debug)..? Why is that there? Its a VR server? Shouldn't it be independant and be able to use its on set of hosts no matter they exist in other VR servers or in a global variable or not? Here is a log from a 3 VR server setup. First is working and reads the hosts from the NAS table the rest seems to be ignored . . Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-cisco-bng): Attempting to connect rlm_sql_mysql #49 Fri May 1 04:44:17 2015 : Info: rlm_sql_mysql: Starting connect to MySQL server for #49 Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-cisco-bng): Connected new DB handle, #49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Processing generate_sql_clients Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Reserving sql socket id: 49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-cisco-bng): Released sql socket id: 49 . . . . Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-asr-bng): Attempting to connect rlm_sql_mysql #49 Fri May 1 04:44:17 2015 : Info: rlm_sql_mysql: Starting connect to MySQL server for #49 Fri May 1 04:44:17 2015 : Info: rlm_sql (sql-asr-bng): Connected new DB handle, #49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Processing generate_sql_clients Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Reserving sql socket id: 49 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.78 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.22 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.20 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.5 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.23 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.24 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 10.11.12.222 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.13 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.14 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.25 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.5.101 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.26 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.40 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.27 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:17 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.28 Fri May 1 04:44:17 2015 : Debug: rlm_sql (sql-asr-bng): Released sql socket id: 49 . . . . Fri May 1 04:44:18 2015 : Info: rlm_sql (sql-smartedge-bng): Connected new DB handle, #49 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Processing generate_sql_clients Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Reserving sql socket id: 49 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.78,shortname=sth0-labb0-bng0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.78 (sth0-labb0-bng0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.78 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.22,shortname=gbg1-ser1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.22 (gbg1-ser1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.22 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.20,shortname=mlm0-ser0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.20 (mlm0-ser0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.20 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.5,shortname=labb0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.5 (labb0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.5 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.23,shortname=mlm0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.23 (mlm0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.23 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.24,shortname=fl0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.24 (fl0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.24 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=10.11.12.222,shortname=fl0-ser1,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 10.11.12.222 (fl0-ser1, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 10.11.12.222 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.13/32,shortname=ids-72-cr0,secret=testing123 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.13 (ids-72-cr0, server=asr-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.13 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.14/32,shortname=ids-72-cr1,secret=testing123 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.14 (ids-72-cr1, server=asr-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.14 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.25,shortname=sth0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.25 (sth0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.25 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.5.101,shortname=gbg0-lb0,secret=redback Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.5.101 (gbg0-lb0, server=smartedge-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.5.101 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.26,shortname=gbg0-ser1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.26 (gbg0-ser1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.26 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.40,shortname=labb1,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.40 (labb1, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.40 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.27,shortname=sv0-ser0,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.27 (sv0-ser0, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.27 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Read entry nasname=192.168.6.28,shortname=gbg0-ser2,secret=cisco Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Adding client 192.168.6.28 (gbg0-ser2, server=cisco-bng) to clients list Fri May 1 04:44:18 2015 : Debug: WARNING: Ignoring duplicate client 192.168.6.28 Fri May 1 04:44:18 2015 : Debug: rlm_sql (sql-smartedge-bng): Released sql socket id: 49 The only way to get around this was to create 3 different NAS tables one for each VR server and not use hosts that existed in the other tables. Then there was no warningsand hosts got read correctly but all requests still ignored of course. Will see if your fix solved things now. Best regards Alex ________________________________________ Från: Freeradius-Users [freeradius-users-bounces+alexander.silverohrt=itux.se@lists.freeradius.org] för A.L.M.Buxey@lboro.ac.uk [A.L.M.Buxey@lboro.ac.uk] Skickat: den 1 maj 2015 00:40 Till: FreeRadius users mailing list Ämne: Re: reading hosts from NAS table not working on 2.2.6? Hi,
How many listen sections do you have? Where else are your clients defined?
just the one. in the main radiusd.conf (well, i have the listen {} in buffered-sql, control-socket and inner-tunnel)
My guess is that you don't have a "listen" section associated with the virtual server. But you do have a global "listen" section, which has its own set of clients. So when you add clients to the virtual server, they aren't used by any "listen" section.
right
If you have a "listen" section tied to a virtual server, then the clients from SQL will be associated with that virtual server, and the associated "listen" section will pick them up. That's what didn't work in 2.2.4.
yes - this was to allow duplicate clients to be defined differently in seperate virtual servers (which isnt something I want/need ;-) )
I supposed I could fix the code so that if there's no "listen" section in a virtual server, then the client is associated with the global list of clients. That's easy enough to do, and probably meets most peoples expectations.
that sounds about right....to ensure behaviour stays the same as you migrate from earlier 2.x releases alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person
On May 1, 2015, at 12:51 AM, Alexander Silveröhrt <Alexander.Silverohrt@itux.se> wrote:
Same problem after recompiling and installing freeradius-server-2.x.x. from git
I guess? Since all clients got ignored for this VR server at start...
It complains about duplicate clients. The only reason to make that complaint is if you actually have duplicate clients. So... why do you have duplicate clients? What configuration do you have, and what do you think the server should do?
###freeradius-server-2.x.x. /usr/local/lib/libfreeradius-radius-020208.so
The code in v2.x.x git with the fix has a version of 2.2.9, so that may be an issue.
Here is a log from a 3 VR server setup. First is working and reads the hosts from the NAS table the rest seems to be ignored
Again, it's complaining about duplicate clients. This is a problem. You have to find out WHY it's complaining about duplicate clients, and go fix that. Why does the default configuration work, and your custom one fail? What changes did you make? Can you reproduce the problem with small changes to the default configuration? Alan DeKok.
I don't have any duplicates and i posted my config earlier. And its the same result when i only add one single host to the nas table(and i only have localhost in clients.conf and i only have one installed freeradius instance on the machine.). As soon as i add a VR server to the config with just the most basic setup i can think of then requests starts getting rejected.. I guess it becomes duplicate clients because? Each VR server uses "readclients = yes" and nas_table = "nas" and they all use same NAS table and then the logic somehow checks each VR servers client readings with the already processed VR servers client list. As i tried to say earlier i tried to do a workaround and let each VR server use its own NAS table and then it stopped complaining about duplicates. But to add a NAS table for each VR server kind of makes it a bit annoying? But if that is how its suppose to be working now with 2.2.6 then i guess thats the way one have to do. Anyway it still doesn't work to let any VR server read clients from each own NAS table.. I Don't know what the server should do..Maybe an easy fix is to only read the NAS table once at start and don't let the VR servers readings re-read the NAS table again unless the VR server actually is using another NAS table of course. Anyway i will test your latest git 2.x.x again tomorrow and see if there is a difference. Thank for the answers. And have a lovely day. Best regards Alex ________________________________________ Från: Freeradius-Users [freeradius-users-bounces+alexander.silverohrt=itux.se@lists.freeradius.org] för Alan DeKok [aland@deployingradius.com] Skickat: den 1 maj 2015 13:30 Till: FreeRadius users mailing list Ämne: Re: reading hosts from NAS table not working on 2.2.6? On May 1, 2015, at 12:51 AM, Alexander Silveröhrt <Alexander.Silverohrt@itux.se> wrote:
Same problem after recompiling and installing freeradius-server-2.x.x. from git
I guess? Since all clients got ignored for this VR server at start...
It complains about duplicate clients. The only reason to make that complaint is if you actually have duplicate clients. So... why do you have duplicate clients? What configuration do you have, and what do you think the server should do?
###freeradius-server-2.x.x. /usr/local/lib/libfreeradius-radius-020208.so
The code in v2.x.x git with the fix has a version of 2.2.9, so that may be an issue.
Here is a log from a 3 VR server setup. First is working and reads the hosts from the NAS table the rest seems to be ignored
Again, it's complaining about duplicate clients. This is a problem. You have to find out WHY it's complaining about duplicate clients, and go fix that. Why does the default configuration work, and your custom one fail? What changes did you make? Can you reproduce the problem with small changes to the default configuration? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person
On May 3, 2015, at 1:41 AM, Alexander Silveröhrt <Alexander.Silverohrt@itux.se> wrote:
I don't have any duplicates and i posted my config earlier.
It was a small piece of the config, and nothing from the SQL table.
And its the same result when i only add one single host to the nas table(and i only have localhost in clients.conf and i only have one installed freeradius instance on the machine.). As soon as i add a VR server to the config with just the most basic setup i can think of then requests starts getting rejected.
Do you have a patch from the default config, so I can test it?
I guess it becomes duplicate clients because? Each VR server uses "readclients = yes" and nas_table = "nas" and they all use same NAS table and then the logic somehow checks each VR servers client readings with the already processed VR servers client list.
The SQL module has "readdlients = yes". The virtual server doesn't have that. If the same module is used in multiple virtual servers, then the module is only initialized once. So there's no way it can read the NAS table multiple times. So I don't know what you mean by "they all use same NAS table". The debug log you posted shows that the NAS table lists clients, and has a defined virtual server. You only posted a small piece of the debug output (again, NOT recommended), so it's impossible to tell what's going on.
As i tried to say earlier i tried to do a workaround and let each VR server use its own NAS table and then it stopped complaining about duplicates.
I have no idea what that means. A virtual server doesn't use a NAS table. An SQL module uses a NAS table.
But to add a NAS table for each VR server kind of makes it a bit annoying? But if that is how its suppose to be working now with 2.2.6 then i guess thats the way one have to do. Anyway it still doesn't work to let any VR server read clients from each own NAS table..
I Don't know what the server should do..Maybe an easy fix is to only read the NAS table once at start and don't let the VR servers readings re-read the NAS table again unless the VR server actually is using another NAS table of course.
I think you're not clear on what the server does. a) clients are read by the SQL module, not by a virtual server b) each SQL module is initialized once, and reads the NAS table once c) an SQL module can be used in multiple virtual servers d) if the virtual servers don't have a "listen" section, the clients read from the NAS table become global clients I *think* what you've done is configured multiple SQL modules, and then set "read_clients = yes" for all of them, and pointed all of them to the same NAS table. That doesn't make any sense. Don't do that. Be sure that the clients are read ONCE, so that there are no duplicates. And post the FULL debug log from v3. The tiny pieces you've posted mean it's impossible to tell exactly what's going on. That makes it MUCH harder to help you. Alan DeKok.
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Alexander Silveröhrt