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

    [SOLVED] Traffic via IPsec tunnel not routing to OPT1 subnet on far end

    Routing and Multi WAN
    2
    3
    956
    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.
    • H
      HaburGate
      last edited by

      We have two pair of pFsense 2.1.5 boxes on either end of an IPSec tunnel connecting our main site to a branch office. Both ends are in an HA+CARP configuration, and traffic between the two LAN subnets is flowing as expected.

      Subnets:
      Main site:          172.16.1.0/24
      LAN Virtual IP:  172.16.1.2
      OPT1 Virtual IP: 192.168.1.2/24

      Branch site:      172.16.5.0/24
      LAN Virtual IP:  172.16.5.1

      problem: we are unable to reach hosts in the 192.168.1.0/24 subnet from the branch office subnet (172.16.5.0/24). When I perform a traceroute from a host at the branch office, the traffic routes out the default gateway onto the public Internet, instead of through the tunnel as desired.

      How can I route traffic destined to 192.168.1.0/24 through the tunnel instead of out the default gateway?

      PGP Key: 0x82A211A2
      Server:    pool.sks-keyservers.net

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Create another phase2 entry at both ends for the 172.16.5.0/24<->192.168.1.0/24 connectivity.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • H
          HaburGate
          last edited by

          @Derelict:

          Create another phase2 entry at both ends for the 172.16.5.0/24<->192.168.1.0/24 connectivity.

          Perfect, that fixed it. Thank-you!

          PGP Key: 0x82A211A2
          Server:    pool.sks-keyservers.net

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