- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Hello,
Can you please provide responses to the following syslog configuration related questions.
1. Is is possible to send syslog on a port other than the default UDP 514, possible by modifying configuration files /etc/syslog.conf or /etc/sysconfig/syslog? I have set up a remote syslog target which is listening on a different port.
2. Is it required to modify the fwsyslog_enable kernel parameter on each gateway to 1, to enable syslog. This is not specified in the r81.20 admin guide, however is it stated as a requirement in the r81.20 logging and monitoring admin guide.
Regards,
Simon
Got an answer from TAC. There is no way to change the default so I've had to NAT the traffic.
The answer to both questions is here: https://support.checkpoint.com/results/sk/sk87560
Looks like you can use a different port and you shouldn't use fwsyslog_enable unless TAC suggests it.
This is not what I'm after.
That SK outlines how to 'How to configure Security Gateway on Gaia OS to send FireWall logs to an external Syslog server'.
I'm already sending firewall logs from all gateways to remote log servers, and from there using log exporter to send in to Splunk.
I'm referring specifically to configuring syslog on individual gateways to send Gaia system messages and audit events only to a remote syslog server. And we want to send this to the remote server on a custom port.
It's interesting that SK also states at the bottom of the document that the fwsyslog_enable parameters is "is intended for optimization of logging performance in environments that require high log rates.Do not enable this kernel parameter unless explicitly instructed by Check Point Support.", as there is no mention of that in the Logging and Monitoring R80.20 Administration Guide, > Logging > Working with Syslog Servers section.
Got an answer from TAC. There is no way to change the default so I've had to NAT the traffic.
Ah yes, that's a beast of a different color.
You might be able to make the relevant change in /etc/rsyslog.conf and make the file immutable so the OS doesn't overwrite it.
However, that falls into "unsupported" category.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION