"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
> Ok i am sorry that i waste your time with these nonsense but i have spent 3
> months trying to do something that has no value...
My suggestion is that next time, you find out more about the
protocol you're trying to modify before working on chang
d enough to give me some directions?
Please help. I am desperate
From: Doug Hardie <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Source code Date: Wed, 1 Dec 2004 10:36:46 -0800
On Dec 1, 2004, at 10:17, Alan DeKok wrote:
"Panagiotis Mavros" <[E
ED]
To: [EMAIL PROTECTED]
Subject: Re: Source code Date: Wed, 1 Dec 2004 10:36:46 -0800
On Dec 1, 2004, at 10:17, Alan DeKok wrote:
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
we are proposing a lightweight WLAN roaming architecture. This means that
we
implement a roaming ar
On Dec 1, 2004, at 10:17, Alan DeKok wrote:
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
we are proposing a lightweight WLAN roaming architecture. This means
that we
implement a roaming architecture for a small community. The scenario
is
Client-->AP-->foreign server -->Home server and so on...
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
> we are proposing a lightweight WLAN roaming architecture. This means that we
> implement a roaming architecture for a small community. The scenario is
> Client-->AP-->foreign server -->Home server and so on...
> All this is done using EAP-MD5 authen
--On Wednesday, December 01, 2004 10:34:22 +0200 Panagiotis Mavros
<[EMAIL PROTECTED]> wrote:
OK
we are proposing a lightweight WLAN roaming architecture. This means that
we implement a roaming architecture for a small community. The scenario is
Client-->AP-->foreign server -->Home server and so
password and radius server have the exact length in its packets for these
attributes.
I havent searched yet about how EAP passes the password.I "know" the
procedure but i havent read yet the rfcs...
thanks
From: "Alan DeKok" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECT
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
> Sorry to bother you but it seems that i havent make my self clear about
> what i want to do.
Details help a lot. So far, you've been resisting providing details.
> User-Name and Password attributes MUST be EXACT 15 and 32 octets
> long(15 for
simple module or just an even smaller perl script that will
check the corresponding attributes in the authorize section and return reject if
they are not exactly what you expect.
From: "Alan DeKok" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Source code Date: Tue, 30 Nov 2004 09:30:21 -0500
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
> I understand that freeradius is based on RFCs and that changing some
> attributes modifies the protocol. But in my case
"Panagiotis Mavros" <[EMAIL PROTECTED]> wrote:
> I understand that freeradius is based on RFCs and that changing some
> attributes modifies the protocol. But in my case I want every radius packet
> to have fixed User-Name and Password length (because my thesis
> implementation says so!).
I co
the length of these attributes when I use EAP-MD5 authentication.
From: "Alan DeKok" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Source code Date: Mon, 29 Nov 2004 17:28:50 -0500
"jh vg" <[EMAIL PROTECTED]> wrote:
> i am writi
"jh vg" <[EMAIL PROTECTED]> wrote:
> i am writing a thesis about WLAN roaming with radius server. We are trying
> to shrink the length of radius packets.
Huh? If you shrink the packets, then you won't be using RADIUS.
> I want to set the length of User-Name and User-Password attribute to
> be
To be more specific we are using EAP-MD5 authentication (i dont know if it
matters...)
From: "jh vg" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Source code
Date: Mon, 29 Nov 2004 21:07:19 +0200
Hi
i am writing a thesis about WLAN roaming with radius server. We
14 matches
Mail list logo
