× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Reply

WAX610: how to set up syslog log level?

cr1cr1
Follower

WAX610: how to set up syslog log level?

I have 3 WAX610 configured in a single SSID using Netgear Insight. 

Whether I configure it on Insight or locally on the Web portal, I cannot choose a log level when enabling syslog to send the syslogs to an external server. The log level seems to be "debug" so the APs are very talkative... 

Is there a hidden way to change the syslog level?

 

If not, how to ask for an enhancement request?  The current implementation of syslog is not very useful if we just want to receive Warnings and Errors. 

Message 1 of 2

Accepted Solutions
schumaku
Guru

Re: WAX610: how to set up syslog log level?

The BSD syslog does always start from the point where the Logger does send all messages - regardless of the Facility or the Severity - to the "next hop" syslog server. The definition of what must be stored, displayed to the admin, or subsequently forwarded to the next syslog server is always done on the destination, never on the origin (the server, the appliance, the router, the switch, ....). 

 

Few sophisticated security appliances for example indeed provide options to control and direct the selected messages into a defined facility, into a defined path, to one or multiple syslog servers on a syslog collector - this isn't standard by far. 

 

sophisticated logger.PNG

 

It's a lot of effort, inherits a certain risk to miss really critical messages or details, to hide insight from security audit - that's why there is nothing like this on most switches, servers, routers, ...

View solution in original post

Message 2 of 2

All Replies
schumaku
Guru

Re: WAX610: how to set up syslog log level?

The BSD syslog does always start from the point where the Logger does send all messages - regardless of the Facility or the Severity - to the "next hop" syslog server. The definition of what must be stored, displayed to the admin, or subsequently forwarded to the next syslog server is always done on the destination, never on the origin (the server, the appliance, the router, the switch, ....). 

 

Few sophisticated security appliances for example indeed provide options to control and direct the selected messages into a defined facility, into a defined path, to one or multiple syslog servers on a syslog collector - this isn't standard by far. 

 

sophisticated logger.PNG

 

It's a lot of effort, inherits a certain risk to miss really critical messages or details, to hide insight from security audit - that's why there is nothing like this on most switches, servers, routers, ...

Message 2 of 2
Top Contributors
Discussion stats
  • 1 reply
  • 882 views
  • 2 kudos
  • 2 in conversation
Announcements