I'm currently developing an application to receive reliable syslogs from the Fortigate (testing with a 60D currently on 6.0 GA), unfortunately I'm having issues with both reliable and legacy-reliable modes.
The reliable mode unfortunately unreliably sends it's NUL terminators. After the TCP session is established I receive them for the first 3-6 logs (in this lucky case, about 13 logs) and then it never includes them again after that unless I re-establish the TCP session. It seems to forget to include those, and without them it's difficult to parse the incoming logs as there are no delimiters or anything. I've attached a sample of my program output that clearly outputs when the NUL terminator was found.
The legacy-reliable mode all I get is the following (BEEP):
RPY 0 0 . 0 52 Content-type: application/beep+xml
<greeting /> END
Unfortunately I haven't been able to figure out how to reply to this to get the actual logs and move forward with this method (which would at least be a workaround for the missing NULs in the reliable mode), any help on this front would be appreciated!
User | Count |
---|---|
2534 | |
1351 | |
795 | |
641 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.