Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 437 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VPN to VPN Connection

Max Roberts

Hi,

I have established a VPN from a branch office to head office and from head office to AWS. I then want to be able to access AWS from the branch office but I can't seem to get this to work. I cannot ping the server at AWS from the branch office. Can anyone offer any suggestions on what I am missing please?

Thanks,

Max



This thread was automatically locked due to age.
Parents
  • 0

    Basically you need to add the AWS networks to the tunnel between Headoffice and branch and also add the branch to the HQ/AWS Tunnel

    lets say

    AWS: 10.1.1.0/24

    HQ: 10.1.2.0/24

    BR: 10.1.3.0/24

     

    then the tunnels would look:

     

    AWS/HQ

    10.1.1.0/24 <> 10.1.2.0/24

    10.1.1.0/24 <> 10.1.3.0/24 (Branch)

     

    Branch/HQ

    10.1.3.0/24 <> 10.1.2.0/24

    10.1.3.0/24 <> 10.1.1.0/24 (AWS)

     

    The Firewall rule on the HQ should allow traffic from VPN to VPN matching the aws/branch subnets.

     

Reply
  • 0

    Basically you need to add the AWS networks to the tunnel between Headoffice and branch and also add the branch to the HQ/AWS Tunnel

    lets say

    AWS: 10.1.1.0/24

    HQ: 10.1.2.0/24

    BR: 10.1.3.0/24

     

    then the tunnels would look:

     

    AWS/HQ

    10.1.1.0/24 <> 10.1.2.0/24

    10.1.1.0/24 <> 10.1.3.0/24 (Branch)

     

    Branch/HQ

    10.1.3.0/24 <> 10.1.2.0/24

    10.1.3.0/24 <> 10.1.1.0/24 (AWS)

     

    The Firewall rule on the HQ should allow traffic from VPN to VPN matching the aws/branch subnets.

     

Children
No Data