--- On Thu, 4/3/10, [email protected] 
<[email protected]> wrote:

From: [email protected] 
<[email protected]>
Subject: Freeradius-Users Digest, Vol 59, Issue 15
To: [email protected]
Date: Thursday, 4 March, 2010, 7:00 PM

Send Freeradius-Users mailing list submissions to
    [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.freeradius.org/mailman/listinfo/freeradius-users
or, via email, send a message with subject or body 'help' to
    [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Freeradius-Users digest..."


Today's Topics:

   1. Lost and confused (jin jin)
   2. Re: Can a wpa_supplicant talk to a Free Radius server without
      a NAS    in between? (Alan DeKok)
   3. Re: freeradius 1.1.8 hangs in rlm_perl on 64bit (Alan DeKok)
   4. Re: vlan and freeradius (Alan DeKok)
   5. Re: Lost and confused (Alan DeKok)
   6. Re: special query for authentication (Bob Brandt)
   7. Threads & Perl (Alexandr Kovalenko)


----------------------------------------------------------------------

Message: 1
Date: Thu, 4 Mar 2010 14:39:46 +0800 (SGT)
From: jin jin <[email protected]>
Subject: Lost and confused
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

This is the first time that I'm trying to set up a freeRADIUS server (Ver 
2.1.0) using Ubuntu 9.10 and I'm running into walls. I used the debug mode and 
this is the output 

Failed binding to socket: Address already in use 
/etc/freeradius/radiusd.conf[236]: Error binding to port for 0.0.0.0 port 1812

I googled but the closest match was a bug which was fixed earlier on. I'm not 
really sure what the above meant either. Do I have to connect my freeRADIUS 
server to my ADSL router first before I run freeRADIUS in debug mode? 

I am sorry if I have asked a few dumb questions, thanks in advance to the 
people replying to me. 

Best regards,
??????????????????? Jin



      New Email names for you! 
Get the Email name you've always wanted on the new @ymail and @rocketmail. 
Hurry before someone else does!
http://mail.promotions.yahoo.com/newdomains/sg/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.freeradius.org/pipermail/freeradius-users/attachments/20100304/0098ce62/attachment.html>

------------------------------

Message: 2
Date: Thu, 04 Mar 2010 07:50:47 +0100
From: Alan DeKok <[email protected]>
Subject: Re: Can a wpa_supplicant talk to a Free Radius server without
    a NAS    in between?
To: FreeRadius users mailing list
    <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

R C wrote:
> and even if i run 5-6 eapol_test processes at the same time, there will
> be only 5-6 parallel sessions at any given time.

  So... run more processes on more machines.

> 2. Since there are no free wpa supplicants that can generate multiple
> separate sessions at the same time, do you know of any paid tools
> (non-open source) that might generate about a 100,000 client requests?

  No. Generating 100K TLS requests will likely take dozens of CPUs, each
running at maximum capacity, just to do all of the crypto overhead.

  So... run more processes on more machines.

> I am just asking this question hoping some one would have had a similar
> requirement.

  No.  Because the requirement is rather extreme, a more than a little
pointless.

  i.e. Q: What happens when I send my web server 100K HTTPS connections?
       A: it dies.

       Q: How do I generate 100K HTTPS connections from clients?
       A: post a link on slashot.

  Alan DeKok.


------------------------------

Message: 3
Date: Thu, 04 Mar 2010 07:57:30 +0100
From: Alan DeKok <[email protected]>
Subject: Re: freeradius 1.1.8 hangs in rlm_perl on 64bit
To: FreeRadius users mailing list
    <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Olivier Bilodeau wrote:
> Any ideas on what it could be? perl? freeradius? 64bit? our perl code?

  <shrug>  That code is about 3 years old at this point, and no longer
actively maintained.

> We haven't switched to 2.x because of day to day activity overload but
> that could be a good reason for us to do the learning necessary to switch.

  It takes an hour or so to compile && test 2.1.8.  You don't need to
switch it to production until you've verified that it works.

  Alan DeKok.


------------------------------

Message: 4
Date: Thu, 04 Mar 2010 07:57:51 +0100
From: Alan DeKok <[email protected]>
Subject: Re: vlan and freeradius
To: FreeRadius users mailing list
    <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Jens Link wrote:
> @Alan: I would document VMPS in some more detail in the wiki if my
> access would be working. ;-)

  It seems to be fine now.

  Alan DeKok.


