- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
We plan to use authentication on the FW-B for Internet access and Mobile Access connections
Description of the problem
FW-B uses an external IP (2.2.2.2) address for requests (Identity Avareaness) to DC-1. DC-1 sends a response in the wrong direction, according to routing
Is it possible to configure the FW-B so that it sends requests (Identity Avareaness) using its local IP address as the source interface?
You could do a hide NAT on the traffic from FW-B when it passes through FW-A to go to the DC-1
What do you see if you issue ip route get and then IP of the DC1? just run ip r g 192.168.0.1 on expert mode of firewall B.
192.168.0.1 via 2.2.2.1 dev eth1 src 2.2.2.2
Well, if you want it to take different path, just change the route to reflect different interface. It seems at this point its using 2.2.2.2 interface IP with gateway of 2.2.2.1.
I don’t understand, you can learn more?
What Im saying is, it does not sound logical to use external interface to access something internal from the firewall itself. Just change it to reflect internal interface of the firewall, as long as topology is right.
Yes, it is not logical, I agree. How to change it to reflect internal interface of the firewall?
From web UI or clish. Just change it via web UI in the browser, it takes 15 seconds literally.
You could do a hide NAT on the traffic from FW-B when it passes through FW-A to go to the DC-1
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY