Skip to content

Implement RFC 3195 #31

@leodido

Description

@leodido

See https://datatracker.ietf.org/doc/html/rfc3195

BEEP frame example:

MSG 1 0 . 200 104
<34>1 2025-01-03T14:07:15.003Z mymachine.example.com su 12345 ID47 - 'su root' failed for user on /dev/pts/0
END

Line 1 is the BEEP header:
– MSG: Indicates the beginning of a message.
– 1: Message channel number.
– 0: Message sequence number.
– .: No immediate replies expected.
– 200: Payload size in bytes (depends on the message length).
– 104: Example length of the Syslog message.
Line 2 is the payload: The actual Syslog message in the format specified (e.g., RFC 3164 or RFC 5424).
Line 3 marks the end of the BEEP frame.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions