Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    VPN IPSEC traffic not routing to subnets/vlans outside of the firewall's network

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 149 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      iamcx
      last edited by

      I have an IPSEC VPN setup between our data center and our AWS cloud network. The VPN connection is up and I can communicate from my AWS cloud computers to any devices on the subnet of the firewall (192.168.2.0/24). The firewall has a default gateway of 192.168.2.1 that routes traffic to/from our other networks (192.168.3.0, 192.168.4.0, etc.). Traffic from the VPN cannot talk to anything outside of the 192.168.2.0 network. I was assuming the VPN IPSEC traffic would follow the default gateway to get out, but it doesn't. I'm assuming I need to configure some other routes, but not sure how to get this done. Any help would be appreciated.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.