- Products
- Learn
- Local User Groups
- Partners
- More
Quantum Spark Management Unleashed!
Introducing Check Point Quantum Spark 2500:
Smarter Security, Faster Connectivity, and Simpler MSP Management!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
On a Cisco router I could specify syslog is sent from one of its interfaces such as loopback. On a checkpoint firewall could I source syslog from an interface other than what is configured as management that is established with SIC? If not, how could I source syslog from a different interface? thank you
Hi Guys,
It'll certainly makes out lives bit better in case Check Point introduce a command to set the source interface for syslog
Many thanks,
The IP used is determined by the routing table in the OS, using the egress interface IP as the source IP.
I suppose you could create a NAT rule to source the relevant traffic from the desired IP.
What's the problem you're trying to solve here?
Nat Don't work. Any Idea ?
Add a host route for your syslog server out the interface you want to source the traffic from off the gateway.
I have the same issue where the module is sending logs to the management server using it's external IP as a source for the packets but the SIC between the mgmt server and the FW module is build based on the management IP which is a private IP.
The return traffic does not routed over our WAN network but over the internet and this is incorrect.
is there a way to set the source interface of the logs to be the Mgmt0 interface?
Hi
In my case, solved the issue, creating a dummy object
Hello and thanks for your reply.
I don't understand your solution, can you please elaborate?
Hi,
You have 2 options:
1. Configure Syslog Server behind the interface you want to be the source of syslog messages.
2. You can configure Syslog server behind any interface and you can do Static NAT on a range of the desired interface, it should work.
Hi Ilya,
I have configured static NAT so the public IP will be replaced with one of the internal IPs configured on the cluster but still, the packets leave the firewall with the original source IP which is the public.
The external interface IP is 192.192.192.254 and the internal interface IP is 10.1.1.254
I have configured a NAT rule that says" original source - 192.192.192.254" to target 192.168.1.1, replace with the source of 10.1.1.254 and the target remains original.
I tried static and hide NAT and the same result - the source is unchanged.
Any thoughts?
as far as i remember there was no issue but miss configuration.
@motiami - can you share what was missing as i don't remember 100%.
Hi Guys,
It'll certainly makes out lives bit better in case Check Point introduce a command to set the source interface for syslog
Many thanks,
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
10 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 |
Wed 03 Sep 2025 @ 11:00 AM (SGT)
Deep Dive APAC: Troubleshooting 101 for Quantum Security GatewaysThu 04 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: External Risk Management for DummiesWed 10 Sep 2025 @ 11:00 AM (CEST)
Effortless Web Application & API Security with AI-Powered WAF, an intro to CloudGuard WAFWed 10 Sep 2025 @ 11:00 AM (EDT)
Quantum Spark Management Unleashed: Hands-On TechTalk for MSPs Managing SMB NetworksWed 03 Sep 2025 @ 11:00 AM (SGT)
Deep Dive APAC: Troubleshooting 101 for Quantum Security GatewaysThu 04 Sep 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: External Risk Management for DummiesWed 10 Sep 2025 @ 11:00 AM (EDT)
Quantum Spark Management Unleashed: Hands-On TechTalk for MSPs Managing SMB NetworksAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY