RE: Re: can't connect to radius server

2006-05-23 Thread simon
I have tried running tcpdump, and I am getting packets from the client to the 
server:
09:38:42.376543 IP 10.10.1.1.bpmd  10.10.1.102.radius: RADIUS, Access Request 
(1), id: 0x00 length: 131
09:38:42.376543 IP 10.10.1.1.bpmd  10.10.1.102.radius: RADIUS, Access Request 
(1), id: 0x00 length: 129

Here is the output I get when I start the server in debug mode:

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 = (null)
main: group = (null)
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 = no
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 = yes
mschap: require_strong = yes
mschap: with_ntdomain_hack = no
mschap: passwd = (null)
mschap: authtype = MS-CHAP
mschap: ntlm_auth = (null)
Module: Instantiated mschap (mschap)
Module: Loaded System
unix: cache = no
unix: passwd = (null)
unix: shadow = (null)
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 = peap
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
tls: rsa_key_exchange = no
tls: dh_key_exchange = yes
tls: rsa_key_length = 512
tls: dh_key_length = 512
tls: verify_depth = 0
tls: CA_path = (null)
tls: pem_file_type = yes
tls: private_key_file = /usr/local/etc/raddb/certs/cert-srv.pem
tls: certificate_file = /usr/local/etc/raddb/certs/cert-srv.pem
tls: CA_file = /usr/local/etc/raddb/certs/demoCA/cacert.pem
tls: private_key_password = whatever
tls: dh_file = /usr/local/etc/raddb/certs/dh
tls: random_file = /usr/local/etc/raddb/certs/random
tls: fragment_size = 1024
tls: include_length = yes
tls: check_crl = no
tls: check_cert_cn = (null)
rlm_eap_tls: Loading the certificate file as a chain
rlm_eap: Loaded and initialized type tls
peap: default_eap_type = mschapv2
peap: copy_request_to_tunnel = no
peap: use_tunneled_reply = no
peap: proxy_tunneled_request_as_eap = yes
rlm_eap: Loaded and initialized type peap
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
preprocess: with_ntdomain_hack = no
preprocess: with_specialix_jetstream_hack = no
preprocess: with_cisco_vsa_hack = no
Module: Instantiated preprocess (preprocess)
Module: Loaded realm
realm: format = suffix
realm: delimiter = @
realm: ignore_default = no
realm: ignore_null = no
Module: Instantiated realm (suffix)
Module: Loaded files
files: usersfile = /usr/local/etc/raddb/users
files: acctusersfile = /usr/local/etc/raddb/acct_users
files: 

Re: can't connect to radius server

2006-05-23 Thread Alan DeKok
[EMAIL PROTECTED] wrote:
 When I run nmap on the Radius server, just watching port 1812, I get
 conflicting results depending on what machine I run nmap on.  When I
 test the port from the client machine, it returns saying the port is
 filtered, but when I run nmap on the actual server, it returns that
 the port is closed.  Not sure if this is normal or not.

  If the server is running, nmap *will* say that the port is open on
localhost.

  In any case, the definitive answer is that an external nmap says
it's filtered.  Delete the firewall rules that block the RADIUS ports.

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


RE: Re: can't connect to radius server

2006-05-23 Thread Laker Netman


