Thanks to both of you, it was a combination of both problems. It was listening on two interfaces plus it was unable to communicate properly with the Cisco Wireless controllers from the subnet it was in. Thomas E. Casartello, Jr. Infrastructure Technician Linux Specialist Department of Information Technology Westfield State College Wilson 105-A (413) 572-8245 E-Mail: tcasartello@wsc.ma.edu Red Hat Certified Technician (RHCT) -----Original Message----- From: freeradius-users-bounces+tcasartello=wsc.ma.edu@lists.freeradius.org [mailto:freeradius-users-bounces+tcasartello=wsc.ma.edu@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Monday, September 15, 2008 11:34 AM To: FreeRadius users mailing list Subject: Re: Fedora 9 EAP issue Casartello, Thomas wrote:
I have two servers with identical configuration and identical versions of freeradius, one running Fedora 8, one running Fedora 9. The Fedora 8 one works issueless, however with Fedora 9 I simply cannot get PEAP authentication to work with it. I am constantly getting this debug output: ... rad_recv: Access-Request packet from host 172.20.5.252 port 32769, id=4, length=194 Sending duplicate reply to client chaplin-wism-a.wsc.ma.edu port 32769 - ID: 4
You have a network interface with 2 IP addresses. (i.e. aliases). FreeRADIUS is receiving packets on the alias IP address, but sending responses from the main IP. This is because the *kernel* makes this choice. Make FreeRADIUS listen on the alias IP (and not "*"). Or, enable udpfromto via the "configure" script. Once that's enabled, the server will receive the destination IP of the RADIUS packet, and use that as the source IP. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html