Fwd: Freeradius3 Empty authorize section
Hi all, Using FreeRADIUS Version 3.0.17. If non default ports are used (1712 below) getting Access-Reject with below error. Same works for 1812 port Debugs failed case ------------------ Fri Jul 27 11:44:17 2018 : Debug: (0) Received Access-Request Id 74 from 192.168.122.1:54017 to 192.168.122.1:1712 length 75 Fri Jul 27 11:44:17 2018 : Debug: (0) User-Name = "agnel" Fri Jul 27 11:44:17 2018 : Debug: (0) User-Password = "cisco" Fri Jul 27 11:44:17 2018 : Debug: (0) NAS-IP-Address = 10.105.236.107 Fri Jul 27 11:44:17 2018 : Debug: (0) NAS-Port = 0 Fri Jul 27 11:44:17 2018 : Debug: (0) Message-Authenticator = 0xddff1bd7dc9e5b44c3f0c9ecf089d325 Fri Jul 27 11:44:17 2018 : Debug: (0) session-state: No State attribute Fri Jul 27 11:44:17 2018 : Debug: (0) Empty authorize section. Using default return values. Fri Jul 27 11:44:17 2018 : ERROR: (0) No Auth-Type found: rejecting the user via Post-Auth-Type = Reject Fri Jul 27 11:44:17 2018 : Debug: (0) Failed to authenticate the user Fri Jul 27 11:44:17 2018 : Debug: (0) Using Post-Auth-Type Reject Fri Jul 27 11:44:17 2018 : Debug: (0) Post-Auth-Type sub-section not found. Ignoring. Fri Jul 27 11:44:17 2018 : Debug: (0) Delaying response for 1.000000 seconds Fri Jul 27 11:44:17 2018 : Debug: Waking up in 0.3 seconds. Fri Jul 27 11:44:17 2018 : Debug: Waking up in 0.6 seconds. Fri Jul 27 11:44:18 2018 : Debug: (0) Sending delayed response Fri Jul 27 11:44:18 2018 : Debug: (0) Sent Access-Reject Id 74 from 192.168.122.1:1712 to 192.168.122.1:54017 length 20 Fri Jul 27 11:44:18 2018 : Debug: Waking up in 3.9 seconds. Fri Jul 27 11:44:22 2018 : Debug: (0) Cleaning up request packet ID 74 with timestamp +7 Fri Jul 27 11:44:22 2018 : Info: Ready to process requests Debugs passed case ------------------- Fri Jul 27 11:45:04 2018 : Debug: (0) Received Access-Request Id 175 from 192.168.122.1:39458 to 192.168.122.1:1812 length 75 Fri Jul 27 11:45:04 2018 : Debug: (0) User-Name = "agnel" Fri Jul 27 11:45:04 2018 : Debug: (0) User-Password = "cisco" Fri Jul 27 11:45:04 2018 : Debug: (0) NAS-IP-Address = 10.105.236.107 Fri Jul 27 11:45:04 2018 : Debug: (0) NAS-Port = 0 Fri Jul 27 11:45:04 2018 : Debug: (0) Message-Authenticator = 0x0e54f6497f8d7966db4f4702ec76a282 Fri Jul 27 11:45:04 2018 : Debug: (0) session-state: No State attribute Fri Jul 27 11:45:04 2018 : Debug: (0) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default Fri Jul 27 11:45:04 2018 : Debug: (0) authorize { Fri Jul 27 11:45:04 2018 : Debug: (0) policy filter_username { Thanks, Agnel
On Jul 27, 2018, at 3:45 AM, Agnel Varghese <agn82kv@gmail.com> wrote:
Hi all,
Using FreeRADIUS Version 3.0.17. If non default ports are used (1712 below) getting Access-Reject with below error. Same works for 1812 port
Debugs failed case
Read http://wiki.freeradius.org/list-help We need "radiusd -X". Not "radiusd -XXxxxxxxx". And if the authorize section is empty, it's because you edited the configuration file and broke it. Don't do that. Please describe what you did. If you just edited the config and changed "1812" to "1712", then it *will not* cause this error. You did something else. What was it? And if you're going to ask questions, ask *good* questions. It's ever so much more useful than asking "I did stuff and it didn't work". Alan DeKok.
Didn't edit configuration file. Running it on different port : radiusd -i 192.168.122.1 -p 1712 -X Below is the output "radiusd -X" (8) Received Access-Request Id 6 from 192.168.122.100:16607 to 192.168.122.1:1745 length 232 (8) Cisco-AVPair = "client-mac-address=0050.9400.0005" (8) Acct-Session-Id = "04000003" (8) NAS-Port-Id = "0/0/4/1" (8) Cisco-NAS-Port = "0/0/4/1" (8) User-Name = "agnel" (8) Service-Type = Framed-User (8) CHAP-Password = 0x77c7575aa27bc6883290278e69588b5807 (8) CHAP-Challenge = 0xd7b99716f3620676b894dbf4d3203ae7 (8) X-Ascend-Connect-Progress = LCP-Opened (8) Cisco-AVPair = "connect-progress=LCP Open" (8) Framed-Protocol = PPP (8) NAS-Port-Type = PPPoEoVLAN (8) Event-Timestamp = "Aug 2 2018 16:43:27 IST" (8) NAS-Identifier = "vBNG" (8) NAS-IP-Address = 192.168.122.100 (8) NAS-IPv6-Address = :: (8) ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject (8) Failed to authenticate the user (8) Using Post-Auth-Type Reject (8) Post-Auth-Type sub-section not found. Ignoring. (8) Delaying response for 1.000000 seconds Waking up in 0.3 seconds. Waking up in 0.6 seconds. (8) Sending delayed response (8) Sent Access-Reject Id 6 from 192.168.122.1:1745 to 192.168.122.100:16607 length 20 Waking up in 3.9 seconds. (8) Cleaning up request packet ID 6 with timestamp +76 Ready to process requests On 27 July 2018 at 17:20, Alan DeKok <aland@deployingradius.com> wrote:
On Jul 27, 2018, at 3:45 AM, Agnel Varghese <agn82kv@gmail.com> wrote:
Hi all,
Using FreeRADIUS Version 3.0.17. If non default ports are used (1712 below) getting Access-Reject with
below
error. Same works for 1812 port
Debugs failed case
Read http://wiki.freeradius.org/list-help
We need "radiusd -X". Not "radiusd -XXxxxxxxx".
And if the authorize section is empty, it's because you edited the configuration file and broke it. Don't do that.
Please describe what you did. If you just edited the config and changed "1812" to "1712", then it *will not* cause this error.
You did something else. What was it?
And if you're going to ask questions, ask *good* questions. It's ever so much more useful than asking "I did stuff and it didn't work".
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
On Aug 2, 2018, at 7:21 AM, Agnel Varghese <agn82kv@gmail.com> wrote:
Didn't edit configuration file. Running it on different port : radiusd -i 192.168.122.1 -p 1712 -X
Below is the output "radiusd -X"
That doesn't happen in my copy of 3.0.17. What else have you done to the system? And post the FULL output of "radiusd -X" for crying out loud. That tells you which configuration files it's loading, including virtual servers. Alan DeKok.
participants (2)
-
Agnel Varghese -
Alan DeKok