Hi,
I would like to achieve some kind of a tracking system for 802.11
wireless clients, therefore every login attempt should be accepted and
the necessary information (e.g. nas-ip-address, calling-station-id)
should be stored in an extra database table.
Example output:
rad_recv: Access-Request
On 11/10/10 11:22, c.schw...@funknetz.at wrote:
Hi,
I would like to achieve some kind of a tracking system for 802.11
wireless clients, therefore every login attempt should be accepted and
the necessary information (e.g. nas-ip-address, calling-station-id)
should be stored in an extra database
Hello!
I got a erroarea following logging and do not know where to look.
Can someone ajunte me?
rad_recv: Access-Request packet from host 127.0.0.1:42096, id=227, length=116
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = phlander
CHAP-Challenge =
On 09/10/10 15:01, Garber, Neal wrote:
Thanks to a lot of work by Phil Mayers, the server now has support for
Microsoft SoH in PEAP, normal RADIUS (MS VPN gateway), and in DHCP.
Wow! That *must* have been a lot of work! Thank you Phil.
Does this mean FreeRADIUS can now act as a Health
Daniel Sandulescu wrote:
Hello!
I got a erroarea following logging and do not know where to look.
Can someone ajunte me?
It means you've edited the default configuration, and broken it.
modcall[authorize]: module mschap returns noop for request 0
radius_xlat: ''
i.e. the SQL
Phil Mayers wrote:
I've tested it with WinXP SP3, Vista and Win7. There is one compile fix
needed which must have snuck through (attached)
I deleted all references to the REQUEST structure from src/lib/soh.c.
The library functions are for clients, not just the server.
The code in git
On 11/10/10 13:24, Alan DeKok wrote:
Phil Mayers wrote:
I've tested it with WinXP SP3, Vista and Win7. There is one compile fix
needed which must have snuck through (attached)
I deleted all references to the REQUEST structure from src/lib/soh.c.
The library functions are for clients, not
Phil Mayers wrote:
Indeed. Is there a good way besides the DEBUG macro to emit debugging
output in lib/*.c code?
Nope.
I imagine there will be SoH type/value or
type/len/value stuff that we'll want to log (but others that we won't -
it's probably too noisy as-is)
OK.
Also I guess the
Hi Alan,
Thank you, this helps. Will have another go at debugging from the NAS
side.
I'll post back once I get it working.
Jay
-Original Message-
From: freeradius-users-bounces+jkuhne=cisco@lists.freeradius.org
[mailto:freeradius-users-bounces+jkuhne=cisco@lists.freeradius.org]
Hi,
It's fairly useful though - you can enable it, and SoH-enabled clients
will submit info like:
snip
This can be punted to a virtual server, and you can assign a vlan or
reject authentication etc.
I've tested it with WinXP SP3, Vista and Win7. There is one compile fix
needed which
I upgraded to version 2.1.10 and now I have this erroare:
rad_recv: Access-Request packet from host 127.0.0.1 port 48934, id=235,
length=116
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = phlander
CHAP-Challenge =
Daniel Sandulescu wrote:
I upgraded to version 2.1.10 and now I have this erroare:
The entire point of the debug output is to *read* it. You have the
same problem as last time.
And even worse, you upgraded to 2.1.10, and left all of the
problematic configuration files in place.
--On Monday, October 11, 2010 14:24:07 +0200 Alan DeKok
al...@deployingradius.com wrote:
Phil Mayers wrote:
I've tested it with WinXP SP3, Vista and Win7. There is one compile fix
needed which must have snuck through (attached)
I deleted all references to the REQUEST structure from
On Sun, 2010-10-10 at 08:50 +0200, Alan DeKok wrote:
Jean-Francois Mousinho wrote:
I've tried to find a way of detail logging the packets sent by
freeradius to the client in the authentication phase but didn't found a
way of doing it. Maybe I've not looked correctly so I'm asking if it's
Returning, we came up here and do not know where erroarea ..
rad_recv: Access-Request packet from host 127.0.0.1 port 58178, id=244,
length=115
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = phlander
CHAP-Challenge =
One step closer by reverse-engineering a TAC example... but still not
quite working
# users file - initial bring up
jkuh...@asr_5_61 Cleartext-Password := hello1
Service-Type += Framed-User,
Framed-Protocol += PPP,
Cisco-Account-Info += NAMED_ACL_SERVICE,
Framed-IPv6-Prefix +=
Daniel Sandulescu wrote:
Returning, we came up here and do not know where erroarea ..
If you're not going to read the messages on this list, then I don't
see why you are posting questions.
You have DELETED the entire configuration. Why?
Use the configuration from 2.1.10. It's not hard.
Phil Mayers wrote:
Ok, the attached should be more sane
Debug messages shouldn't have \n. The log function adds the \n
itself.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 11/10/10 16:23, Alan DeKok wrote:
Phil Mayers wrote:
Ok, the attached should be more sane
Debug messages shouldn't have \n. The log function adds the \n
itself.
Yeah - that's in 0004-*.patch (I noticed it when using the excellent
raddebug to test that the SoH stuff appeared)
-
List
Is there a typical way to set an Auth-Type := Kerberos¹ when a user is part
of a specific realm? For testing purposes, I am able to add this to the
users¹ file:
DEFAULTAuth-Type := Kerberos
But, will need something based on realm in the future.
-
List info/subscribe/unsubscribe? See
On 11/10/2010 12:37, Phil Mayers wrote:
On 09/10/10 15:01, Garber, Neal wrote:
Thanks to a lot of work by Phil Mayers, the server now has support for
Microsoft SoH in PEAP, normal RADIUS (MS VPN gateway), and in DHCP.
Wow! That *must* have been a lot of work! Thank you Phil.
Does this mean
On 11/10/2010 22:14, James J J Hooper wrote:
On 11/10/2010 12:37, Phil Mayers wrote:
On 09/10/10 15:01, Garber, Neal wrote:
Thanks to a lot of work by Phil Mayers, the server now has support for
Microsoft SoH in PEAP, normal RADIUS (MS VPN gateway), and in DHCP.
Wow! That *must* have been a
Mathew Rowley wrote:
Is there a typical way to set an ‘Auth-Type := Kerberos’ when a user is
part of a specific realm? For testing purposes, I am able to add this to
the ‘users’ file:
DEFAULTAuth-Type := Kerberos
But, will need something based on realm in the future.
You can do
So I did, I deleted everything in / etc / raddb and I configuration, again
depending on the requirements there.
My question was, if I can see where misuse.
Sincerely,
Daniel
- Original Message -
From: Alan DeKok al...@deployingradius.com
To: FreeRadius users mailing list
24 matches
Mail list logo
