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

    unable to get firewall to route traffic

    Scheduled Pinned Locked Moved NAT
    52 Posts 5 Posters 4.2k 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.
    • Bob.DigB
      Bob.Dig LAYER 8 @zari90
      last edited by Bob.Dig

      @zari90 said in unable to get firewall to route traffic:

      done rule is there now

      The states show zero, that is not good. This could mean something is blocking it before pfSense. Or you using the wrong address with the port-checker? Have you tried with your WAN-IP-Address or just with a domain name? Try both. If it is still not working and that port tester is working, there is something else blocking it before pfSense. And there is nothing we could do about that within pfSense and here.

      Z 1 Reply Last reply Reply Quote 0
      • Z
        zari90 @zari90
        last edited by

        @zari90
        just with the wan IP the windows 10 machine is not in dns, let me try with Jellyfin add a rule and see if that works

        Bob.DigB 1 Reply Last reply Reply Quote 0
        • Z
          zari90 @Bob.Dig
          last edited by

          @Bob-Dig

          963d6703-1b5a-435b-943e-369179cde1c1-image.png

          e27360ac-da1c-4735-8485-1da8867cd5f3-image.png

          98247c3d-ad22-4e7f-92c6-7142820035c2-image.png
          55f14345-109c-41de-bb3c-892755b76577-image.png

          nothing changed

          1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8 @zari90
            last edited by Bob.Dig

            @zari90 said in unable to get firewall to route traffic:

            10 machine is not in dns

            It is not about DNS at this point. If you test the port of your WAN-IP from the outside, it should create a state on WAN if there is a rule for that. For whatever reason now there is something shown for your first rule. Don't take the screenshot to quick after the port test, wait some seconds and reload the page before you take a screenshot or look.

            Z 1 Reply Last reply Reply Quote 0
            • Z
              zari90 @Bob.Dig
              last edited by

              @Bob-Dig
              okay tried both domain name and WAN-IP but port still seems to closed

              Bob.DigB M 2 Replies Last reply Reply Quote 0
              • Bob.DigB
                Bob.Dig LAYER 8 @zari90
                last edited by

                @zari90 Look at the states.

                Z 1 Reply Last reply Reply Quote 0
                • M
                  MoonKnight @zari90
                  last edited by

                  @zari90
                  What protocol are your service running at? TCP or UDP?
                  Not all port-tester can to UDP port test.

                  --- 24.11 ---
                  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)

                  Z 1 Reply Last reply Reply Quote 0
                  • Z
                    zari90 @Bob.Dig
                    last edited by

                    @Bob-Dig
                    can see the state yes trickling in but port checker still shows port is closed on both NAT port forward rules

                    Bob.DigB 1 Reply Last reply Reply Quote 0
                    • Z
                      zari90 @MoonKnight
                      last edited by

                      @MoonKnight
                      for jellyfin its tcp/udp and the other is just tcp

                      1 Reply Last reply Reply Quote 0
                      • Bob.DigB
                        Bob.Dig LAYER 8 @zari90
                        last edited by Bob.Dig

                        @zari90 So that is a good sign, your pfSense-WAN was receiving the connections! Now the problem is on your hosts, maybe the windows firewall is blocking something or whatever but it is not within pfSense, from what you have told us.

                        Z 2 Replies Last reply Reply Quote 0
                        • Z
                          zari90 @Bob.Dig
                          last edited by

                          @Bob-Dig
                          21dfd575-9c3d-4ca2-9de2-2b327e6b8e58-image.png
                          3df41420-8388-4887-90f8-86775a3eae2a-image.png
                          fa79df85-b6ce-4b63-bd45-e4113f471cf7-image.png

                          showing there is traffic but nothing ports still closed

                          1 Reply Last reply Reply Quote 0
                          • Z
                            zari90 @Bob.Dig
                            last edited by

                            @Bob-Dig
                            can't access jellyfin externally either

                            Bob.DigB 1 Reply Last reply Reply Quote 0
                            • Bob.DigB
                              Bob.Dig LAYER 8 @zari90
                              last edited by

                              @zari90 Outbound NAT is still on automatic? Gateways are default? Then there es nothing I could tell you.

                              Z 2 Replies Last reply Reply Quote 0
                              • Z
                                zari90 @Bob.Dig
                                last edited by

                                @Bob-Dig

                                everything still default only port change for pfsense 10443 so nothing else changed

                                1 Reply Last reply Reply Quote 0
                                • Z
                                  zari90 @Bob.Dig
                                  last edited by

                                  @Bob-Dig
                                  and this was changed to pure NAT828d5e4d-4751-45f7-bb03-46c3d63c77a4-image.png

                                  Bob.DigB 1 Reply Last reply Reply Quote 0
                                  • Bob.DigB
                                    Bob.Dig LAYER 8 @zari90
                                    last edited by

                                    @zari90 Pure NAT might be okay for beginners but also it has nothing to do with your problem. Maybe try another port tester like GRC | ShieldsUP! But again, it is not with pfSense anymore, must be your machines now.

                                    Z 1 Reply Last reply Reply Quote 0
                                    • Z
                                      zari90 @Bob.Dig
                                      last edited by

                                      @Bob-Dig
                                      if I use cloudflared docker container then I can get to the sites no issue so not sure why it isn't working normally okay thanks will poke around more

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