Navigation

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

    NAT the clients and then route them through VPN?

    OpenVPN
    4
    5
    2207
    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.
    • G
      grav5 last edited by

      Hi folks,

      i'm fiddling around for a while trying to get something like that working:

      I want to to route everything that comes from the clients and is destinated to go "to the internet" to be routed through the VPN tunnel. That VPN tunnel is already working.

      The server (the debian box n the image) should not see the clients and which client is doing what, the server should only see one IP adress, the one of the pfSense box. Therefore pfSense has to NAT everything before sending it through the tunnel, hasn't it?

      The reason behind is, that i do not want to do a classic site-to-site scenario, it often happens that roadwarrior users having access to the VPNserver temporary want to connect a whole subnet.

      What shall I do now? Or do you think there is a better way to do this?

      1 Reply Last reply Reply Quote 0
      • GruensFroeschli
        GruensFroeschli last edited by

        It's not possible to NAT into the VPN tunnel
        (at least not through the GUI)
        –> not supported.

        1 Reply Last reply Reply Quote 0
        • G
          grav5 last edited by

          Bad to hear…

          Thanks for the fast responding anyway!

          1 Reply Last reply Reply Quote 0
          • Cry Havok
            Cry Havok last edited by

            ISTR that NAT with OpenVPN is coming in one of the future releases.  I don't remember which, but a search of this forum should find the details.

            It is possible to manually add the required NAT configuration - again, search the forum as I don't remember the details.

            1 Reply Last reply Reply Quote 0
            • V
              Valhalla1 last edited by

              I do stuff similar to this, but instead of having 1 VPN tunnel between the remote box and the pfsense box, instead each client on the LAN has to run openvpn client and connect to the remote box.   then all their traffic is routed over the tunnel.  this takes pfsense out of the openvpn equation

              disadvantage - instead of one tunnel, there are many. more to manage,  scalability problems I imagine..

              but end goal is the same,  clients on LAN all traffic goes through tunnel

              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