- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi Guys,
we have a Cluster running on R81.20 with JHF T65.
We want to separate WebEX from other traffic.
So I used the Updatable Object for allowing the Traffic to "WebEX Services".
In NAT-Rules I created a Source NAT:
internal Net --> WebEX Services NAT-IP 10.1.1.1 (hide) ---> original
Rule and NAT is working fine, BUT ....
I have configured PBR to work for Source IP.
BPR-Rule: If Source IP is 10.1.1.1 ---> Route Destination x.x.x.14
Default Route is x.x.x.254 (Loadbalancer)
So I expected, that the traffic, which has been source natted to 10.1.1.1 will use the
PBR Route for x.x.x.14 and NOT my default Route to the loadbalancer.
Unfortunately it still uses the default route!
Is the order for PBR..... first look up for PBR and than make Source NAT ???
And why not use the PBR route based on the real ip instead of NAT pool range?
Because, that will match all traffic from the real IPs.
I do source NAT only for Destination WebEX Services.
So original Source with other Destination musst use default route.
Destination WebEX Services are Source natted and should use PBR Route
https://support.checkpoint.com/results/sk/sk163320
Yes, i have seen it.
I will try another way to separate the traffic:
The purpose of extending the basic PBR rule criteria to include Firewall rule is to enable users to match on configured Firewall rules and forward traffic accordingly. This extension of PBR functionality forwards the traffic based on application, service, users, time, location, and many more, as supported by FW rules.
Currently, this feature is supported to direct Office365 traffic to Microsoft Cloud and is being tested with other updatable SaaS and cloud service objects.
This feature is currently hidden. To enable it, run these commands on the Security Gateway in the Expert mode and reboot:
HostName:0# dbset process:rtgpbrd:runlevel 4
HostName:0# dbset process:rtgpbrd:path /bin
HostName:0# dbset process:rtgpbrd t
HostName:0# dbset :save
HostName:0# reboot
I will test this scenario, if I get a maintenance window from the customer.
You mean then this SK correct? https://support.checkpoint.com/results/sk/sk167135
Yes, have found sk167135.
Never tried this "hidden" feature. Will give it a try and will post my results.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 21 | |
| 20 | |
| 19 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY