- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Announcing Quantum R82.10!
Learn MoreOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hey guys,
We are having a site-to-site VPN issue. The remote end (Cisco Router) uses the same phase 2 selectors for multiple peers. On our side, the security gateway is accepting all Phase 2 selectors, regardless of what is configured in encryption domain.
Is it possible to have the security gateway reject phase 2 selectors that are not configured?
We are running R81 take 17.
Thanks in advance,
RK
What precisely has been configured versus what has been proposed?
Hi PhoneBoy,
The peer is a Cisco router and it is using a single configuration for two of our gateways, and it has two networks configured for their phase two remote (10.164.128.0 and 10.164.0.0). Their local network is 172.16.0.0.
We have two gateways, one is configured for local 10.164.128.0 and the other for 10.164.0.0. We are using separate VPN Communities. The issue is that both our gateways accept both incoming phase 2, although it is not specified in it's security domain.
I am worried this will affect the remote end's routing and wanted to deny the non-specified phase 2.
Maybe I am missing something, but in each community you are configuring member gateways, one of yours and one of theirs (where theirs is the same in both communities).
If you are on R80.40, you should be able to define VPN domain per VPN community on your side (in gateway's networking properties).
You then should be sending only relevant network to the peer for each connection.
Hi Vladimir,
That is correct for outgoing connections. The security gateway only sends the domains we have. The issue is from what I have seem, incoming phase 2 is always accepted regardless of network, although encryption has to match.
This would not be a problem if the other side was using separate definitions on their router.
Have you try defining two Interoperable devices with the same IP for your peer and specifying a single network in the topology of each?
I don’t think you can actually do that and have it work.
I think a TAC case may be in order here.
Personally, I never heard of any vendor be able to do so.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 21 | |
| 20 | |
| 16 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY