:10 PM
To: FreeRadius users mailing list
Subject: Re: radwho not working
Clint Petty wrote:
I am not blaming, I am just wanting to get the radwho command to work.
That is *entirely* the wrong attitude. There is no just get it to
work. There *are* multiple pieces involved, each of which has
On 7 Oct 2013, at 22:39, Clint Petty cpe...@luthresearch.com wrote:
Hi Alan,
Well I discovered a way to display a list of all active users without having
to implement FreeRadius accounting, which BTW is not as straight forward as
it should be.
I was able to display all active users
Clint Petty wrote:
Hi Alan,
Well I discovered a way to display a list of all active users without having
to implement FreeRadius accounting, which BTW is not as straight forward as
it should be.
I was able to display all active users through my StrongSwan server, with the
simple
Hi Clint,
On Thu, Oct 03, 2013 at 09:53:57PM +, Clint Petty wrote:
...
[detail] expand: %t - Thu Oct 3 21:45:27 2013
++[detail] returns ok
++[unix] returns ok
[radutmp] expand: /var/log/radius/radutmp - /var/log/radius/radutmp
[radutmp] expand: %{User-Name} - test
Hi,
I would like to display the active Radius connections. When I run radwho I
get the following results (showing nothing but the titles) even though I know
I have an active connection:
using the utmp/wtmp modules? what does your FreeRADIUS debug show when
someone logging in?
alan
-
List
: freeradius-users-bounces+me=company@lists.freeradius.org
[mailto:freeradius-users-bounces+me=company@lists.freeradius.org] On Behalf
Of a.l.m.bu...@lboro.ac.uk
Sent: Thursday, October 03, 2013 1:32 AM
To: FreeRadius users mailing list
Subject: Re: radwho not working
Hi,
I would like
Clint Petty wrote:
Below is the results from radiusd -X (debug mode), while logging in:
rad_recv: Access-Request packet from host xx.xx.xx.79 port 40379, id=79,
length=138
The radwho file logs *accounting* packets. That is an
*authentication* packet.
You're blaming FreeRADIUS because
Of Alan DeKok
Sent: Thursday, October 03, 2013 10:53 AM
To: FreeRadius users mailing list
Subject: Re: radwho not working
cpetty wrote:
Below is the results from radiusd -X (debug mode), while logging in:
rad_recv: Access-Request packet from host xx.xx.xx.79 port 40379, id=79,
length=138
Hi,
I am not blaming, I am just wanting to get the radwho command to work. I
have now turned on accounting info to be sent from the StrongSwan server to
the FreeRadius server. For I can see the accounting info in
/var/log/radius/radacct/IP_Address/detail-20131003 file. However I am
, 2013 2:17 PM
To: FreeRadius users mailing list
Subject: Re: radwho not working
Hi,
I am not blaming, I am just wanting to get the radwho command to work. I
have now turned on accounting info to be sent from the StrongSwan server to
the FreeRadius server. For I can see the accounting info
Clint Petty wrote:
I am not blaming, I am just wanting to get the radwho command to work.
That is *entirely* the wrong attitude. There is no just get it to
work. There *are* multiple pieces involved, each of which has to be
verified. I'm trying to convince you to use a methodical approach.
I would like to display the active Radius connections. When I run radwho I get
the following results (showing nothing but the titles) even though I know I
have an active connection:
# radwho
Login Name What TTY When FromLocation
#
-
List
12 matches
Mail list logo