RP-PPPOE + RADIUS = no connection

sheddy · 05-05-2011, 04:55 PM

Hi,

i want to set up a pppoe server with radius support. the pppoe server works, because the authentification works with pap- or chap-secret file. i get no connection between ppp and radius server.

when i test the radius server with "radtest", it works. but if try to connect from a client to the ppp-server and the authentication shall use the radius server, it terminates the connection and says "pap authetification failed".

Quote:

May 2 11:09:24 ubuntu pppd[3356]: Plugin radius.so loaded.
May 2 11:09:24 ubuntu pppd[3356]: RADIUS plugin initialized.
May 2 11:09:24 ubuntu pppd[3356]: Plugin radattr.so loaded.
May 2 11:09:24 ubuntu pppd[3356]: RADATTR plugin initialized.
May 2 11:09:24 ubuntu pppd[3356]: pppd 2.4.5 started by root, uid 0
May 2 11:09:24 ubuntu pppd[3356]: Using interface ppp0
May 2 11:09:24 ubuntu pppd[3356]: Connect: ppp0 <--> /dev/pts/3
May 2 11:09:37 ubuntu pppd[3356]: PAP peer authentication failed for test
May 2 11:09:37 ubuntu pppd[3356]: Connection terminated.
May 2 11:09:37 ubuntu pppd[3356]: Exit.

can anybody help me to fix the problem?

best regards
sdy

baldy3105 · 05-06-2011, 02:48 AM

Can you get a trace for the PPP? If its PPPOE you should be able to Wireshark it. PPP authentication can be bi-directional so its possible that its only failing in one direction. Radtest just checks that a service can fetch credentials from the radius server. Maybe the PPOE service is unable to use the RADIUS credentials for outbound authentication or something. A trace might give you a better idea of whats going on.

sheddy · 05-06-2011, 06:55 AM

hi,

the pppoe- and radius server run on the same machine and the client is another machine and both are VMs.

PPPoE/Radius-Machine has two interfaces:

LAN: 192.168.0.50
WAN (Internet): dynamic IP from Router

Client has one interface with 192.168.0.100

i will try to post a trace from wireshark:

WS-Trace

If you need more information of the trace, i can post it.

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

This is my approach to set up both:

RP-PPPOE:
pppoe-server-options

Quote:

require-pap
lcp-echo-interval 10
lcp-echo-failure 2
ms-dns 213.191.74.18
ms-dns 213.191.74.19
plugin radius.so
plugin radattr.so

RADIUSCLIENT:

So, instead of using pap-secret file, i installed radiuslclient1 and edited the file server, so that the radiusclient and the radius server can communicate:

Quote:

# Make sure that this file is mode 600 (readable only to owner)!
#
#Server Name or Client/Server pair Key
#---------------- ---------------
#portmaster.elemental.net hardlyasecret
#portmaster2.elemental.net donttellanyone

192.168.0.50 radiustest123

RADIUS:

The radius server must know the secret, too. so i edited the radius server file clients.conf:

Quote:

client 192.168.0.0/24 {
secret = radiustest123
shortname = pppoe-to-radius
}

i think, that should be the setting for the communication between the radius and the radiusclient.

Now i need a user, so i edited the radius users file:

Quote:

"test" Cleartext-Password := "test123"

If i try to connect from client to pppoe-server, it will fail, because the pap authetication will fail. (see the log above this post).

I hope, i could give you some more information.

sdy

baldy3105 · 05-07-2011, 11:25 AM

Well you only have unidirectional authentication happening and its clearly being rejected rather than timing out or erroring in some way.
We can't see the radius request/response as the PPPOE server and radius server are on the same VM.

Can we get a the server log of the radius request? Does one even happen? i.e. can you see that the PPPOE server is actually triggering a radius transaction?

sheddy · 05-09-2011, 04:30 AM

1. how can you see that there is only uni-directional authentication? i cannnot see it in this trace

2. logs:

i think, there is no log for radius respectively there is no communication between ppp and radiusclient or radius, beacuse there is no logging. (or i took the worng log)

I started the radiusserver with "freeradius -X" to see what is happening.

Quote:

root@ubuntu:/etc/freeradius# freeradius -X
FreeRADIUS Version 2.1.9, for host i686-pc-linux-gnu, built on Jun 21 2010 at 19:17:04
Copyright (C) 1999-2009 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 v2.
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/echo
including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login
including configuration file /etc/freeradius/modules/digest
including configuration file /etc/freeradius/modules/unix
including configuration file /etc/freeradius/modules/mac2ip
including configuration file /etc/freeradius/modules/attr_filter
including configuration file /etc/freeradius/modules/sradutmp
including configuration file /etc/freeradius/modules/counter
including configuration file /etc/freeradius/modules/exec
including configuration file /etc/freeradius/modules/linelog
including configuration file /etc/freeradius/modules/checkval
including configuration file /etc/freeradius/modules/smbpasswd
including configuration file /etc/freeradius/modules/detail.example.com
including configuration file /etc/freeradius/modules/expiration
including configuration file /etc/freeradius/modules/radutmp
including configuration file /etc/freeradius/modules/otp
including configuration file /etc/freeradius/modules/expr
including configuration file /etc/freeradius/modules/pam
including configuration file /etc/freeradius/modules/ldap
including configuration file /etc/freeradius/modules/passwd
including configuration file /etc/freeradius/modules/ippool
including configuration file /etc/freeradius/modules/detail
including configuration file /etc/freeradius/modules/preprocess
including configuration file /etc/freeradius/modules/wimax
including configuration file /etc/freeradius/modules/mschap
including configuration file /etc/freeradius/modules/policy
including configuration file /etc/freeradius/modules/sql_log
including configuration file /etc/freeradius/modules/always
including configuration file /etc/freeradius/modules/cui
including configuration file /etc/freeradius/modules/mac2vlan
including configuration file /etc/freeradius/modules/realm
including configuration file /etc/freeradius/modules/etc_group
including configuration file /etc/freeradius/modules/inner-eap
including configuration file /etc/freeradius/modules/pap
including configuration file /etc/freeradius/modules/ntlm_auth
including configuration file /etc/freeradius/modules/krb5
including configuration file /etc/freeradius/modules/perl
including configuration file /etc/freeradius/modules/acct_unique
including configuration file /etc/freeradius/modules/chap
including configuration file /etc/freeradius/modules/detail.log
including configuration file /etc/freeradius/modules/files
including configuration file /etc/freeradius/modules/logintime
including configuration file /etc/freeradius/modules/smsotp
including configuration file /etc/freeradius/modules/attr_rewrite
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/default
including configuration file /etc/freeradius/sites-enabled/inner-tunnel
main {
user = "freerad"
group = "freerad"
allow_core_dumps = no
}
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
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
}
}
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
require_message_authenticator = no
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
irt = 2
mrt = 16
mrc = 5
mrd = 30
}
home_server_pool my_auth_failover {
type = fail-over
home_server = localhost
}
realm example.com {
auth_pool = my_auth_failover
}
realm LOCAL {
}
radiusd: #### Loading Clients ####
client localhost {
ipaddr = 127.0.0.1
require_message_authenticator = no
secret = "radiustest123"
}
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 = 4096
}
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 = "/etc/freeradius/certs/server.key"
certificate_file = "/etc/freeradius/certs/server.pem"
CA_file = "/etc/freeradius/certs/ca.pem"
private_key_password = "whatever"
dh_file = "/etc/freeradius/certs/dh"
random_file = "/etc/freeradius/certs/random"
fragment_size = 1024
include_length = yes
check_crl = no
cipher_list = "DEFAULT"
make_cert_command = "/etc/freeradius/certs/bootstrap"
cache {
enable = no
lifetime = 24
max_entries = 255
}
}
Module: Linked to sub-module rlm_eap_ttls
Module: Instantiating eap-ttls
ttls {
default_eap_type = "md5"
copy_request_to_tunnel = no
use_tunneled_reply = no
virtual_server = "inner-tunnel"
include_length = yes
}
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 = "/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
} # server
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 = "/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
} # modules
} # server
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 0
}
listen {
type = "acct"
ipaddr = *
port = 0
}
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on proxy address * port 1814
Ready to process requests.

after that i set up the firewall and satrtet the pppoe-server:

Quote:

iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o eth0 -j MASQUERADE
pppoe-server -C isp -L 192.168.0.50 -p /etc/ppp/allowips -I eth1

the /var/log/messages display the same again:

Quote:

