Disable logging for one virtual server
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 Thanks Richard ______ Richard Green IT Solution Design & Delivery | UNSW Sydney | NSW 2052
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:
No, unfortunately not. It's something we have planned for v4, but it's not even implemented there yet. -Arran
Hello, My users logged out after a few minutes of inactivity while I set Idle Timeout attributes to 86400 seconds. This is a FreeRadius or NAS or user device configuration problem? Thanks, JMLZ
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.
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
On Jan 31, 2020, at 5:56 AM, Matthew Newton <mcn@freeradius.org> wrote:
On Fri, 2020-01-31 at 02:25 +0000, Richard Green wrote:
Thanks for the suggestion. That would block the health-check probe, which makes a full tcp connect.
If it's supposed to be connecting, maybe actually add a client entry for it?
Or is it just a generic LB probe? -Arran
participants (5)
-
Alan DeKok -
Arran Cudbard-Bell -
Matthew Newton -
Philemon Jaomalaza -
Richard Green