BUG: incorrect syslog message format

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

BUG: incorrect syslog message format

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
BUG: incorrect syslog message format
BUG: incorrect syslog message format
2021-03-21 13:36:03
Model: EAP245  
Hardware Version: V3
Firmware Version: 5.0.1 Build 20201224 Rel. 59228(5553)

Syslog messages are formatted incorrectly.  They include line-ending characters, but should not.

 

With Management -> System Log -> Log Settings set to enable, log messages are sent to the remote syslog port (514).  "More client detail" is also set.

 

Wireshark confirms that the log messages are terminated with <cr><lf> (015,012).  This is incorrect.  RFC3164  states that the messages are delimited by their length, not by an embedded character.

 

The extra characters are stored into log files by the syslog daemons, which confuses some parsers and can make the files hard for humans to read.

Please stop including them.

 

You can use Wireshark to show that other log sources do not use <cr><lf> terminators.

 

Note that "Enable auto mail" is not set.  In an e-mail message, the <cr><lf> delimiters are required.

 

Thanks

 

  1      
  1      
#1
Options

Information

Helpful: 1

Views: 312

Replies: 0