------------------------------

Message: 5
Date: Thu, 04 Mar 2010 07:58:50 +0100
From: Alan DeKok <[email protected]>
Subject: Re: Lost and confused
To: FreeRadius users mailing list
    <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

jin jin wrote:
> This is the first time that I'm trying to set up a freeRADIUS server
> (Ver 2.1.0) using Ubuntu 9.10 and I'm running into walls. I used the
> debug mode and this is the output
> 
> Failed binding to socket: Address already in use
> /etc/freeradius/radiusd.conf[236]: Error binding to port for 0.0.0.0
> port 1812

  Stop the server before you run it in debugging mode:

$ /etc/init.d/freeradius stop

  Alan DeKok.


------------------------------

Message: 6
Date: Thu, 4 Mar 2010 09:17:10 +0000
From: Bob Brandt <[email protected]>
Subject: Re: special query for authentication
To: FreeRadius users mailing list
    <[email protected]>
Message-ID:
    <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Someone else might have to help out here, but I remember seeing
something about using the huntgroups file, say:

Free         NAS-IP-Address == 192.168.1.1
Pay          NAS-IP-Address == 192.168.1.2

And then maybe in the users file use:

DEFAULT Huntgroup-Name == Free
        Service-Type = "Login-User",
        SomeOtherAttribute = "Free"

DEFAULT Huntgroup-Name == Pay
        Service-Type = "Login-User",
        SomeOtherAttribute ="Pay"

Maybe ??

Good Luck
Bob


------------------------------

Message: 7
Date: Thu, 4 Mar 2010 11:57:08 +0200
From: Alexandr Kovalenko <[email protected]>
Subject: Threads & Perl
To: FreeRadius users mailing list
    <[email protected]>
Message-ID:
    <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Hello!

I'm trying to find out if FreeRADIUS create separate Perl instance per
each thread (thread pool {}) (2.1.8) ?

The main question is: will FreeRADIUS with use of rlm_perl script be
able to serve multiple requests simultaneously or each next request
should wait until previous will finish?

-- 
Alexandr Kovalenko
http://uafug.org.ua/


------------------------------

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


End of Freeradius-Users Digest, Vol 59, Issue 15
************************************************

I tried to stop the server but I don't think it's working. Should I switch over 
to using other OS like OpenSuse or Debian instead? Sorry for the all the 
trouble. 

 * Stopping FreeRADIUS daemon freeradius                                        
start-stop-daemon: warning: failed to kill 6339: No such process
                                                                         [ OK ]

Here is the full output from using the debug command

