- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- External Interface - Internal Only Firewall
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
External Interface - Internal Only Firewall
I am in the process of setting up some firewalls to segment different parts of my network. I'm curious how some of you configure the external interface in this case. These firewalls will be internal only, no direct connection to an ISP, and no public IPs. Just use a private IP space then NAT it at the edge gateway? Then define as external in topology for address spoofing? Seems like it should be easier than this. Let me know how you solve this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You describe the solution yourself?
That's exactly how I'd do it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is required for antispoofing feature in your case and cose sometimes handy in other cases, like for example hide all traffic behind external gateway IP in with one checkbox.
Internal interface would mean that you have only specific networks behind it:
- Network defined by the interface IP and Net Mask - There is only one network that connects to this internal interface.
- Specific - There is more than one network that connects to this internal interface, select a group.
External interface - all other networks, not defined as internal ones or Sync.
Of course you can disable antispoofing at all and not think about it, which I would highly not recommend.
In my opinion, this is how to choose an external interface in this case - leading in the direction of internet connection (default route), all protected networks (for example networks with some specific servers) which you can define are behind other (internal) interfaces, in that direction there are many network, which cannot be easily defined and they are not part of protected scope of this gateway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
External doesn't mean the interface that directly connects to the ISP router, it describes the network segment your traffic passes to reach (even indirectly) public or other untrusted networks. Often this is the interface that connects to the default gateway of your firewall.
Anti-Spoofing is a sanity-check on what interfaces packets are coming from and what interfaces they should be going to.
Some Check Point features need to know what interfaces are Internet-facing (External) in order to activate protections. Example for 'Interface leads to DMZ'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I want to ask a similar question. I am setting up another internal only firewall. In this case, I have limited connections. Would it be possible to combine management, internal, and external interfaces into one interface? They would all lead to the same place anyway. All would go to the next hop router, then somewhere inside or outside. Can someone help me run through if this will work and the possible pitfalls like potentially anti-spoofing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I mean, yeah, you can set it up that way (just set the interface as External and possibly disable Anti-Spoofing).