tail -f -n10 /var/log/messages
May 9 02:10:48 ubuntu kernel: [ 355.205763] ip_tables: (C) 2000-2006 Netfilter Core Team
May 9 02:10:48 ubuntu kernel: [ 355.221296] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
May 9 02:10:48 ubuntu kernel: [ 355.222133] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
May 9 02:10:48 ubuntu kernel: [ 355.222134] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
May 9 02:10:48 ubuntu kernel: [ 355.222136] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
May 9 02:14:04 ubuntu pppd[2475]: Plugin radius.so loaded.
May 9 02:14:04 ubuntu pppd[2475]: RADIUS plugin initialized.
May 9 02:14:04 ubuntu pppd[2475]: Plugin radattr.so loaded.
May 9 02:14:04 ubuntu pppd[2475]: RADATTR plugin initialized.
May 9 02:14:04 ubuntu pppd[2475]: pppd 2.4.5 started by root, uid 0
May 9 02:14:04 ubuntu pppd[2475]: Using interface ppp0
May 9 02:14:04 ubuntu pppd[2475]: Connect: ppp0 <--> /dev/pts/5
May 9 02:14:07 ubuntu pppd[2475]: PAP peer authentication failed for hugo
May 9 02:14:07 ubuntu pppd[2475]: Connection terminated.
May 9 02:14:08 ubuntu pppd[2475]: Exit.

and now the radius.log shows the following one (NO logging!):

Quote:

root@ubuntu:~# tail -f -n10 /var/log/freeradius/radius.log
Mon May 9 01:23:36 2011 : Info: Loaded virtual server <default>
Mon May 9 01:23:37 2011 : Info: Ready to process requests.
Mon May 9 01:49:23 2011 : Info: Loaded virtual server inner-tunnel
Mon May 9 01:49:23 2011 : Info: Loaded virtual server <default>
Mon May 9 01:49:23 2011 : Error: Failed binding to authentication address * port 1812: Address already in use
Mon May 9 01:49:23 2011 : Error: /etc/freeradius/radiusd.conf[240]: Error binding to port for 0.0.0.0 port 1812
Mon May 9 01:49:37 2011 : Info: Exiting normally.
Mon May 9 02:05:08 2011 : Info: Loaded virtual server inner-tunnel
Mon May 9 02:05:09 2011 : Info: Loaded virtual server <default>
Mon May 9 02:05:09 2011 : Info: Ready to process requests.
Mon May 9 02:08:29 2011 : Info: Exiting normally.

Should i take another log-file?
I do not know to go on

best regards
sdy

(btw: i changed the user and pw in pppoe-server pap-secret file to "hugo" and "test123" and the radius users-file to "hugo" and "test098" to see the difference between radius and pap-secret)

baldy3105 · 05-09-2011, 03:03 PM

You can see that its only unidirectional as there is only one request-pair. For Bidirectional you would see both ends requesting authentication almost simultaneously.

At a guess I would set -

log {
stripped_names = yes
auth = yes
auth_badpass = yes
auth_goodpass = yes
}

Which I would hope should generate some output about the authentication attempt.

sheddy · 05-10-2011, 02:32 AM

I changed the log-part in radiusd.conf, but still no logging. Even if start the radius server with "freeradius -X", there is no log.

I installed freeradius via ubuntu synaptic. If i start my system, radius is started. I can kill the process and start it with "freeradius -X" again. If i kill the process, radius.log log this. But if i start radius with "freeradius -X" again, it will not be logged.

Only if i start the radius server with "freeradius -X", the debug modus display the following with "radtest hugo test098 192.168.0.50 0 radiustest123", but still NO logging in radius.log.

Quote:

[...]
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on proxy address * port 1814
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.0.50 port 37551, id=251, length=56
User-Name = "hugo"
User-Password = "test098"
NAS-IP-Address = 127.0.0.1
NAS-Port = 0
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
[suffix] No '@' in User-Name = "hugo", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP
++[eap] returns noop
++[unix] returns notfound
[files] users: Matched entry hugo at line 1
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
++[pap] returns updated
Found Auth-Type = PAP
+- entering group PAP {...}
[pap] login attempt with password "test098"
[pap] Using clear text password "test098"
[pap] User authenticated successfully
++[pap] returns ok
Login OK: [hugo/test098] (from client pppoe-to-radius port 0)
+- entering group post-auth {...}
++[exec] returns noop
Sending Access-Accept of id 251 to 192.168.0.50 port 37551
Finished request 0.
Going to the next request
Waking up in 4.9 seconds.
Cleaning up request 0 ID 251 with timestamp +3
Ready to process requests.

I also edited the radiusclient.conf

Quote:

authserver 192.168.0.50
acctserver 192.168.0.50

sheddy · 05-10-2011, 10:09 AM

i tried another configuration.

The first attempt was (which is still not working!)

Config 1 - not working

My second attempt was to split pppoe- and radius-server. i set up a new VM for the radius server:

Config 2 - working

And now i get the following outputs:

/var/log/messages

Quote:

May 10 07:59:08 ubuntu pppd[3512]: Plugin radius.so loaded.
May 10 07:59:08 ubuntu pppd[3512]: RADIUS plugin initialized.
May 10 07:59:08 ubuntu pppd[3512]: Plugin radattr.so loaded.
May 10 07:59:08 ubuntu pppd[3512]: RADATTR plugin initialized.
May 10 07:59:08 ubuntu pppd[3512]: pppd 2.4.5 started by root, uid 0
May 10 07:59:08 ubuntu pppd[3512]: Using interface ppp0
May 10 07:59:08 ubuntu pppd[3512]: Connect: ppp0 <--> /dev/pts/2
May 10 07:59:14 ubuntu pppd[3512]: PAP peer authentication succeeded for hugo
May 10 07:59:14 ubuntu pppd[3512]: found interface eth1 for proxy arp
May 10 07:59:14 ubuntu pppd[3512]: local IP address 192.168.0.50
May 10 07:59:14 ubuntu pppd[3512]: remote IP address 192.168.0.90

freeradius -X (still no logging in radius.log)

Quote:

[...]
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on proxy address * port 1814
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.0.50 port 46416, id=26, length=68
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = "hugo"
User-Password = "test098"
NAS-IP-Address = 192.168.1.54
NAS-Port = 0
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
[suffix] No '@' in User-Name = "hugo", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP
++[eap] returns noop
++[unix] returns notfound
[files] users: Matched entry hugo at line 1
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
++[pap] returns updated
Found Auth-Type = PAP
+- entering group PAP {...}
[pap] login attempt with password "test098"
[pap] Using clear text password "test098"
[pap] User authenticated successfully
++[pap] returns ok
Login OK: [hugo/test098] (from client xtramachine port 0)
+- entering group post-auth {...}
++[exec] returns noop
Sending Access-Accept of id 26 to 192.168.0.50 port 46416
Finished request 0.
Going to the next request
Waking up in 4.9 seconds.
rad_recv: Accounting-Request packet from host 192.168.0.50 port 49875, id=27, length=96
Acct-Session-Id = "4DC952C20DB800"
User-Name = "hugo"
Acct-Status-Type = Start
Service-Type = Framed-User
Framed-Protocol = PPP
Acct-Authentic = RADIUS
NAS-Port-Type = Virtual
Framed-IP-Address = 192.168.0.90
NAS-IP-Address = 192.168.1.54
NAS-Port = 0
Acct-Delay-Time = 0
+- entering group preacct {...}
++[preprocess] returns ok
[acct_unique] Hashing 'NAS-Port = 0,Client-IP-Address = 192.168.0.50,NAS-IP-Address = 192.168.1.54,Acct-Session-Id = "4DC952C20DB800",User-Name = "hugo"'
[acct_unique] Acct-Unique-Session-ID = "79b7bf85628f6381".
++[acct_unique] returns ok
[suffix] No '@' in User-Name = "hugo", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
++[files] returns noop
+- entering group accounting {...}
[detail] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.0.50/detail-20110510
[detail] /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.0.50/detail-20110510
[detail] expand: %t -> Tue May 10 07:59:02 2011
++[detail] returns ok
++[unix] returns ok
[radutmp] expand: /var/log/freeradius/radutmp -> /var/log/freeradius/radutmp
[radutmp] expand: %{User-Name} -> hugo
++[radutmp] returns ok
[attr_filter.accounting_response] expand: %{User-Name} -> hugo
attr_filter: Matched entry DEFAULT at line 12
++[attr_filter.accounting_response] returns updated
Sending Accounting-Response of id 27 to 192.168.0.50 port 49875
Finished request 1.
Cleaning up request 1 ID 27 with timestamp +476
Going to the next request
Waking up in 4.9 seconds.
Cleaning up request 0 ID 26 with timestamp +476
Ready to process requests.

So, it will work with 2 separate machines for radius and ppp. but why does it not work, if both servers are on the same machine/vm?! the settings are the same (except for the little customization for the radius vm).

baldy3105 · 05-15-2011, 02:05 PM

Hmm, difficult to say. You would need to concentrate on getting the logging working on both packages. Then you might have a chance of seeing where it is failing.