Starting - reading configuration files ...
including configuration file /etc/freeradius/radiusd.conf
including configuration file /etc/freeradius/proxy.conf
including configuration file /etc/freeradius/clients.conf
including files in directory /etc/freeradius/modules/
including configuration file /etc/freeradius/modules/detail
including configuration file /etc/freeradius/modules/wimax
including configuration file /etc/freeradius/modules/pam
including configuration file /etc/freeradius/modules/files
including configuration file /etc/freeradius/modules/expiration
including configuration file /etc/freeradius/modules/echo
including configuration file /etc/freeradius/modules/mac2vlan
including configuration file /etc/freeradius/modules/checkval
including configuration file /etc/freeradius/modules/mschap
including configuration file /etc/freeradius/modules/krb5
including configuration file /etc/freeradius/modules/detail.example.com
including configuration file /etc/freeradius/modules/pap
including configuration file /etc/freeradius/modules/mac2ip
including configuration file /etc/freeradius/modules/radutmp
including configuration file /etc/freeradius/modules/acct_unique
including configuration file /etc/freeradius/modules/policy
including configuration file /etc/freeradius/modules/exec
including configuration file /etc/freeradius/modules/counter
including configuration file /etc/freeradius/modules/inner-eap
including configuration file /etc/freeradius/modules/etc_group
including configuration file /etc/freeradius/modules/linelog
including configuration file /etc/freeradius/modules/sql_log
including configuration file /etc/freeradius/modules/logintime
including configuration file /etc/freeradius/modules/attr_filter
including configuration file /etc/freeradius/modules/preprocess
including configuration file /etc/freeradius/modules/realm
including configuration file /etc/freeradius/modules/expr
including configuration file /etc/freeradius/modules/chap
including configuration file /etc/freeradius/modules/attr_rewrite
including configuration file /etc/freeradius/modules/sradutmp
including configuration file /etc/freeradius/modules/ippool
including configuration file /etc/freeradius/modules/always
including configuration file /etc/freeradius/modules/ldap
including configuration file /etc/freeradius/modules/passwd
including configuration file /etc/freeradius/modules/digest
including configuration file /etc/freeradius/modules/unix
including configuration file /etc/freeradius/modules/smbpasswd
including configuration file /etc/freeradius/modules/detail.log
including configuration file /etc/freeradius/eap.conf
including configuration file /etc/freeradius/policy.conf
including files in directory /etc/freeradius/sites-enabled/
including configuration file /etc/freeradius/sites-enabled/inner-tunnel
including configuration file /etc/freeradius/sites-enabled/default
including dictionary file /etc/freeradius/dictionary
main {
    prefix = "/usr"
    localstatedir = "/var"
    logdir = "/var/log/freeradius"
    libdir = "/usr/lib/freeradius"
    radacctdir = "/var/log/freeradius/radacct"
    hostname_lookups = no
    max_request_time = 30
    cleanup_delay = 5
    max_requests = 1024
    allow_core_dumps = no
    pidfile = "/var/run/freeradius/freeradius.pid"
    checkrad = "/usr/sbin/checkrad"
    debug_level = 0
    proxy_requests = yes
 log {
    stripped_names = no
    auth = no
    auth_badpass = no
    auth_goodpass = no
 }
 security {
    max_attributes = 200
    reject_delay = 1
    status_server = yes
 }
}
 client localhost {
    ipaddr = 127.0.0.1
    require_message_authenticator = no
    secret = "testing123"
    nastype = "other"
 }
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_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 = no
    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 = yes
    require_encryption = no
    require_strong = no
    with_ntdomain_hack = no
  }
 Module: Linked to module rlm_unix
 Module: Instantiating unix
  unix {
    radwtmp = "/var/log/freeradius/radwtmp"
  }
 Module: Linked to module rlm_eap
 Module: Instantiating eap
  eap {
    default_eap_type = "md5"
    timer_expire = 60
    ignore_unknown_eap_types = no
    cisco_accounting_username_bug = no
    max_sessions = 2048
  }
 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"
   }
Ignoring EAP-Type/tls because we do not have OpenSSL support.
Ignoring EAP-Type/ttls because we do not have OpenSSL support.
Ignoring EAP-Type/peap because we do not have OpenSSL support.
 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 = "/etc/freeradius/users"
    acctusersfile = "/etc/freeradius/acct_users"
    preproxy_usersfile = "/etc/freeradius/preproxy_users"
    compat = "no"
  }
 Module: Checking session {...} for more modules to load
 Module: Linked to module rlm_radutmp
 Module: Instantiating radutmp
  radutmp {
    filename = "/var/log/freeradius/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 = "/etc/freeradius/attrs.access_reject"
    key = "%{User-Name}"
  }
 }
}
 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 = "/etc/freeradius/huntgroups"
    hints = "/etc/freeradius/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 = 
"/var/log/freeradius/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 = "/etc/freeradius/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 = *
    port = 0
Failed binding to socket: Address already in use 
/etc/freeradius/radiusd.conf[236]: Error binding to port for 0.0.0.0 port 1812
la...@lauwk-desktop:~$ 

Best regards,
                    Jin



      New Email names for you! 
Get the Email name you&#39;ve always wanted on the new @ymail and @rocketmail. 
Hurry before someone else does!
http://mail.promotions.yahoo.com/newdomains/sg/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to