Hi Thanks for the suggestion. That would block the health-check probe, which makes a full tcp connect. For now, my solution is to switch to using the syslog log facility, which is rsyslog in my case, then use a filter to drop the messages :) Regards -Richard ________________________________ From: Freeradius-Users <freeradius-users-bounces+richard.green=unsw.edu.au@lists.freeradius.org> on behalf of Alan DeKok <aland@deployingradius.com> Sent: Wednesday, 29 January 2020 11:38 PM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Disable logging for one virtual server On Jan 28, 2020, at 11:31 PM, Richard Green <richard.green@unsw.edu.au> wrote:
Is it possible to disable logging for one virtual server, with FreeRADIUS 3?
I have a network load balancer in front of FreeRADIUS 3, for the purposes of multiple availability zone fail-overs in AWS. The health checks (which are only valid for TCP btw) are resulting in many logged errors:
Wed Jan 29 04:28:24 2020 : Error: Ignoring request to auth proto tcp address * port 1812 bound to server health-check-tcp from unknown client 10.118.241.27 port 43332 proto tcp
Use a firewall rule to block those connections at the OS layer. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html