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

    AirVPN + Open Port, I've tried everything and it's not worth it

    Scheduled Pinned Locked Moved OpenVPN
    18 Posts 4 Posters 1.7k Views 4 Watching
    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.
    • V Offline
      viragomann @neba
      last edited by

      @neba said in AirVPN + Open Port, I've tried everything and it's not worth it:

      I expect that when I go to check that port on the AirVPN site or on canyouseeme.org, it will show that the port is open.

      I'm not sure on this. The forwarded port might be the tracker and the software is expecting UDP packets?
      The port checker, however, only sends TCP packets, which your host probably to not respond to.

      You can sniff the traffic on the involved interfaces, however, while probing the port on your pfSense to see if there is something coming in.

      N 1 Reply Last reply Reply Quote 0
      • N Offline
        neba @viragomann
        last edited by

        @viragomann said in AirVPN + Open Port, I've tried everything and it's not worth it:

        You can sniff the traffic on the involved interfaces, however, while probing the port on your pfSense to see if there is something coming in.

        I don't know how?

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

          @neba
          Diagnostic > Packet Capture

          Select Air_SRB for the interface.
          At port number enter 47057.
          Hit "Start" and go to the port checker website and test again.

          N 1 Reply Last reply Reply Quote 0
          • N Offline
            neba @viragomann
            last edited by

            @viragomann

            This is what it looks like when qBittorrent is started.
            When I turn off qBit, and check openport, nothing happens

            eff3b21f-ef77-418d-9089-48cb76227725-image.png

            M V 2 Replies Last reply Reply Quote 0
            • M Offline
              MoonKnight @neba
              last edited by

              @neba

              This one?
              97e3a082-b09a-4e35-b3dd-21aaf6b66828-image.png

              Make sure you have set the right protocol in your OpenVPN client.

              4c30c16b-f529-4214-9818-d925009642b2-image.png

              --- 25.07 ---
              Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
              Kingston DDR4 2666MHz 16GB ECC
              2 x HyperX Fury SSD 120GB (ZFS-mirror)
              2 x Intel i210 (ports)
              4 x Intel i350 (ports)

              N 1 Reply Last reply Reply Quote 0
              • V Offline
                viragomann @neba
                last edited by

                @neba
                So obviously the port is properly forwarded to you. Now, what's your issue? Only that the port check fails?

                As mentioned, I expect it to fail, since it only sends TCP packets. But I also expect, that you see this TCP packet in the capture.

                N 1 Reply Last reply Reply Quote 0
                • N Offline
                  neba @MoonKnight
                  last edited by

                  @MoonKnight

                  It's like this for me, should I change to TCP on Ipv4
                  90b17e3a-6494-4b1c-b075-f0daf4af9001-image.png

                  M 1 Reply Last reply Reply Quote 0
                  • M Offline
                    MoonKnight @neba
                    last edited by

                    @neba
                    I use UDP, but you have to make sure when you did the "config generator" you selected the UDP?
                    I haven't used OpenVPN for couple of years now, so I can't tell if there is other settings you need to change. :(

                    --- 25.07 ---
                    Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
                    Kingston DDR4 2666MHz 16GB ECC
                    2 x HyperX Fury SSD 120GB (ZFS-mirror)
                    2 x Intel i210 (ports)
                    4 x Intel i350 (ports)

                    1 Reply Last reply Reply Quote 0
                    • N Offline
                      neba @viragomann
                      last edited by

                      @viragomann

                      TCP
                      1f211071-dcb6-482c-ba2e-bf3f0e1852c4-image.png

                      UDP
                      fd68c6ef-3e2d-4d8a-af16-7de0349a5035-image.png

                      1 Reply Last reply Reply Quote 0
                      • N Offline
                        neba
                        last edited by

                        I solved the problem.
                        I didn't know that the whole chain has to be activated from the VPN server to the qBittorrent end user.
                        I always thought that it was enough to open the port on pfSense and that it would give me confirmation that the port is open. qBit must also be started.
                        At the moment I have a problem with Unraid, but I'll solve it easily, it's important for me that I set everything up nicely on pfSense.

                        THANK YOU EVERYONE

                        johnpozJ 1 Reply Last reply Reply Quote 0
                        • johnpozJ Online
                          johnpoz LAYER 8 Global Moderator @neba
                          last edited by

                          @neba said in AirVPN + Open Port, I've tried everything and it's not worth it:

                          pfSense and that it would give me confirmation that the port is open. qBit must also be started.

                          Pfsense doesn't listen and answer - it just forwards traffic it sees. If you want the port to show open, then yes where you forward to would have to be listening on that port, and actually answer. Users also run into sim sort of problem where they think its pfsense port forwarding problem, when its just the client having its own firewall and not answering. All kinds of other problems as well - like were you sending the traffic through pfsense, isn't using pfsense as its gateway so sends the answer to some other gateway.

                          Pfsense port forwarding is pretty rock solid stable and easy enough to setup.. In all the years I have been here on the forums - to be honest I don't recall even one issue that was not user issue.

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 25.07 | Lab VMs 2.8, 25.07

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