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

    Only Some of my Port Forwards work ?

    Scheduled Pinned Locked Moved Firewalling
    43 Posts 3 Posters 5.9k 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
      Cire3 @NogBadTheBad
      last edited by

      @nogbadthebad said in Only Some of my Port Forwards work ?:

      packet capture on the WAN

      Sorry, thought you wanted rule, as I already posted the NAT Forward rules. My bad. However I double checked.

      I'm connected over VPN, and know enough to be dangerous...lol Any way I can packet capture on the WAN remote ? Never had to do this.

      NogBadTheBadN 1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad @Cire3
        last edited by

        @cire3 yup have a look at the diagnostics section.

        You can download the packet capture from the page and view in wireshark.

        Andy

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

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

          @nogbadthebad Just seen it after I asked the question. Way cool. Downloading now after trying to check port.

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

            @cire3 Host address being my Static WAN ? And should I use a port or just capture?

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

              @cire3 Packate Capture 9300.PNG

              And this from PFSense :

              15:25:00.282522 IP 198.199.98.246.50719 > 198.0.115.21.9300: tcp 0
              15:25:01.278833 IP 198.199.98.246.50719 > 198.0.115.21.9300: tcp 0
              15:25:01.283582 IP 198.199.98.246.50724 > 198.0.115.21.9300: tcp 0
              15:25:02.282636 IP 198.199.98.246.50724 > 198.0.115.21.9300: tcp 0
              15:25:02.284759 IP 198.199.98.246.50731 > 198.0.115.21.9300: tcp 0
              15:25:03.282818 IP 198.199.98.246.50731 > 198.0.115.21.9300: tcp 0
              15:25:56.035819 IP 198.199.98.246.50880 > 198.0.115.21.9300: tcp 0
              15:25:57.034127 IP 198.199.98.246.50880 > 198.0.115.21.9300: tcp 0
              15:25:57.036750 IP 198.199.98.246.50883 > 198.0.115.21.9300: tcp 0
              15:25:58.034059 IP 198.199.98.246.50883 > 198.0.115.21.9300: tcp 0
              15:25:58.038290 IP 198.199.98.246.50889 > 198.0.115.21.9300: tcp 0
              15:25:59.038237 IP 198.199.98.246.50889 > 198.0.115.21.9300: tcp 0
              15:26:00.276783 IP 198.199.98.246.50895 > 198.0.115.21.9300: tcp 0
              15:26:01.274091 IP 198.199.98.246.50895 > 198.0.115.21.9300: tcp 0
              15:26:01.277837 IP 198.199.98.246.50897 > 198.0.115.21.9300: tcp 0
              15:26:02.273897 IP 198.199.98.246.50897 > 198.0.115.21.9300: tcp 0
              15:26:02.278893 IP 198.199.98.246.50899 > 198.0.115.21.9300: tcp 0
              15:26:03.277951 IP 198.199.98.246.50899 > 198.0.115.21.9300: tcp 0

              NogBadTheBadN 1 Reply Last reply Reply Quote 0
              • NogBadTheBadN
                NogBadTheBad @Cire3
                last edited by

                @cire3 OK so it looks like 9300 is hitting the WAN interface.

                Andy

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

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

                  @nogbadthebad Yea, It would have been great to blame Comcast. Not today I guess...lol

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

                    @cire3 Firewall Rules WAN.PNG

                    Figured I would post in case something didn't look right

                    C NogBadTheBadN 2 Replies Last reply Reply Quote 0
                    • C
                      Cire3 @Cire3
                      last edited by

                      @cire3 States.PNG

                      This is what's back in states

                      1 Reply Last reply Reply Quote 0
                      • NogBadTheBadN
                        NogBadTheBad @Cire3
                        last edited by NogBadTheBad

                        @cire3 Rules are read from the top down, I suggest you have a read:-

                        https://docs.netgate.com/pfsense/en/latest/firewall/rule-list-intro.html

                        Everything TCP will hit the 3rd rule down.

                        Andy

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

                        C 2 Replies Last reply Reply Quote 0
                        • C
                          Cire3 @NogBadTheBad
                          last edited by

                          @nogbadthebad Reset States again, waiting for it to boot back up and VPN in

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

                            @nogbadthebad UDP to TCP/UDP to TCP. No change

                            NogBadTheBadN 1 Reply Last reply Reply Quote 0
                            • NogBadTheBadN
                              NogBadTheBad @Cire3
                              last edited by

                              @cire3 If you still have that 3rd rule you need to delete it, it won't hit your NAT rule.

                              Its very dangerous what you've done with that rule and if you havent noticed all your TCP traffic is hitting it.

                              Andy

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

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

                                @nogbadthebad Oh dam, corrected :)

                                Any other thoughts ? Hate to rebuild the box.

                                Only thing I notice is the port conversions forward, but the port to port match don't. Or it's just a fluke.

                                NogBadTheBadN 1 Reply Last reply Reply Quote 0
                                • NogBadTheBadN
                                  NogBadTheBad @Cire3
                                  last edited by NogBadTheBad

                                  @cire3 I'd check with the supplier again, you've got to and - in your first post, is that a range or is it convert one port to another.

                                  A packet capture using the phones IP address would show you whats hiting the firewall.

                                  Andy

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

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

                                    @nogbadthebad Directions.PNG

                                    This was the direction I was given. Some ports convert, while one is a range

                                    Ports Working :

                                    44443 Convert to 443 Forward to 10.10.1.25 Status: : Open
                                    24493 Convert to 2728 Forward to 10.10.1.25 Status : Open

                                    Port Not Working :

                                    16000 Through 16511 Forward to 10.10.1.26 Status : Closed
                                    9300 Forward to 10.10.1.25 Status : Closed

                                    NogBadTheBadN 1 Reply Last reply Reply Quote 0
                                    • NogBadTheBadN
                                      NogBadTheBad @Cire3
                                      last edited by NogBadTheBad

                                      @cire3 Well your packet capture shows port 9300 TCP not UDP as per their info.

                                      15:25:00.282522 IP 198.199.98.246.50719 > 198.0.115.21.9300: tcp 0
                                      15:25:01.278833 IP 198.199.98.246.50719 > 198.0.115.21.9300: tcp 0
                                      15:25:01.283582 IP 198.199.98.246.50724 > 198.0.115.21.9300: tcp 0
                                      15:25:02.282636 IP 198.199.98.246.50724 > 198.0.115.21.9300: tcp 0
                                      15:25:02.284759 IP 198.199.98.246.50731 > 198.0.115.21.9300: tcp 0
                                      15:25:03.282818 IP 198.199.98.246.50731 > 198.0.115.21.9300: tcp 0
                                      15:25:56.035819 IP 198.199.98.246.50880 > 198.0.115.21.9300: tcp 0
                                      15:25:57.034127 IP 198.199.98.246.50880 > 198.0.115.21.9300: tcp 0
                                      15:25:57.036750 IP 198.199.98.246.50883 > 198.0.115.21.9300: tcp 0
                                      15:25:58.034059 IP 198.199.98.246.50883 > 198.0.115.21.9300: tcp 0
                                      15:25:58.038290 IP 198.199.98.246.50889 > 198.0.115.21.9300: tcp 0
                                      15:25:59.038237 IP 198.199.98.246.50889 > 198.0.115.21.9300: tcp 0
                                      15:26:00.276783 IP 198.199.98.246.50895 > 198.0.115.21.9300: tcp 0
                                      15:26:01.274091 IP 198.199.98.246.50895 > 198.0.115.21.9300: tcp 0
                                      15:26:01.277837 IP 198.199.98.246.50897 > 198.0.115.21.9300: tcp 0
                                      15:26:02.273897 IP 198.199.98.246.50897 > 198.0.115.21.9300: tcp 0
                                      15:26:02.278893 IP 198.199.98.246.50899 > 198.0.115.21.9300: tcp 0
                                      15:26:03.277951 IP 198.199.98.246.50899 > 198.0.115.21.9300: tcp 0

                                      Andy

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

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

                                        @nogbadthebad Just changed that a bit ago as I was testing both ways. Set to UDP per instructions. Just trying to find if the information I have is accurate.

                                        Will it show open even if there is not a device on that IP ? Just a curious thing more than anything. Is PFSense rejecting it, or is the device not accepting it was my wonder

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

                                          Hitting WAN.PNG

                                          This is in States from me using portchecker.co

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

                                            @cire3 Wait a second. Does portchecker.co use TCP ? If so, h
                                            ow do I check UDP ?

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