RE: Log auth message

18 Jun 2013

      Alan,

My mistake. I didnt give you exact information. 

I used test request ( in both cases ):
NAS-Identifier = "ggsn-01-bb2.orange.sk"
User-Name = "gre@test.sk"
User-Password = "tojejedno"
NAS-IP-Address = 213.151.211.225
NAS-Port-Type = Virtual
Called-Station-Id = "GRETEST01BB2.VPS"
Calling-Station-Id = "421995222222"
Service-Type = Framed-User
Framed-Protocol = GPRS-PDP-Context
Acct-Session-Id = "d597d9250ac7aeba"
Acct-Multi-Session-Id = "d597d92505600f87"

For testing i used this freeradius version:
radiusd: FreeRADIUS Version 3.0.0, for host x86_64-unknown-linux-gnu, built on May 16 2013 at 19:51:06
Copyright (C) 1999-2013 The FreeRADIUS server project and contributors.
...

Configuration ( for logging in radiusd.conf ):
Log {
        destination = files
        file = /app_log/radius/radius.log
        auth = yes
        auth_badpass = yes
        auth_goodpass = yes
}

Difference between cases are runtime parameters:
1. /storage/app/radius/freeradius-3.0.0/sbin/radiusd -d /storage/app/radius/raddb/auth
2. /storage/app/radius/freeradius-3.0.0/sbin/radiusd -x -d /storage/app/radius/raddb/auth

In case 1. :
When i sent test request 
radiusd@tdrad1test:/storage/app/radius/test$ ./run-auth.sh gre/auth1.req 1
Sending Access-Request of id 87 to 127.0.0.1 port 1812
	NAS-Identifier = "ggsn-01-bb2.orange.sk"
	User-Name = "gre@test.sk"
	User-Password = "tojejedno"
	NAS-IP-Address = 213.151.211.225
	NAS-Port-Type = Virtual
	Called-Station-Id = "GRETEST01BB2.VPS"
	Calling-Station-Id = "421995222222"
	Service-Type = Framed-User
	Framed-Protocol = GPRS-PDP-Context
	Acct-Session-Id = "d597d9250ac7aeba"
	Acct-Multi-Session-Id = "d597d92505600f87"
rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=87, length=44
	Framed-Protocol = PPP
	Service-Type = Framed-User
	Framed-IP-Address = 10.10.10.1
	Framed-IP-Netmask = 255.255.255.255

	   Total approved auths:  1
	     Total denied auths:  0
	       Total lost auths:  0
Test result: [  OK  ]

I will not see any auth log message in the main radius log file /app_log/radius/radius.log ( somethink like ):
Tue Jun 18 08:12:55 2013 : Auth: Login OK: [gre@test.sk/tojejedno] (from client IPSECgtw-01-BB1 port 997 cli 421995222222) 

In case 2. Is no problem of course.

Thx.

-----Original Message-----
From: freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org [mailto:freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org] On Behalf Of Alan DeKok
Sent: Monday, June 17, 2013 4:37 PM
To: FreeRadius users mailing list
Subject: Re: Log auth message

BALSIANOK, Peter wrote:
...
Is it OK, when i don`t see any log message for authetification process 
( when i run radiusd only with parameter –d ) ?
Yes.
...
Log output:
Mon Jun 17 14:01:55 2013 : Info: Loaded virtual server <default> Mon 
Jun 17 14:01:55 2013 : Info: Loaded virtual server default Mon Jun 17 
14:01:55 2013 : Info: Ready to process requests.
No log messages for authentification process
You do realize that the server logs packets it receives, right?

  And if it receives no packets, it doesn't log anything?
...
When i add parameter –x  ( in command line ), i will see log 
message(s) marked ###
Running it as "radiusd -X" is only suggested in the FAQ, "man" page, web pages, and daily on this list.  But why would you do that?

  Follow the documentation.  it's not hard.

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