Re: FreeRadius seems to be working, but not getting it to respond

2006-11-07 Thread Michelle Manning

Thank you
As it turns out , there were a couple of little things wrong with the 
radius set up - SSL being the worst,
but the chillispot wasn't set up correctly - and I assumed that it was 
cause it worked for the other server.
That's what I get for assuming...so now I am doing a little bit of clean 
up but should be good to go.

Thanks all..
Michelle

Dennis Skinner wrote:


Michelle Manning wrote:
 


And - the log file in /usr/local/var/log/radius has nothing in it. I was
hoping that that would give me some clues
   



FYI...you will get either the debug output from running radiusd -X *or*
output in the log file.  Not both.

Also, if you want to know if iptables is running, ask it:

iptables -nL

man iptables

On CentOS/RedHat, you can stop iptables by doing this:

/etc/init.d/iptables stop

 

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


RE: FreeRadius seems to be working, but not getting it to respond

2006-11-06 Thread King, Michael
Does CENTOS have a built-in firewall?  (IPTABLES)  Does it have holes
(Rules, exceptions) poked in it so that the RADIUS packets get thru?

Ports 1812 and 1813.  I'm not sure if it's TCP or UDP, I always see them
referenced together, so I opened both. 

 -Original Message-
 From: 
 [EMAIL PROTECTED]
 g 
 [mailto:[EMAIL PROTECTED]
adius.org] On Behalf Of Michelle Manning
 Sent: Monday, November 06, 2006 11:12 AM
 To: FreeRadius users mailing list
 Subject: FreeRadius seems to be working, but not getting it 
 to respond 
 
 Hi,
 I have been reading the list for a couple of days now and 
 maybe I have missed something - but here goes.
 My set up is the following - Linksys Router with DD-WRT 
 running on it. 
 It does work as it connects to a older version of Radius on 
 another server. The newer server is CENTOS with FreeRadius 
 1.1.3 - I changed the config files and the information below 
 is from running Radius in debug mode. From what I can see it 
 should be happy. I have the DD-WRT pointing to the new server 
 - the hotspotlogin.cgi is in the correct place and configured 
 correctly. I also have PhpMyPrepaid on the server - and do 
 wonder if this is my problem - but I don't think so
 
 Any ideas? Is there something in this 'log' file that jumps 
 out at any of you?
 
 And - the log file in /usr/local/var/log/radius has nothing 
 in it. I was hoping that that would give me some clues
 
 Please help.
 
 Michelle
 
 *
 Starting - reading configuration files ...
 reread_config:  reading radiusd.conf
 Config:   including file: /usr/local/etc/raddb/proxy.conf
 Config:   including file: /usr/local/etc/raddb/clients.conf
 Config:   including file: /usr/local/etc/raddb/snmp.conf
 Config:   including file: /usr/local/etc/raddb/eap.conf
 Config:   including file: /usr/local/etc/raddb/sql.conf
  main: prefix = /usr/local
  main: localstatedir = /usr/local/var
  main: logdir = /usr/local/var/log/radius
  main: libdir = /usr/local/lib
  main: radacctdir = /usr/local/var/log/radius/radacct
  main: hostname_lookups = no
  main: max_request_time = 30
  main: cleanup_delay = 5
  main: max_requests = 1024
  main: delete_blocked_requests = 0
  main: port = 0
  main: allow_core_dumps = no
  main: log_stripped_names = no
  main: log_file = /usr/local/var/log/radius/radius.log
  main: log_auth = no
  main: log_auth_badpass = no
  main: log_auth_goodpass = no
  main: pidfile = /usr/local/var/run/radiusd/radiusd.pid
  main: user = radiusd
  main: group = radiusd
  main: usercollide = no
  main: lower_user = no
  main: lower_pass = no
  main: nospace_user = no
  main: nospace_pass = no
  main: checkrad = /usr/local/sbin/checkrad
  main: proxy_requests = yes
  proxy: retry_delay = 5
  proxy: retry_count = 3
  proxy: synchronous = no
  proxy: default_fallback = yes
  proxy: dead_time = 120
  proxy: post_proxy_authorize = yes
  proxy: wake_all_if_all_dead = no
  security: max_attributes = 200
  security: reject_delay = 1
  security: status_server = no
  main: debug_level = 0
 read_config_files:  reading dictionary
 read_config_files:  reading naslist
 Using deprecated naslist file.  Support for this will go away soon.
 read_config_files:  reading clients
 read_config_files:  reading realms
 radiusd:  entering modules setup
 Module: Library search path is /usr/local/lib
 Module: Loaded exec
  exec: wait = yes
  exec: program = (null)
  exec: input_pairs = request
  exec: output_pairs = (null)
  exec: packet_type = (null)
 rlm_exec: Wait=yes but no output defined. Did you mean output=none?
 Module: Instantiated exec (exec)
 Module: Loaded expr
 Module: Instantiated expr (expr)
 Module: Loaded PAP
  pap: encryption_scheme = crypt
 Module: Instantiated pap (pap)
 Module: Loaded CHAP
 Module: Instantiated chap (chap)
 Module: Loaded MS-CHAP
  mschap: use_mppe = yes
  mschap: require_encryption = no
  mschap: require_strong = no
  mschap: with_ntdomain_hack = no
  mschap: passwd = (null)
  mschap: ntlm_auth = (null)
 Module: Instantiated mschap (mschap)
 Module: Loaded System
  unix: cache = no
  unix: passwd = (null)
  unix: shadow = /etc/shadow
  unix: group = (null)
  unix: radwtmp = /usr/local/var/log/radius/radwtmp
  unix: usegroup = no
  unix: cache_reload = 600
 Module: Instantiated unix (unix)
 Module: Loaded eap
  eap: default_eap_type = md5
  eap: timer_expire = 60
  eap: ignore_unknown_eap_types = no
  eap: cisco_accounting_username_bug = no
 rlm_eap: Loaded and initialized type md5
 rlm_eap: Loaded and initialized type leap
  gtc: challenge = Password: 
  gtc: auth_type = PAP
 rlm_eap: Loaded and initialized type gtc
  mschapv2: with_ntdomain_hack = no
 rlm_eap: Loaded and initialized type mschapv2
 Module: Instantiated eap (eap)
 Module: Loaded preprocess
  preprocess: huntgroups = /usr/local/etc/raddb/huntgroups
  preprocess: hints = /usr/local/etc/raddb/hints
  preprocess: with_ascend_hack = no
  preprocess: ascend_channels_per_line = 23
  

Re: FreeRadius seems to be working, but not getting it to respond

2006-11-06 Thread Dennis Skinner
Michelle Manning wrote:
 And - the log file in /usr/local/var/log/radius has nothing in it. I was
 hoping that that would give me some clues

FYI...you will get either the debug output from running radiusd -X *or*
output in the log file.  Not both.

Also, if you want to know if iptables is running, ask it:

iptables -nL

man iptables

On CentOS/RedHat, you can stop iptables by doing this:

/etc/init.d/iptables stop

-- 
Dennis Skinner
Systems Administrator
BlueFrog Internet
http://www.bluefrog.com
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html