Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
TomShanti
Collaborator
Jump to solution

Exclude IP addresses (non local subnets) from hub mode

Hi,

 

is it possible to also exclude specific IP adresses/subnets for a VPN client running in hub mode (route all traffic to gateway) ?

I know there is a solution for excluding local LANs (https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...but I need to exclude specific IPs and I must not disable hub mode.

 

Thanks and regards

Thomas

 

0 Kudos
1 Solution

Accepted Solutions
LukeOxley
Participant

If you'd like configure the Remote Access routing to essentially route all traffic to the gateway, EXCEPT a certain list of hosts/subnets, then you need to do the following:

  1. Ensure "Route all traffic to gateway" is set to NO in Global Properties > Remote Access > SecureClient Mobile & Endpoint Connect. 
  2. Ensure Hub Mode is set to ALLOW on the gateway object under VPN Clients > Remote Access.
  3. Create a new network group named 'All_Internet_Group', and add the default 'All_Internet' object to it.
  4. Create a new network group named 'ED-RemoteAccess_Exclusions'. Add all of the hosts/networks you'd like to be excluded from hub mode (I.E, routed locally on the client's end rather than across the VPN to the gateway).
  5. Create a new "group with exclusions" called 'ED-RemoteAccess', reference the 'All_Internet_Group' we created as the main group and the 'ED-RemoteAccess_Exclusions' we created as the exclusion group.
  6. Set the 'ED-RemoteAccess' group as the Remote Access encryption domain on the gateway topology.
  7. Ensure security rules and NAT rules are setup to support this configuration (I.E, security rules allow the OfficeMode subnet access to the Internet, and the OfficeMode subnet is NAT'd behind the gateway).
  8. Install policy, then disconnect/reconnect any existing connected clients so that they get the new routing table.

To put this into a scenario, lets say you want all traffic to be routed to the gateway (like it is in hub mode), apart from 167.20.10.0/24 (some random network I thought of, insert yours here) - you want the clients to route this out of their local connection rather than via the security gateway. Following the scenario above and adding the 167.20.10.0/24 network to the 'ED-RemoteAccess_Exclusions' group will achieve this.

Hope that helps!

Luke

View solution in original post

0 Kudos
5 Replies
G_W_Albrecht
Legend
Legend

Why not user Access Roles to differentiate between local and RA VPN clients and create a ruleset that denies access to these IP addresses for RA VPN clients only ?

CCSE CCTE CCSM SMB Specialist
0 Kudos
TomShanti
Collaborator

Hi Günther,

 

can you elaborate what you mean by  local and RA VPN clients ?

Target scenario is this

 

RA VPN client ---- forced tunnel ---------------------------Corp FW -- company LAN

          |------------- Webserver 80.80.80.80 (Corp DMZ)--------|

 

Regards Thomas

 

0 Kudos
G_W_Albrecht
Legend
Legend

You have  local clients at your site that connect to the internet thru the GW, and you have RA VPN clients using Hub Mode / Route all traffic to gateway, So you could use one access rule  for local clients and another for RA VPN clients with excluded destinations...

CCSE CCTE CCSM SMB Specialist
0 Kudos
TomShanti
Collaborator

"and another for RA VPN clients with excluded destinations..."

 

This configuration is what I am looking for. How do you exclude destinations in Hub mode ?


Regards Thomas

0 Kudos
LukeOxley
Participant

If you'd like configure the Remote Access routing to essentially route all traffic to the gateway, EXCEPT a certain list of hosts/subnets, then you need to do the following:

  1. Ensure "Route all traffic to gateway" is set to NO in Global Properties > Remote Access > SecureClient Mobile & Endpoint Connect. 
  2. Ensure Hub Mode is set to ALLOW on the gateway object under VPN Clients > Remote Access.
  3. Create a new network group named 'All_Internet_Group', and add the default 'All_Internet' object to it.
  4. Create a new network group named 'ED-RemoteAccess_Exclusions'. Add all of the hosts/networks you'd like to be excluded from hub mode (I.E, routed locally on the client's end rather than across the VPN to the gateway).
  5. Create a new "group with exclusions" called 'ED-RemoteAccess', reference the 'All_Internet_Group' we created as the main group and the 'ED-RemoteAccess_Exclusions' we created as the exclusion group.
  6. Set the 'ED-RemoteAccess' group as the Remote Access encryption domain on the gateway topology.
  7. Ensure security rules and NAT rules are setup to support this configuration (I.E, security rules allow the OfficeMode subnet access to the Internet, and the OfficeMode subnet is NAT'd behind the gateway).
  8. Install policy, then disconnect/reconnect any existing connected clients so that they get the new routing table.

To put this into a scenario, lets say you want all traffic to be routed to the gateway (like it is in hub mode), apart from 167.20.10.0/24 (some random network I thought of, insert yours here) - you want the clients to route this out of their local connection rather than via the security gateway. Following the scenario above and adding the 167.20.10.0/24 network to the 'ED-RemoteAccess_Exclusions' group will achieve this.

Hope that helps!

Luke

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events