Alan DeKok wrote:
Dan Newcombe <[EMAIL PROTECTED]> wrote:
One thing I've noticed is on the non-PEAP packets, the src address of
the packet going to the IAS box is 172.28.240.73, whereas on the PEAP
packets, it is 127.0.0.1,
That's bad. That's the source of the problem, then.
I ha
Dan Newcombe <[EMAIL PROTECTED]> wrote:
> One thing I've noticed is on the non-PEAP packets, the src address of
> the packet going to the IAS box is 172.28.240.73, whereas on the PEAP
> packets, it is 127.0.0.1,
That's bad. That's the source of the problem, then.
I have *no* idea why that
Alan DeKok wrote:
Dan Newcombe <[EMAIL PROTECTED]> wrote:
The short of it is I'm trying to get 802.1x with PEAP to be proxied by
freeradius to an ias radius server.
Start simple. Use PAP, and "radtest" to send the packets. If that
makes FreeRADIUS proxy the packets, then go to PEAP
Dan Newcombe <[EMAIL PROTECTED]> wrote:
> The short of it is I'm trying to get 802.1x with PEAP to be proxied by
> freeradius to an ias radius server.
Start simple. Use PAP, and "radtest" to send the packets. If that
makes FreeRADIUS proxy the packets, then go to PEAP. Otherwise,
you're test
Okay...one step closer. I had been using a debian version of freeradius
1.0.2 and hacked in the eap-tls. I have since followed Ben Kenobi's
advice and "use the source". It appears to be sending packets to the
IAS box now, and I can cut the stuff out and use radclient and have IAS
respond, ho
Hi all.I've done my best to try and figure this out myself, but am
really stuck.
First the basics: An enterasys C2 switch setup to do 802.1x
authentication. This switch points to my freeradius server. Attached
to the swich is my XP notebook, which is setup to do 802.1x via PEAP.
On t
6 matches
Mail list logo
