On Mon, Apr 28, 2025 at 12:19 PM Alan DeKok <aland@deployingradius.com> wrote:
On Apr 28, 2025, at 11:58 AM, Timothy M Butterworth < timothy.m.butterworth@gmail.com> wrote:
I did not destroy the configuration. I am using the Debian default config plus the additions I made and posted above. Attached is the full config files.
As per the documentation: http://wiki.freeradius.org/list-help
We do not need to see the configuration files.
We DO need to see the debug output.
ALL OF THE DEBUG OUTPUT.
When the documentation says "post all of it and don't edit it", what that means is "post all of it and don't edit it".
Plus, the debug output you posted makes it VERY clear that you edited the file sites-available/default, and removed everything related to accounting.
Just read what you posted to the list. You will see:
* receiving Access-Request * processing the Access-Request through all kinds of configuration, modules, etc. * replying to the Access-Request
Then for accounting:
* receiving Accounting-Request * nothing happens * no reply is sent to the client.
Conclusion: you edited sites-available/default, and removed everything related to accounting. The debug output doesn't lie.
I did not delete anything from sites available. I just edited the IP address and port as I previously did not modify this file. # This second "listen" section is for listening on the accounting # port, too. # listen { ipaddr = 10.0.0.1 # ipv6addr = :: port = 1813 type = acct # interface = eth0 # clients = per_socket_clients limit { # The number of packets received can be rate limited via the # "max_pps" configuration item. When it is set, the server # tracks the total number of packets received in the previous # second. If the count is greater than "max_pps", then the # new packet is silently discarded. This helps the server # deal with overload situations. # # The packets/s counter is tracked in a sliding window. This # means that the pps calculation is done for the second # before the current packet was received. NOT for the current # wall-clock second, and NOT for the previous wall-clock second. # # Useful values are 0 (no limit), or 100 to 10000. # Values lower than 100 will likely cause the server to ignore # normal traffic. Few systems are capable of handling more than # 10K packets/s. # # It is most useful for accounting systems. Set it to 50% # more than the normal accounting load, and you can be sure that # the server will never get overloaded # # max_pps = 0 # Only for "proto = tcp". These are ignored for "udp" sockets. # # idle_timeout = 0 # lifetime = 0 # max_connections = 0 } }
Now stop arguing, and go fix the configuration. Use the default configuration. It works.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