Navigation

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

    One Nic install for VPN

    IPsec
    2
    5
    896
    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.
    • P
      pfk last edited by

      Hi all,

      I've got a setup (simplified) as follows…
      Interweb <---->Router<------>Pfsense
                                          <------>other PC

      I've got an IPSec VPN up and connecting, which is great. Despite a lot of googling and trial and error, I can't solve the routing so that the VPN client can connect to "Other PC".

      -outbound NAT on auto
      -Firewall > rules > IPSec - rule created from * to * passes

      In a way, I think I'm looking to bind IpSec back to the Wan - as this is a single nic installation. Has anyone got any ideas???

      1 Reply Last reply Reply Quote 0
      • P
        peterclark4 last edited by

        As along as the "other PC" has either it's default gateway or a rout set to the pfSense you should be good to go.

        Also might be worth checking your firewall rules on the IPsec interface on the pfSense.

        1 Reply Last reply Reply Quote 0
        • P
          pfk last edited by

          PFSense's only got one nic though, I don't think you can use a wan-designated port as a gateway?

          1 Reply Last reply Reply Quote 0
          • P
            peterclark4 last edited by

            I've done it with OpenVPN, the pfSense had one NIC and initiated the tunnel. Any client that needed to traverse the tunnel either had it's default gateway set or had a route added to it. I don't see it working any differently with IPsec.

            1 Reply Last reply Reply Quote 0
            • P
              pfk last edited by

              As per diagram above, I'm connecting from a remote client (192.168.1.0/24) to pfsense, which is on 192.168.0.0/24.

              The router pfsense is behind is 192.168.0.2. Also, ipsec client will be 192.168.99.0/24.

              Added a rule on that router (192.168.0.2) for anything 192.168.99.0/24 directs towards pfsense (192.168.0.110).

              Still, the VPN client(192.168.1.137 or virtually 192.168.99.1) cannot access anything on the other side of the tunnel, nor can a PC on the 192.168.0.0/24 network ping the client. Only concerned about the former though.

              Looks like it'll be a long weekend…

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy