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

    Network connectivity issue from OpenVPN client

    Scheduled Pinned Locked Moved Firewalling
    15 Posts 3 Posters 592 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.
    • C
      CoffeeOrTea @viragomann
      last edited by CoffeeOrTea

      @viragomann

      Upstream, meaning the WAN access?

      I did create that, yes. I don't have a screenshot handy, but essentially the rule is:

      Outbound Rule
      Interface: WAN
      Source: 192.168.50.0/24 (Tunnel subnet)
      Destination: *
      Translation Address: WAN Address

      However, it wasn't just WAN access that was failing, it was everything. I couldn't ping/communicate with pfsense gateway/dns on the same tunnel network or servers on other subnets despite having wide-open allow rules.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @CoffeeOrTea
        last edited by

        @CoffeeOrTea

        My :

        6b48db3b-a856-45ca-831d-f25897b8e58c-image.png

        never had to create anything.
        192.168.3.0/24 is my OpenVPN tunnel IP network.
        I don't recall adding what so ever manually.

        Btw : 192.168.1.0/24, 192.168.2.0/24 and 192.168.100.0/24 are all my LANs

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        C 1 Reply Last reply Reply Quote 0
        • C
          CoffeeOrTea @Gertjan
          last edited by

          @Gertjan said in Network connectivity issue from OpenVPN client:

          never had to create anything.

          I've got my outbound NAT set to 'manual rule generation' rather than automatic. Odd though because I have the manual equivalent of the rule that you have. Still, that should only be for WAN access over the VPN whereas I can't even communicate with the gateway/other subnets [with 'force all traffic through tunnel' enabled].

          That said, everything is working flawlessly right now due to disabling the 'force all traffic through tunnel' option and manually specifying accessible subnets. I just don't understand why the 'force all traffic through tunnel' breaks everything.

          GertjanG V 2 Replies Last reply Reply Quote 0
          • GertjanG
            Gertjan @CoffeeOrTea
            last edited by

            @CoffeeOrTea

            00a92759-f084-4be6-8492-236487ac4d68-image.png

            I've "force all" set ...
            ( because : when I fire up my OpenVPN from my laptop phone etc, that is because I want to use one of devices on the pfSense LAN. I connect to these devices using their host names, known to unbound on pfSense. So, my phone will ask unbound what IP the device has, and I can connect.
            I don't need to use my company's VPN access as a VPN to visit other, Internet based sites. )

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            C 1 Reply Last reply Reply Quote 0
            • C
              CoffeeOrTea @Gertjan
              last edited by CoffeeOrTea

              @Gertjan

              That's the configuration that I want to use, but it's the one that breaks everything for me. In order to get it to work, I have to uncheck that box, then manually specify the IPv4 Local networks.

              Curious - do you have your OpenVPN server assigned to an interface?

              The reason I ask is because enabling "Redirect IPv4 Gateway" works for me UNTIL I assign it to an interface, then everything breaks.

              1 Reply Last reply Reply Quote 0
              • V
                viragomann @CoffeeOrTea
                last edited by

                @CoffeeOrTea said in Network connectivity issue from OpenVPN client:

                That said, everything is working flawlessly right now due to disabling the 'force all traffic through tunnel' option and manually specifying accessible subnets. I just don't understand why the 'force all traffic through tunnel' breaks everything.

                With "redirect gateway" checked, I expect, that you at least can access the remote LANs.
                If that's not the case, I'd suspect, that there is an issue with your client. Maybe you can try another one.

                C 1 Reply Last reply Reply Quote 0
                • C
                  CoffeeOrTea @viragomann
                  last edited by CoffeeOrTea

                  @viragomann said in Network connectivity issue from OpenVPN client:

                  With "redirect gateway" checked, I expect, that you at least can access the remote LANs.
                  If that's not the case, I'd suspect, that there is an issue with your client. Maybe you can try another one.

                  I would expect that too, but that's the issue that I'm having. Client is Android phone with OpenVPN app. Are you saying to try another device, or app?

                  The only way that I've been able to get it to work is by configuring it this way. I would much rather get the "Redirect Gateway" option working, though.

                  Edit for clarification: The only way that I've been able to get it to work after assigning OpenVPN to an interface is to configure it as the picture below. If I don't assign OpenVPN to an interface, then "Redirect Gateway" works.

                  s3.png

                  V C 2 Replies Last reply Reply Quote 0
                  • V
                    viragomann @CoffeeOrTea
                    last edited by

                    @CoffeeOrTea said in Network connectivity issue from OpenVPN client:

                    Edit for clarification: The only way that I've been able to get it to work after assigning OpenVPN to an interface is to configure it as the picture below. If I don't assign OpenVPN to an interface, then "Redirect Gateway" works.

                    Not clear at the moment, why this happens, but there is no benefit of assigning an interface to an access server anyway.
                    This is only useful if you need to route traffic to the client site.

                    1 Reply Last reply Reply Quote 0
                    • C
                      CoffeeOrTea @CoffeeOrTea
                      last edited by

                      Follow up thought...

                      Because assigning my OpenVPN server to an interface automatically creates a new gateway, would I need edit this setting in the OpenVPN server config?

                      s4.jpg

                      V 1 Reply Last reply Reply Quote 0
                      • V
                        viragomann @CoffeeOrTea
                        last edited by

                        @CoffeeOrTea
                        No, there is nothing to change after assigning the interface.

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