Mike Bernhardt wrote:
> "It doesn't work" referred to the original question I posted with the same
> subject a few weeks ago. At that time I provided debug output.
Ah... that's the "failed creating proxy socket" issue. Weird.
> I tried this
> configuration with 2.1.7 and 2.1.8 but it "didn't w
10 11:12 PM
To: FreeRadius users mailing list
Subject: Re: STILL Trying to get tunneling to work- resolved, and a question
Mike Bernhardt wrote:
> Just to clarify my questions:
> If one of the servers I'm proxying to is dead, is there a way to reduce
the
> number of times freeradi
Mike Bernhardt wrote:
> Just to clarify my questions:
> If one of the servers I'm proxying to is dead, is there a way to reduce the
> number of times freeradius tries before failing over to the next one?
Read raddb/proxy.conf
> 2. Are there any ways to make this process more efficient, given th
k with the downstream servers?
-Original Message-
From: Mike Bernhardt [mailto:bernha...@bart.gov]
Sent: Friday, January 29, 2010 11:36 AM
To: 'freeradius-users@lists.freeradius.org'
Subject: Re: STILL Trying to get tunneling to work- resolved, and a question
I found the major pr
Mike Bernhardt wrote:
> I found the major problem that caused my configuration to not work. This was
> in regards to getting freeradius to proxy EAP/PEAP to IAS servers as
> standard CHAP.
? That's impossible. PEAP uses a MD4 hash of the password, and CHAP
uses an MD5 hash of the password. Yo
I found the major problem that caused my configuration to not work. This was
in regards to getting freeradius to proxy EAP/PEAP to IAS servers as
standard CHAP. I was using freeradius 2.1.7, and then 2.1.8 as recommended
by someone. Neither worked.
The solution was to back down to 2.1.4. Is this a
6 matches
Mail list logo
