Site to Site VPN 1 GW multiple peers Same VPN network

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Site to Site VPN 1 GW multiple peers Same VPN network

L0 Member

Hi,

 

Looking for your advise and best practise for setting up a site to site vpn with one GW and multiple peers. VPN IP addresses are from the same subnet. Services behind the GW1 should be accessible be each pee and vice versa. However, each peer should not be communicating to each other.

 

Is this possible? if yes, is there a guidelines on how to achive this in secure method?

 

GW1: 1.1.1.1/24

Peer1: 1.1.1.2/24

Peer2: 1.1.1.3/24

Peer3: 1.1.1.4/24

 

Thank you.

1 accepted solution

Accepted Solutions

L4 Transporter

Hi there,

If understand your topology you should have at the start a 'trust' zone which holds the services your remote hosts want to access.

To prevent the hosts behind the remote VPN peers from communicating, place each VPN tunnel in its own security zone. Create explicit security polices permitting traffic between the 'trust' and VPN individual security zones. The default inter-zone policy of 'deny' will ensure the VPN hosts cannot communicate.

How is routing between the hub firewall and VPN peers being handled? Is the hub firewall advertising a default route? Do the VPN peers have a static default route with a next-hop of the hub firewall?

If you are dynamically advertising routes between the hub and VPN peers, then so long as you do not re-advertise received VPN peer subnets there will be no way for this inter-VPN traffic to be routed from the remote sites. BGP would be the best way to control this.

 

cheers,

Seb.

View solution in original post

2 REPLIES 2

L4 Transporter

Hi there,

If understand your topology you should have at the start a 'trust' zone which holds the services your remote hosts want to access.

To prevent the hosts behind the remote VPN peers from communicating, place each VPN tunnel in its own security zone. Create explicit security polices permitting traffic between the 'trust' and VPN individual security zones. The default inter-zone policy of 'deny' will ensure the VPN hosts cannot communicate.

How is routing between the hub firewall and VPN peers being handled? Is the hub firewall advertising a default route? Do the VPN peers have a static default route with a next-hop of the hub firewall?

If you are dynamically advertising routes between the hub and VPN peers, then so long as you do not re-advertise received VPN peer subnets there will be no way for this inter-VPN traffic to be routed from the remote sites. BGP would be the best way to control this.

 

cheers,

Seb.

Thank you. I was afraid that peers will be on same zone. Since each tunnel will be on different zone, then this will enable more control.

 

In terms of routing, it will be simple static route.

 

Thank you again.

  • 1 accepted solution
  • 1500 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!