dave anderson wrote:
> Also the raddact table has empty field for calling station-id for wimax.
> I know wimax has this field in hex rather than ascii which is a problem
> addressed wimax.c for auth. Changing the library to octet instead sting
> solves it for auth.
Don't. Instead, list t
Also the raddact table has empty field for calling station-id for wimax.
I know wimax has this field in hex rather than ascii which is a problem
addressed wimax.c for auth. Changing the library to octet instead sting
solves it for auth.
Can you tell me which module or .c to look at for repa
Alan,
Thanks for your answer.
Can you point me to a document or website where the following mechanism
is described well ?
ie MSCHAPv2 Radius Client -> Freeradius does the MSCHAPv2 challenge ? ->
auth is delegated to external script receiving attributes like username
and password in clear ->
Ok thanks, so for the first item I can just put some function in to
calculate it as I want or static code them.
-Original Message-
From: Alan DeKok [mailto:al...@deployingradius.com]
Sent: February 14, 2009 10:32 AM
To: FreeRadius users mailing list
Subject: Re: FW: wimax.c
dave anderso
dave anderson wrote:
> However to populate these other variable into the reply such as Session
> reply, it is not clear how to do so:
>
> WiMAX-AAA-Session-ID = ?
> WiMAX-HA-RK-SPI = ?
> WiMAX-HA-RK-Lifetime = ?
The WiMAX specifications really aren't clear how most
Norbert Wegener wrote:
>> The hope is that we can add TACACS+ support to FreeRADIUS in a future
>> version. That will help with migration.
>>
> Can this be expected in the foreseeable future?
Maybe within 6 months? We've been involved with the RadSec documents
(RADIUS over TLS over TCP).
Andrew Hall wrote:
> On a similar note does anyone know if O'Reilly plan to update their RADIUS
> book?
They don't. The book sold well initially (i.e. the first few months).
After that, people realized it was less than helpful.
I've been trying to write a book for a while. I've recently f
Arran Cudbard-Bell wrote...
> Maybe because it was written 6 years ago, and very few of the
> freeRADIUS 1.* examples will still work with 2
I see your point but why deny users access to this information ?
Surely all that's required is a note informing them of this.
I administer a legacy 1.
Alan DeKok schrieb:
Nicholas R. Cappelletti wrote:
In the recent weeks, I have come across some downfalls to using TACACS+ such as
no 802.1x authentication, no WPA integration, and the impossible integration
into both Kerberos and LDAP.
I hate to sound naive, but like many who need help, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Hall wrote:
> I'd just like to make other subscribers / searchers / admins
> pulling their hair out aware of the FreeRADIUS LDAP HOWTO available
> here...
>
> http://freeradius.org/radiusd/doc/ldap_howto.txt
>
> For some reason it doesn't seem t
I'd just like to make other subscribers / searchers / admins pulling
their hair out aware of the FreeRADIUS LDAP HOWTO available here...
http://freeradius.org/radiusd/doc/ldap_howto.txt
For some reason it doesn't seem to be linked to on any main website or
wiki page - bizarrely including the HOWT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marinko Tarlac wrote:
> Hi friends.
>
> I have small problem with freeradius and accounting (with
> database). Something is closing opened sessions and I can't see
> what is the reason. It seems that accounting_onoff_query was
> triggered by "something
Hi friends.
I have small problem with freeradius and accounting (with database).
Something is closing opened sessions and I can't see what is the reason.
It seems that accounting_onoff_query was triggered by "something" and
acctterminatecause field is empty so I don't see anything.
accountin
13 matches
Mail list logo
