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

    Routing between VPN Client and VPN tunnel

    IPsec
    2
    7
    725
    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
      interessierter
      last edited by

      Hello all!

      I use pfsense with a home network of 192.168.0.0/16
      I offer VPN access, the used IP range is 10.98.0.0/16
      I have a IPSEC tunnel to Microsoft Azure, in Azure I use 10.0.0.0/16

      When I m at home in 192net, I can reach the azure servers
      When I m connected with VPN, I can reach my home IPs but not the azure Servers in the 10network.

      Some research on google guide me to create a new P2 in IPSEC.
      What I have to specify exactly`?

      thanks

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

        Azure needs to know to send traffic for 10.98.0.0/16 over the tunnel so you probably need a route over there.

        pfSense needs another Phase 2 entry for:

        Local network: 10.98.0.0/16
        Remote network: 10.0.0.0/16

        on the Azure tunnel.

        And proper firewall rules, security groups, etc for the traffic.

        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
        • I
          interessierter
          last edited by

          Hi!

          That is already in place.
          What firewall rule do I need exactly? On the IPSEC tab? Because I don t see any DENY or blocks in the logfiles

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

            You'll have to post what you have.

            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)

            I 1 Reply Last reply Reply Quote 0
            • I
              interessierter @Derelict
              last edited by

              pfsense.JPG

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

                More than that. All settings pertaining to this including your Azure settings.

                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
                • I
                  interessierter
                  last edited by

                  pfs2.JPG azurepfs.png

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