New Server EAP issue

[David Peterson]

Ahh sure...  the issue was that the IP address I needed to use was a secondary.

I put the listener on the IP address but got this:

Tue Feb 19 14:54:23 2013 : Info: [ttls] Authenticate
Tue Feb 19 14:54:23 2013 : Info: [ttls] processing EAP-TLS
Tue Feb 19 14:54:23 2013 : Info: [ttls] Received TLS ACK
Tue Feb 19 14:54:23 2013 : Info: [ttls] ACK handshake is finished
Tue Feb 19 14:54:23 2013 : Info: [ttls] eaptls_verify returned 3
Tue Feb 19 14:54:23 2013 : Info: [ttls] eaptls_process returned 3
Tue Feb 19 14:54:23 2013 : Info: [ttls] Using saved attributes from the original Access-Accept
        Filter-Id := "TestProfile"
        Session-Timeout := 86400
Segmentation fault (core dumped)

What's the best way to bind to a particular IP address?

David

-----Original Message-----
From: Alan DeKok [mailto:aland at deployingradius.com] 
Sent: Tuesday, February 19, 2013 2:47 PM
To: David Peterson-WirelessConnections; FreeRadius users mailing list
Subject: Re: New Server EAP issue

David Peterson wrote:
> I can’t figure out where I went wrong.  The auth never gets to the 
> inner-tunnel.
> 
> David
> 
> root at hafreeradius1://usr/local/etc/raddb# radiusd -Xxx

  PLEASE use "radiusd -X".  The extra information with "-Xxx" isn't necessary.

> rad_recv: Access-Request packet from host 172.16.4.10 port 1812, 
> id=108,
> length=240
> Tue Feb 19 12:21:37 2013 : Info: Sending duplicate reply to client 
> Test NAS port 1812 - ID: 108 Sending Access-Challenge of id 108 to 
> 172.16.4.10 port 1812

  The NAS isn't seeing the response.  Go fix that.  It's a network issue.  I don't think it's a FreeRADIUS problem.

  Alan DeKok.