linguini1 opened a new pull request, #3090:
URL: https://github.com/apache/nuttx-apps/pull/3090

   ## Summary
   
   Initial implementation of syslogd including version information, simple 
usage help and UDP transmission. The current implementation transmits RFC 5424 
formatted syslog entries over UDP for consumption by a syslog collector. Only 
some options from the manpage are implemented since NuttX doesn't currently 
have the ability for some of the more complex features (-l, etc.).
   
   ## Impact
   
   Users can use this application alongside the new RFC 5424 support (see other 
PR here) to send syslog entries over the network in a format that is understood 
by various logging servers and network utilities (i.e. WireShark, rsyslog, etc).
   
   ## Testing
   
   Testing was performed by completing a local build on the `sim` and 
`raspberrpi-pico-w` platforms with all new `syslogd` options enabled. Builds 
succeeded.
   
   On the simulator (`tcpblaster` config used as a basis), `syslogd` was used 
with the host routing mode to verify that logs were being sent over UDP to the 
configured server address and port. This was confirmed with WireShark, which 
also successfully parsed the messages using the syslog protocol.
   
   On the Pico W, the `telnetd` configuration was used as a basis. `syslogd` 
was run using my host computer as the server address and I verified that all 
logs were continuously received (as they occurred) by watching traffic using 
WireShark.
   
   
![image](https://github.com/user-attachments/assets/0be9e034-6cd2-4965-bfc4-ec6589d11abd)
   
   Debug output was confirmed to work by running with the `-d` flag and 
verifying that all logs being transmitted were also being logged to `stdout`, 
along with information about socket setup.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to