Problem with freeradius.org website
Is anyone else experiencing problems with the freeradius.org website? I'm new to freeradius, so maybe this is normal for the site, but I'm getting massive waits (minutes) generally ending in timeouts. Both the addresses are pingable. The Wiki is OK, it's just the website at freeradius.org. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@biplane.com.au) +61-2-64957160 (h) http://www.biplane.com.au/~kauer/ +61-428-957160 (mob) GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28
Karl Auer wrote:
Is anyone else experiencing problems with the freeradius.org website?
Must be a local routing thing.
I'm new to freeradius, so maybe this is normal for the site, but I'm getting massive waits (minutes) generally ending in timeouts. Both the addresses are pingable.
The Wiki is OK, it's just the website at freeradius.org.
Both IP's of the web site are up && operational, so far as I can tell. One is in the US && the other is in France. So if you're seeing issues with both of them, it's not a "local" issue to the web site. Alan DeKok.
Am Montag, 29. September 2008 15:50 schrieb Karl Auer:
Is anyone else experiencing problems with the freeradius.org website?
I'm new to freeradius, so maybe this is normal for the site, but I'm getting massive waits (minutes) generally ending in timeouts. Both the addresses are pingable.
The Wiki is OK, it's just the website at freeradius.org.
Regards, K.
Works from here. No problem. -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: misch@multinet.de web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42
Hi Michael I don't face this kind of problems ether. I'm located in Germany close to Stuttgart ... The problem you face has something to do with you're internet provider. Similar things happend to me several times in the US&A with SBC Global or how ever the provider was called again .. and also with MTC in Namibia ... Masters Solution: - Try to setup an VPN Server somwhere in the world where the Internet connection is more trustable ... even encrypted PPTP with minimum 8 digit pwd is good enough - Use Toor - but don't abuse its bandwidth Regards, Leander Michael Schwartzkopff schrieb:
Am Montag, 29. September 2008 15:50 schrieb Karl Auer:
Is anyone else experiencing problems with the freeradius.org website?
I'm new to freeradius, so maybe this is normal for the site, but I'm getting massive waits (minutes) generally ending in timeouts. Both the addresses are pingable.
The Wiki is OK, it's just the website at freeradius.org.
Regards, K.
Works from here. No problem.
On Mon, 2008-09-29 at 16:11 +0200, Leander S. wrote:
I don't face this kind of problems ether. I'm located in Germany close to Stuttgart ... The problem you face has something to do with you're internet provider.
Thank you all for your swift diagnoses of problems at my end :-) If I went to 64.34.165.250, one of the two IP addresses for the name "freeradius.org", I got "500 service temporarily unavailable", apparently due to "maintenance downtime or capacity problems". I get the same message if I go to leia.telante.com. the canonical name of that address. The other IP address for the name "freeradius.org", 88.191.76.12, responded instantly, with a page from someone called Network RADIUS, Inc. The canonical name for the address, liberty.deployingradius.com, returned a page too. Attempts to go to the *name* "freeradius.org" always failed (timeouts). All of this was - and is! - completely repeatable. Oddly enough, when I force freeradius.org to be 64.34.165.250 using my local /etc/hosts file, everything works. No idea why. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@biplane.com.au) +61-2-64957160 (h) http://www.biplane.com.au/~kauer/ +61-428-957160 (mob) GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28
I ran out of IP space in my original IP_Pool, and since the next available addresses were non contiguous, I added a second pool. Here's the snippet of my radiusd.conf: The problem is that the first pool comes up and is used, but when it runs out of IP space, the second pool never gets used. If the db files are deleted and freeradius restarted, should both sets of files get recreated on start up? ippool main_pool { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 768 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } ippool main_pool2 { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 768 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2 # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2 # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
You should use sql_ippool for non-continuous pools. Ivan Kalik Kalik Informatika ISP Dana 30/9/2008, "Marco C. Coelho" <maillist1@argontech.net> piše:
I ran out of IP space in my original IP_Pool, and since the next available addresses were non contiguous, I added a second pool. Here's the snippet of my radiusd.conf: The problem is that the first pool comes up and is used, but when it runs out of IP space, the second pool never gets used.
If the db files are deleted and freeradius restarted, should both sets of files get recreated on start up?
ippool main_pool {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 768
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
ippool main_pool2 {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 768
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Marco C. Coelho wrote:
I ran out of IP space in my original IP_Pool, and since the next available addresses were non contiguous, I added a second pool. Here's the snippet of my radiusd.conf:
Did you add "main_pool2" to the "post-auth" && accounting sections where "main_pool" was referenced? Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ? Alan DeKok.
Please See Below: Alan DeKok wrote:
Marco C. Coelho wrote:
I ran out of IP space in my original IP_Pool, and since the next available addresses were non contiguous, I added a second pool. Here's the snippet of my radiusd.conf:
Did you add "main_pool2" to the "post-auth" && accounting sections where "main_pool" was referenced?
No. After I added it and corrected the operand to := it now issues the new addresses. Thanks!
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Marco C. Coelho wrote:
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Sorry, the "redundant" section should do what you want. Alan DeKok.
I've been trying to get my second set up IP address' working. The main_pool works correctly. main_pool2 does not appear to ever issue more than 2 ip addresses. you had previously mentioned: Marco C. Coelho wrote:
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Sorry, the "redundant" section should do what you want. Alan DeKok. I cannot find a redundant section in this radiusd.conf my radiusd.conf contains: ippool main_pool { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } ippool main_pool2 { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2 # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2 # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } **********************************It also has: # Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail main_pool main_pool2 **********************************It also has: # Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. main_pool main_pool2 # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above.
No response so I'm resending this Marco C. Coelho wrote:
I've been trying to get my second set up IP address' working. The main_pool works correctly. main_pool2 does not appear to ever issue more than 2 ip addresses. you had previously mentioned:
Marco C. Coelho wrote:
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Sorry, the "redundant" section should do what you want.
Alan DeKok.
I cannot find a redundant section in this radiusd.conf
my radiusd.conf contains:
ippool main_pool {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
ippool main_pool2 {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
**********************************It also has:
# Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail main_pool main_pool2
**********************************It also has:
# Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. main_pool main_pool2 # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above.
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
You did have a reply. Ivan Kalik Kalik Informatika ISP Dana 30/10/2008, "Marco C. Coelho" <maillist1@argontech.net> piše:
No response so I'm resending this
Marco C. Coelho wrote:
I've been trying to get my second set up IP address' working. The main_pool works correctly. main_pool2 does not appear to ever issue more than 2 ip addresses. you had previously mentioned:
Marco C. Coelho wrote:
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Sorry, the "redundant" section should do what you want.
Alan DeKok.
I cannot find a redundant section in this radiusd.conf
my radiusd.conf contains:
ippool main_pool {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
ippool main_pool2 {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
**********************************It also has:
# Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail main_pool main_pool2
**********************************It also has:
# Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. main_pool main_pool2 # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above.
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Ok here's where I'm at now: I added a second IP Pool in my radius.conf. If I create a user account with a group that only lists that new IP Pool (main_pool2), I get an address in that pool. The problem is when I have a user in a group that uses both pools (main_pool and main_pool2), when the first pool runs out of IP addresses, the second pool does not get used. Below are all sections of the radius.conf that I've got the pools called out. any suggestions are greatly appreciated. Help! Marco ippool main_pool { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 44.202.227.1 range-stop = 44.202.229.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } ippool main_pool2 { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 44.202.237.1 range-stop = 44.202.239.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2 # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2 # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } accounting { detail main_pool main_pool2 radutmp sql } post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql } redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log } Marco C. Coelho wrote:
I've been trying to get my second set up IP address' working. The main_pool works correctly. main_pool2 does not appear to ever issue more than 2 ip addresses. you had previously mentioned:
Marco C. Coelho wrote:
Did you put "main_pool" and "main_pool" into a fail-over section, as documented in "man unlang" ?
No, and I must be blind, because I have read the section and cannot find mention of it.
Sorry, the "redundant" section should do what you want.
Alan DeKok.
I cannot find a redundant section in this radiusd.conf
my radiusd.conf contains:
ippool main_pool {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.227.1 range-stop = 64.202.229.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
ippool main_pool2 {
# range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 64.202.237.1 range-stop = 64.202.239.254
# netmask: The network mask used for the ip's netmask = 255.255.255.0
# cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 762
# session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool2
# ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex2
# override: Will this ippool override a Framed-IP-Address already set override = no
# maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 }
**********************************It also has:
# Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail main_pool main_pool2
**********************************It also has:
# Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. main_pool main_pool2 # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above.
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth. Ivan Kalik Kalik Informatika ISP
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth. Ivan Kalik Kalik Informatika ISP
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night? Marco tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night? It now looks like: post-auth { # Get an address from the IP Pool. main_pool main_pool2 # sql redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log } Marco C. Coelho wrote:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
Marco
tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Don't you have a test server? Don't run tests on a production server. radclient can send simultaneous requests. http://wiki.freeradius.org/Radclient Ivan Kalik Kalik Informatika ISP Dana 15/1/2009, "Marco C. Coelho" <maillist1@argontech.net> piše:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
Marco
tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night? It now looks like: post-auth { # Get an address from the IP Pool. main_pool main_pool2 # sql redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log } Marco C. Coelho wrote:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
Marco
tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
radclient. Ivan Kalik Kalik Informatika ISP Dana 16/1/2009, "Marco C. Coelho" <maillist1@argontech.net> piše:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
It now looks like:
post-auth { # Get an address from the IP Pool. main_pool main_pool2 # sql redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
Marco C. Coelho wrote:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
Marco
tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/usershtml
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Ouch.... This change made radius stop issuing IP addresses. It would start without errors, but would then still authenticate a user, but would not issue a new IP address. Never good on a production server.... Yea I know, don't test on production server.... Duhh Is the syntax show below what you meant? Thanks, Marco Marco C. Coelho wrote:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
It now looks like:
post-auth { # Get an address from the IP Pool. main_pool main_pool2 # sql redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
Marco C. Coelho wrote:
I've moved redundant to be inside of post-auth and restarted radiusd..... Any ideas on how to test that it's working without waiting for a max usage night?
Marco
tnt@kalik.net wrote:
Below are all sections of the radius.conf that I've got the pools called out.
accounting { detail main_pool main_pool2 radutmp sql }
post-auth { # Get an address from the IP Pool. main_pool main_pool2 sql }
redundant { # added by mcc per suggestions 11/9/08 main_pool main_pool2 # # reply_log }
redundant section should be *inside* post-auth.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
------------------------------------------------------------------------
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Marco C. Coelho wrote:
This change made radius stop issuing IP addresses. It would start without errors, but would then still authenticate a user, but would not issue a new IP address. Never good on a production server.... Yea I know, don't test on production server.... Duhh
Is the syntax show below what you meant?
You can try using Postgresql, which doesn't have this problem. Or: post-auth { ... redundant { main_pool main_pool # just in case there was a race condition main_pool2 # if main_pool is down } ... } That might work. Alan DeKok.
Hi all, I am newbie here, I have a few problems like to seek professional advice. I have FreeRadius 2.0.4 running fine but when I check with radtest, it did'n't return any message accept or reject. I tried in /var/log/radius/radius.log or /usr/local/var/local/radius/radius.log but all were blank. further the FreeRadius server also not response to client requst. ]# /usr/local/sbin/radiusd -X FreeRADIUS Version 2.0.4, for host i686-pc-linux-gnu, built on Jan 20 2009 at 22:49:37 Copyright (C) 1999-2008 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including configuration file /usr/local/etc/raddb/snmp.conf including configuration file /usr/local/etc/raddb/eap.conf including configuration file /usr/local/etc/raddb/sql.conf including configuration file /usr/local/etc/raddb/sql/mysql/dialup.conf including configuration file /usr/local/etc/raddb/sql/mysql/counter.conf including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel including dictionary file /usr/local/etc/raddb/dictionary main { prefix = "/usr/local" localstatedir = "/usr/local/var" logdir = "/usr/local/var/log/radius" libdir = "/usr/local/lib" radacctdir = "/usr/local/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no pidfile = "/usr/local/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes security { max_attributes = 200 reject_delay = 1 status_server = yes } } client localhost { ipaddr = 127.0.0.1 netmask = 32 require_message_authenticator = yes secret = "testing123" shortname = "localhost" nastype = "portslave" } client 192.168.0.206/24 { require_message_authenticator = no secret = "testing123-1" shortname = "sB3010" nastype = "portslave" } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 zombie_period = 40 status_check = "status-server" ping_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = yes input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = no require_encryption = yes require_strong = yes with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/usr/local/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "ttls" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/server.pem" certificate_file = "/usr/local/etc/raddb/certs/server.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "Mars123" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "mschapv2" copy_request_to_tunnel = yes use_tunneled_reply = no virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/usr/local/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } } server { modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } } radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = 192.168.0.10 port = 1812 } Listening on authentication address 192.168.0.10 port 1812 Listening on proxy address 192.168.0.10 port 1814 Ready to process requests. ]# radtest John hello localhost 0 testing123-1 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 radclient: no response from server for ID 121 socket 3 _________________________________________________________________ It's simple! Sell your car for just $40 at CarPoint.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2...
On Wed, 2009-01-21 at 13:58 +0900, saman saman wrote:
radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = 192.168.0.10 port = 1812 } Listening on authentication address 192.168.0.10 port 1812 Listening on proxy address 192.168.0.10 port 1814 Ready to process requests.
]# radtest John hello localhost 0 testing123-1 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 User-Name = "John" User-Password = "hello" NAS-IP-Address = 192.168.1.5 NAS-Port = 0 radclient: no response from server for ID 121 socket 3
because it's only listening on 192.168.0.10 but you are trying to connect to localhost (and I assume that localhost means 127.0.0.1) try radtest John hello 192.168.0.10 0 testing123-1 or set up clients.conf with a setup for localhost Craig
If the freeradius.org is a virtual site bound to that IP address, hitting the IP may not display the content you're looking for. Which is why putting it into /etc/hosts resolved your issue, because your web browser is sending an HTTP request with a virtual site's domain name, and then the web server knows what content to deliver. Frank -----Original Message----- From: freeradius-users-bounces+frnkblk=iname.com@lists.freeradius.org [mailto:freeradius-users-bounces+frnkblk=iname.com@lists.freeradius.org] On Behalf Of Karl Auer Sent: Monday, September 29, 2008 9:59 AM To: FreeRadius users mailing list Subject: Re: Problem with freeradius.org website On Mon, 2008-09-29 at 16:11 +0200, Leander S. wrote:
I don't face this kind of problems ether. I'm located in Germany close to Stuttgart ... The problem you face has something to do with you're internet provider.
Thank you all for your swift diagnoses of problems at my end :-) If I went to 64.34.165.250, one of the two IP addresses for the name "freeradius.org", I got "500 service temporarily unavailable", apparently due to "maintenance downtime or capacity problems". I get the same message if I go to leia.telante.com. the canonical name of that address. The other IP address for the name "freeradius.org", 88.191.76.12, responded instantly, with a page from someone called Network RADIUS, Inc. The canonical name for the address, liberty.deployingradius.com, returned a page too. Attempts to go to the *name* "freeradius.org" always failed (timeouts). All of this was - and is! - completely repeatable. Oddly enough, when I force freeradius.org to be 64.34.165.250 using my local /etc/hosts file, everything works. No idea why. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@biplane.com.au) +61-2-64957160 (h) http://www.biplane.com.au/~kauer/ +61-428-957160 (mob) GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28
participants (9)
-
Alan DeKok -
Craig White -
Frank Bulk -
Karl Auer -
Leander S. -
Marco C. Coelho -
Michael Schwartzkopff -
saman saman -
tnt＠kalik.net