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

    Port forwarding problems

    Scheduled Pinned Locked Moved NAT
    43 Posts 6 Posters 13.4k 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.
    • K
      kevindd992002
      last edited by

      Here's a screenshot of the main settings of the dd-wrt switch:

      I think I know the problem. The gateway and local dns are not specified which is why it cannot respond to outside requests?

      But this switch is accessible via the LAN side of pfsense.

      1 Reply Last reply Reply Quote 0
      • K
        kevindd992002
        last edited by

        I specified 192.168.1.1 for both Gateway and Local DNS and IT WORKED! So this NAT entry is solved.

        How about the others?

        1 Reply Last reply Reply Quote 0
        • G
          Gloom
          last edited by

          lol you want your monies worth  ;)

          Again I'm going to guess it's a routing issue. What's the OS of the boxes running Sab?

          Never underestimate the power of human stupidity

          1 Reply Last reply Reply Quote 0
          • K
            kevindd992002
            last edited by

            @Gloom:

            lol you want your monies worth  ;)

            Again I'm going to guess it's a routing issue. What's the OS of the boxes running Sab?

            Lol, sorry about that.

            Nope, I already solved the SAB problems. I'm pertaining now to entry numbers 3 and 5.

            1 Reply Last reply Reply Quote 0
            • G
              Gloom
              last edited by

              Sorry I thought I'd already posted what I thought was wrong with the setup to cause 3 and 5
              The packet arriving at the 192.168.103.3 interface has the originating IP address of the request ie the computer on the internet. So it responds back but because it's default route is via wan3 the reply goes back to the sender with a different public IP than the one the request was sent to and the remote PC rejects it because it is not expecting a response from that host.
              Can't see a fix for it as the default route for wan3 must be out so all I can suggest is that you move the NAT over to the wan3 IP and come in that way.

              Never underestimate the power of human stupidity

              1 Reply Last reply Reply Quote 0
              • K
                kevindd992002
                last edited by

                @Gloom:

                Sorry I thought I'd already posted what I thought was wrong with the setup to cause 3 and 5
                The packet arriving at the 192.168.103.3 interface has the originating IP address of the request ie the computer on the internet. So it responds back but because it's default route is via wan3 the reply goes back to the sender with a different public IP than the one the request was sent to and the remote PC rejects it because it is not expecting a response from that host.
                Can't see a fix for it as the default route for wan3 must be out so all I can suggest is that you move the NAT over to the wan3 IP and come in that way.

                Ah. How do you move the NAT over to the wan3 IP?

                1 Reply Last reply Reply Quote 0
                • K
                  kevindd992002
                  last edited by

                  BUMP!

                  1 Reply Last reply Reply Quote 0
                  • G
                    Gloom
                    last edited by

                    Does it have a fixed IP or is it dynamic?

                    Never underestimate the power of human stupidity

                    1 Reply Last reply Reply Quote 0
                    • K
                      kevindd992002
                      last edited by

                      @Gloom:

                      Does it have a fixed IP or is it dynamic?

                      The wan3 router ip or the modem3 ip? Both of them have fixed IP anyway.

                      1 Reply Last reply Reply Quote 0
                      • G
                        Gloom
                        last edited by

                        If it's a fixed public IP then just put the NAT on the public interface and add a rule to allow the traffic through to the internal IP. It's exactly the same as the ones you have already setup just on a different interface.

                        Never underestimate the power of human stupidity

                        1 Reply Last reply Reply Quote 0
                        • K
                          kevindd992002
                          last edited by

                          @Gloom:

                          If it's a fixed public IP then just put the NAT on the public interface and add a rule to allow the traffic through to the internal IP. It's exactly the same as the ones you have already setup just on a different interface.

                          Ok, I'll try that. Thanks :)

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