Using freeradius, the system enters in an infinite loop
Hello out there, I am using freeradius2 in a raspberry pi3 with last version of LEDE and FreeRADIUS Version 2.2.9, and it happens something really weird, an infinite loop when a user tries to connect from a wifi hotspot. After installing freeradius, I only change 2 things: Add:ricardo Cleartext-Password := “testing”to /etc/freeradius2/users Comment out this# interface = br-lan from /etc/freeradius2/radiusd.conf I test the radius server using:root@LEDE:/etc/freeradius2# echo "User-Name = ricardo, User-Password = testing" | radclient -x 127.0.0.1 auth testing123 And it works:Sending Access-Request of id 28 to 127.0.0.1 port 1812 User-Name = "ricardo" User-Password = "testing"rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=28, length=20 However, when I setup WPA 2 Enterprise in the LEDE router (the same with freeradius server) and a user tries to connect, this infinite loop happens:https://vimeo.com/233192357 No error or warning message when running radiusd -XXXHere the log:https://gist.github.com/Ricardo1980/a5a7047fd0a03a6b10aea3b82f5e7cdf I think it is not related with certificates, because I can see this in the log:Sun Sep 10 14:07:31 2017 : Info: [peap] (other): SSL negotiation finished successfully Apart from that, I have this package installed:freeradius2-democerts And in the iPhone, it says that the expiration date is next year. Do you have any idea or suggestion? Probably it is a small detail but I cannot see it.Thanks a lot for your time.
On Sep 10, 2017, at 11:36 AM, Ricardo Ruiz via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am using freeradius2 in a raspberry pi3 with last version of LEDE and FreeRADIUS Version 2.2.9, and it happens something really weird, an infinite loop when a user tries to connect from a wifi hotspot. After installing freeradius, I only change 2 things: Add:ricardo Cleartext-Password := “testing”to /etc/freeradius2/users Comment out this# interface = br-lan from /etc/freeradius2/radiusd.conf I test the radius server using:root@LEDE:/etc/freeradius2# echo "User-Name = ricardo, User-Password = testing" | radclient -x 127.0.0.1 auth testing123 And it works:Sending Access-Request of id 28 to 127.0.0.1 port 1812 User-Name = "ricardo" User-Password = "testing"rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=28, length=20
However, when I setup WPA 2 Enterprise in the LEDE router (the same with freeradius server) and a user tries to connect, this infinite loop happens:https://vimeo.com/233192357
Vimeo links aren't generally helpful.
No error or warning message when running radiusd -XXXHere the log:https://gist.github.com/Ricardo1980/a5a7047fd0a03a6b10aea3b82f5e7cdf
Which doesn't show an infinite loop. It shows a user authenticating successfully. If the user asks to authenticate over and over again... blame the user. Not FreeRADIUS. Alan DeKok.
What do you mean exactly?In the log I see:Sun Sep 10 14:07:31 2017 : Info: [files] users: Matched entry ricardo at line 76 Sun Sep 10 14:07:31 2017 : Info: ++[files] = ok Does that mean the problem is in LEDE and not freeradius? On Sunday, 10 September 2017, 16:47, Alan DeKok <aland@deployingradius.com> wrote: On Sep 10, 2017, at 11:36 AM, Ricardo Ruiz via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am using freeradius2 in a raspberry pi3 with last version of LEDE and FreeRADIUS Version 2.2.9, and it happens something really weird, an infinite loop when a user tries to connect from a wifi hotspot. After installing freeradius, I only change 2 things: Add:ricardo Cleartext-Password := “testing”to /etc/freeradius2/users Comment out this# interface = br-lan from /etc/freeradius2/radiusd.conf I test the radius server using:root@LEDE:/etc/freeradius2# echo "User-Name = ricardo, User-Password = testing" | radclient -x 127.0.0.1 auth testing123 And it works:Sending Access-Request of id 28 to 127.0.0.1 port 1812 User-Name = "ricardo" User-Password = "testing"rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=28, length=20
However, when I setup WPA 2 Enterprise in the LEDE router (the same with freeradius server) and a user tries to connect, this infinite loop happens:https://vimeo.com/233192357
Vimeo links aren't generally helpful.
No error or warning message when running radiusd -XXXHere the log:https://gist.github.com/Ricardo1980/a5a7047fd0a03a6b10aea3b82f5e7cdf
Which doesn't show an infinite loop. It shows a user authenticating successfully. If the user asks to authenticate over and over again... blame the user. Not FreeRADIUS. Alan DeKok.
On Sep 10, 2017, at 12:07 PM, Ricardo Ruiz via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
What do you mean exactly?
What part of my response was not clear?
In the log I see:Sun Sep 10 14:07:31 2017 : Info: [files] users: Matched entry ricardo at line 76 Sun Sep 10 14:07:31 2017 : Info: ++[files] = ok
So? That doesn't show an infinite loop.
Does that mean the problem is in LEDE and not freeradius?
I said where the problem is... my message was very clear. Alan DeKok.
In the system log I see this: Sun Sep 10 16:34:28 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: associatedSun Sep 10 16:34:28 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-STARTED c0:cc:f8:ec:55:f8Sun Sep 10 16:34:28 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1Sun Sep 10 16:34:28 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociatedSun Sep 10 16:34:28 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociatedSun Sep 10 16:34:29 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: associatedSun Sep 10 16:34:29 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-STARTED c0:cc:f8:ec:55:f8Sun Sep 10 16:34:29 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1Sun Sep 10 16:34:29 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociatedSun Sep 10 16:34:29 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociatedSun Sep 10 16:34:29 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: associatedSun Sep 10 16:34:29 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-STARTED c0:cc:f8:ec:55:f8Sun Sep 10 16:34:29 2017 daemon.notice hostapd: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1Sun Sep 10 16:34:30 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociatedSun Sep 10 16:34:30 2017 daemon.info hostapd: wlan0: STA c0:cc:f8:ec:55:f8 IEEE 802.11: disassociated So, maybe the problem is in hostapd. For some reason is disconnecting the client just after is connected. I will review that... On Sunday, 10 September 2017, 17:58, Alan DeKok <aland@deployingradius.com> wrote: On Sep 10, 2017, at 12:07 PM, Ricardo Ruiz via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
What do you mean exactly?
What part of my response was not clear?
In the log I see:Sun Sep 10 14:07:31 2017 : Info: [files] users: Matched entry ricardo at line 76 Sun Sep 10 14:07:31 2017 : Info: ++[files] = ok
So? That doesn't show an infinite loop.
Does that mean the problem is in LEDE and not freeradius?
I said where the problem is... my message was very clear. Alan DeKok.
participants (2)
-
Alan DeKok -
Ricardo Ruiz