--- [EMAIL PROTECTED] wrote:

 I have tried running tcpdump, and I am getting
 packets from the client to the server:
 09:38:42.376543 IP 10.10.1.1.bpmd 
 10.10.1.102.radius: RADIUS, Access Request (1), id:
 0x00 length: 131
 09:38:42.376543 IP 10.10.1.1.bpmd 
 10.10.1.102.radius: RADIUS, Access Request (1), id:
 0x00 length: 129
 
 Here is the output I get when I start the server in
 debug mode:
 
 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 = (null)
 main: group = (null)
 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 = no
 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 = yes
 mschap: require_strong = yes
 mschap: with_ntdomain_hack = no
 mschap: passwd = (null)
 mschap: authtype = MS-CHAP
 mschap: ntlm_auth = (null)
 Module: Instantiated mschap (mschap)
 Module: Loaded System
 unix: cache = no
 unix: passwd = (null)
 unix: shadow = (null)
 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 = peap
 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
 tls: rsa_key_exchange = no
 tls: dh_key_exchange = yes
 tls: rsa_key_length = 512
 tls: dh_key_length = 512
 tls: verify_depth = 0
 tls: CA_path = (null)
 tls: pem_file_type = yes
 tls: private_key_file =
 /usr/local/etc/raddb/certs/cert-srv.pem
 tls: certificate_file =
 /usr/local/etc/raddb/certs/cert-srv.pem
 tls: CA_file =
 /usr/local/etc/raddb/certs/demoCA/cacert.pem
 tls: private_key_password = whatever
 tls: dh_file = /usr/local/etc/raddb/certs/dh
 tls: random_file =
 /usr/local/etc/raddb/certs/random
 tls: fragment_size = 1024
 tls: include_length = yes
 tls: check_crl = no
 tls: check_cert_cn = (null)
 rlm_eap_tls: Loading the certificate file as a chain
 rlm_eap: Loaded and initialized type tls
 peap: default_eap_type = mschapv2
 peap: copy_request_to_tunnel = no
 peap: use_tunneled_reply = no
 peap: proxy_tunneled_request_as_eap = yes
 rlm_eap: Loaded and initialized type peap
 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
 preprocess: with_ntdomain_hack = no
 preprocess: with_specialix_jetstream_hack = no
 preprocess: with_cisco_vsa_hack = no
 Module: Instantiated preprocess (preprocess)
 Module: Loaded realm
 realm: format = suffix
 realm: delimiter = @
 realm: ignore_default = no
 realm: 

Re: can't connect to radius server

2006-05-18 Thread Christopher Carver
If the radius server in debugging mode isn't showing any sort of 
access-request coming from the client, then the requests simply aren't 
reach the server.  This could be due to firewalling, your client looking 
at the wrong host/port, or a variety of other things.  I'd suggest using 
tcpdump to see if the packets sent from the client are even reaching the 
radius server.


tcpdump port 1812

If you see nothing when the client should be sending access-requests 
then you have a networking issue to solve.


Chris Carver
Pennswoods.Net
Network Engineer

[EMAIL PROTECTED] wrote:

Hi,

I think I have my radius server configured properly (I followed the 
configuration advice in http://tldp.org/HOWTO/html_single/8021X-HOWTO/).

I can get it running (using radiusd -X) and see all the expected output.

I have also configured my AP to point to the correct location, and it is 
pingable from the radius server.

However, when I try to connect, user validation always fails. And the radius 
server (which is in debug mode) doesn't show me anything. It's like nothing is 
connecting to it at all. I also tried to test it using NTRadPing, and his won't 
connect either.

Any help or suggestions here would be appreciated. I am running version 1.1.1 
of freeRADIUS.

Thanks,

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


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


Re: can't connect to radius server

2006-05-18 Thread Laker Netman
Comments below

--- [EMAIL PROTECTED] wrote:

 Hi,
 
 I think I have my radius server configured properly
 (I followed the configuration advice in
 http://tldp.org/HOWTO/html_single/8021X-HOWTO/).
 
 I can get it running (using radiusd -X) and see all
 the expected output.

Please post this output, even if it's just the server
startup info.

 
 I have also configured my AP to point to the correct
 location, and it is pingable from the radius server.
 

So, the AP is configured with the RADIUS server's IP,
you have configured your FR clients.conf file with
the APs information and the shared secret is correct
on both devices?

Does your AP have any ping functionality?  If so, can
it ping the RADIUS server? Does the AP provide any
logging data indicating it connected to the RADIUS
server?  Sounds suspiciously as if the RADIUS box's
firewall settings may be at fault.

Laker

 However, when I try to connect, user validation
 always fails. And the radius server (which is in
 debug mode) doesn't show me anything. It's like
 nothing is connecting to it at all. I also tried to
 test it using NTRadPing, and his won't connect
 either.
 
 Any help or suggestions here would be appreciated. I
 am running version 1.1.1 of freeRADIUS.
 
 Thanks,
 
 Simon
 - 
 List info/subscribe/unsubscribe? See
 http://www.freeradius.org/list/users.html
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html