Dubravko Penezić
08/12/2025, 7:06 PMTCP_Framing="octet-counted"
• RFC 6587 compliant — each message is prefixed with its length in decimal, followed by a space.
TCP_Framing="traditional"
• Messages are terminated by the NUL (\0) character.
• Simpler, but not RFC compliant — works if the receiver expects null-delimited messages.
TCP_Framing="non-transparent"
• Also per RFC 6587 — messages end with a newline (\n) character.
• Called “non-transparent” because if the message itself contains newlines, it breaks parsing.
• Only safe if you know messages won’t contain embedded \n characters.
At a moment, I am able only to receive traditional syslog messages .Pat
08/13/2025, 6:46 AMPat
08/13/2025, 6:46 AMDubravko Penezić
08/13/2025, 7:05 AMDubravko Penezić
08/13/2025, 7:18 AMDubravko Penezić
08/13/2025, 7:59 AMDubravko Penezić
08/13/2025, 8:00 AMDubravko Penezić
08/13/2025, 8:57 AM/* Always parse while some remaining bytes exists */
while (eof < end) {
/* Lookup the ending byte */
eof = p = conn->buf_data + conn->buf_parsed;
while (*eof != '\n' && *eof != '\0' && eof < end) {
eof++;
}
/* Incomplete message */
if (eof == end || (*eof != '\n' && *eof != '\0')) {
break;
}Dubravko Penezić
08/13/2025, 8:59 AMDubravko Penezić
08/13/2025, 10:09 AMDubravko Penezić
08/13/2025, 10:26 AMDubravko Penezić
08/13/2025, 10:28 AMDubravko Penezić
08/13/2025, 10:37 AMtcp_framing and tcp_nt_character