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

Port Forward does not work..

Firewalling
help nat nat rules firewall firewall rules
5
71
12.8k
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.
  • R
    root1ng LAYER 8
    last edited by root1ng Nov 5, 2023, 11:42 AM Nov 5, 2023, 11:41 AM

    Hello,

    I run pfSense on a virtual machine in Proxmox, and on another virtual machine I installed a teamspeak3 server, which needs the following open ports to be able to connect - 9987, 30033, but I added the rules in NAT -> Port Forward, but without results. I still can't connect with the public IP but only with the local one.
    I am attaching some screenshots, maybe I made a mistake somewhere.

    🔒 Log in to view

    🔒 Log in to view

    🔒 Log in to view

    Thanks!

    N J 2 Replies Last reply Nov 5, 2023, 11:47 AM Reply Quote 1
    • N
      NogBadTheBad @root1ng
      last edited by Nov 5, 2023, 11:47 AM

      @root1ng change the firewall destination rule to WAN address.

      Andy

      1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

      B V 2 Replies Last reply Nov 5, 2023, 11:52 AM Reply Quote 0
      • B
        Bob.Dig LAYER 8 @NogBadTheBad
        last edited by Bob.Dig Nov 5, 2023, 11:54 AM Nov 5, 2023, 11:52 AM

        @NogBadTheBad said in Port Forward does not work..:

        @root1ng change the firewall destination rule to WAN address.

        Why? Port Forward comes first so he did it correct.

        Enable NAT reflection (Pure NAT) in the Port Forward and see if it makes a difference to you. If not, you probably have a problem with your proxmox. The Port Forward is looking fine.

        R N 2 Replies Last reply Nov 5, 2023, 11:54 AM Reply Quote 1
        • R
          root1ng LAYER 8 @Bob.Dig
          last edited by Nov 5, 2023, 11:54 AM

          @Bob-Dig

          It is on the default system, I tried with NAT + Proxy activated and with Pure Nat, it doesn't work.

          1 Reply Last reply Reply Quote 1
          • V
            viragomann @NogBadTheBad
            last edited by Nov 5, 2023, 11:56 AM

            @NogBadTheBad said in Port Forward does not work..:

            change the firewall destination rule to WAN address.

            No, when forwarding traffic, the destination in the firewall rule has to be the backend host. It's also be generated automatically this way if applicable.

            @root1ng
            The rule doesn't show up any hits. So check out if the packets even arrive on your WAN.
            You can use packets capture to do this.

            Is there a router in front of pfSense.

            @root1ng said in Port Forward does not work..:

            I still can't connect with the public IP but only with the local one.

            Or do you only want local devices to use the WAN address for whatever reason?

            R 1 Reply Last reply Nov 5, 2023, 12:01 PM Reply Quote 1
            • R
              root1ng LAYER 8 @viragomann
              last edited by Nov 5, 2023, 12:01 PM

              @viragomann said in Port Forward does not work..:

              The rule doesn't show up any hits. So check out if the packets even arrive on your WAN.
              You can use packets capture to do this.

              Is there a router in front of pfSense.

              I don't know how to use Packet Capture, and in front of pfSense there is only the ONT, but it has nothing to do with what happens after it.
              It is only a fiber to RJ45 converter.

              @viragomann said in Port Forward does not work..:

              Or do you only want local devices to use the WAN address for whatever reason?

              It's a public server and that's why I need it to be accessed with the wan address.

              V 1 Reply Last reply Nov 5, 2023, 12:08 PM Reply Quote 1
              • V
                viragomann @root1ng
                last edited by Nov 5, 2023, 12:08 PM

                @root1ng said in Port Forward does not work..:

                It's a public server and that's why I need it to be accessed with the wan address.

                And what's the recent issue you're on? Accessing it from outside or from inside your network?

                For inside access you should rather use its local IP and a DNS host override for the public FQDN.

                R 1 Reply Last reply Nov 5, 2023, 12:09 PM Reply Quote 0
                • R
                  root1ng LAYER 8 @viragomann
                  last edited by Nov 5, 2023, 12:09 PM

                  @viragomann said in Port Forward does not work..:

                  And what's the recent issue you're on? Accessing it from outside or from inside your network?

                  For inside access you should rather use its local IP and a DNS host override for the public FQDN.

                  I can't access it from the outside, only from the inside with a private local IP, not the public one.

                  V 1 Reply Last reply Nov 5, 2023, 12:15 PM Reply Quote 1
                  • V
                    viragomann @root1ng
                    last edited by Nov 5, 2023, 12:15 PM

                    @root1ng
                    So I assume, you're not sure, if the desired traffic is even forwarded to your public IP. It could be blocked by the ISP.
                    BTW, do you even have a real public IP? And if, is it assigned to pfSense WAN interface (ONT in bridge mode)?

                    If yes, sniff the WAN traffic to ensure, that the traffic is even forward to pfSense.
                    Diagnostic > Packet Capture
                    Select the WAN interface
                    In the "untagged filter" section at port number select "all off" and enter "9987|30033". This capture both.
                    Hit start and try to access your server from the internet.

                    1 Reply Last reply Reply Quote 1
                    • J
                      johnpoz LAYER 8 Global Moderator @root1ng
                      last edited by Nov 5, 2023, 12:16 PM

                      @root1ng I don't see any hits on either of those rules that allow for your port forwards to port 9987 and 30033

                      First step in troubleshooting a port forward or any wan side firewall rule is validate the traffic actually gets to pfsense, go to like can you see me . org and send some traffic. Be it you allow it or forward it or not.. You should see that traffic in your packet capture.

                      For example just sent some traffic to port 9987 like your forward, as you can see from packet capture on my wan pfsense actually sees this traffic.

                      🔒 Log in to view

                      If pfsense never sees the traffic no amount of firewall rules or forwards would ever work.

                      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 24.11 | Lab VMs 2.7.2, 24.11

                      B R 2 Replies Last reply Nov 5, 2023, 12:24 PM Reply Quote 0
                      • B
                        Bob.Dig LAYER 8 @johnpoz
                        last edited by Nov 5, 2023, 12:24 PM

                        @johnpoz said in Port Forward does not work..:

                        If pfsense never sees the traffic no amount of firewall rules or forwards would ever work.

                        For him it is UDP but right. For testing do something with TCP.

                        B 1 Reply Last reply Nov 5, 2023, 12:30 PM Reply Quote 0
                        • N
                          NogBadTheBad @Bob.Dig
                          last edited by Nov 5, 2023, 12:27 PM

                          @Bob-Dig Oops forgot about the order 👍

                          Andy

                          1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

                          1 Reply Last reply Reply Quote 0
                          • B
                            Bob.Dig LAYER 8 @Bob.Dig
                            last edited by Bob.Dig Nov 5, 2023, 12:31 PM Nov 5, 2023, 12:30 PM

                            @Bob-Dig said in Port Forward does not work..:

                            For testing do something with TCP.

                            Because it is more easy I have to add. 😉

                            For instance, while it is showing as stealth because there is no service running on that port, I still see that the rule was triggered.

                            🔒 Log in to view

                            1 Reply Last reply Reply Quote 0
                            • R
                              root1ng LAYER 8 @johnpoz
                              last edited by Nov 5, 2023, 12:30 PM

                              @johnpoz said in Port Forward does not work..:

                              @root1ng I don't see any hits on either of those rules that allow for your port forwards to port 9987 and 30033

                              First step in troubleshooting a port forward or any wan side firewall rule is validate the traffic actually gets to pfsense, go to like can you see me . org and send some traffic. Be it you allow it or forward it or not.. You should see that traffic in your packet capture.

                              For example just sent some traffic to port 9987 like your forward, as you can see from packet capture on my wan pfsense actually sees this traffic.

                              If pfsense never sees the traffic no amount of firewall rules or forwards would ever work.

                              30033 TCP seems to work, 9987 UDP doesn't and I don't understand why, all ports are open from ISP

                              🔒 Log in to view
                              🔒 Log in to view
                              🔒 Log in to view

                              V B 2 Replies Last reply Nov 5, 2023, 12:32 PM Reply Quote 1
                              • V
                                viragomann @root1ng
                                last edited by Nov 5, 2023, 12:32 PM

                                @root1ng
                                The port checker might only be able to do TCP checks.

                                J 1 Reply Last reply Nov 5, 2023, 12:59 PM Reply Quote 1
                                • B
                                  Bob.Dig LAYER 8 @root1ng
                                  last edited by Nov 5, 2023, 12:33 PM

                                  @root1ng said in Port Forward does not work..:

                                  30033 TCP seems to work,

                                  That does look good.

                                  R 1 Reply Last reply Nov 5, 2023, 12:34 PM Reply Quote 0
                                  • R
                                    root1ng LAYER 8 @Bob.Dig
                                    last edited by Nov 5, 2023, 12:34 PM

                                    @Bob-Dig said in Port Forward does not work..:

                                    That does look good

                                    Yes, but the main one is 9987 .. and for now it still doesn't work.

                                    B V 2 Replies Last reply Nov 5, 2023, 12:37 PM Reply Quote 1
                                    • B
                                      Bob.Dig LAYER 8 @root1ng
                                      last edited by Bob.Dig Nov 5, 2023, 12:37 PM Nov 5, 2023, 12:37 PM

                                      @root1ng said in Port Forward does not work..:

                                      Yes, but the main one is 9987 .. and for now it still doesn't work.

                                      Maybe your proxmox Firewall is blocking UDP?

                                      R 1 Reply Last reply Nov 5, 2023, 12:38 PM Reply Quote 0
                                      • R
                                        root1ng LAYER 8 @Bob.Dig
                                        last edited by Nov 5, 2023, 12:38 PM

                                        @Bob-Dig said in Port Forward does not work..:

                                        Maybe your proxmox Firewall is blocking UDP?

                                        All firewalls are disabled.. tell me where to check and I'll come back

                                        1 Reply Last reply Reply Quote 0
                                        • V
                                          viragomann @root1ng
                                          last edited by Nov 5, 2023, 12:42 PM

                                          @root1ng said in Port Forward does not work..:

                                          Yes, but the main one is 9987 .. and for now it still doesn't work.

                                          As long as there is no service listening on this port at TCP, the access won't succeed naturally.
                                          Your backend is listening at UDP 9987 and UDP probably cannot be probed with the port checker.

                                          R 1 Reply Last reply Nov 5, 2023, 12:44 PM Reply Quote 0
                                          3 out of 71
                                          • First post
                                            3/71
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.