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

    OPT1 Port forward doesn't work.

    Scheduled Pinned Locked Moved Routing and Multi WAN
    8 Posts 5 Posters 4.1k 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.
    • H Offline
      hacktek00
      last edited by

      -Dual WAN, both get the ip from DHCP.
      -They have totally different gateways.
      -Two NAT rules created for the same port on the same host, both with their auto generated firewall rule.
      -Port forward only works on WAN.
      -Already tried changing the gateway the rule uses, no dice.
      -Tried setting manual outbound configuration with static port enabled, no dice.

      uTorrent port checker sees the port as open on WAN but closed on OPT1, also tried it from work and nothing.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • H Offline
        hacktek00
        last edited by

        Uhm…anyone? This is really frustrating.

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG Offline
          GruensFroeschli
          last edited by

          uTorrent isnt really a reliable way to test portforwards.
          I would try it first simply with a port80 forward to a small webserver.

          Since you're testing with uTorrent i assume you want this to make use of multiple WANs for bittorrent.
          This wont really work since there is no torrent client which announces multiple public IPs for a single client.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • C Offline
            cheesyboofs
            last edited by

            This wont really work since there is no torrent client which announces multiple public IPs for a single client.

            This is true for seeding but when downloading a torrent the sessions/connections are fired out of each wan gateway to connect to all the different leechers in the swarm, making use of the additional bandwidth an extra modem provides.

            Author of pfSense themes:

            DARK-ORANGE

            CODE-RED

            1 Reply Last reply Reply Quote 0
            • H Offline
              hacktek00
              last edited by

              @GruensFroeschli:

              uTorrent isnt really a reliable way to test portforwards.
              I would try it first simply with a port80 forward to a small webserver.

              Since you're testing with uTorrent i assume you want this to make use of multiple WANs for bittorrent.
              This wont really work since there is no torrent client which announces multiple public IPs for a single client.

              Thanks for your response.

              No, i'm not interested in using multiwan for torrents, i have already been using it for usenet and general browsing for some time now and have been very happy with it. I'm testing with uTorrent because it was a pretty simple test to just go to their site and have their tool tell me if the port is open or not, which has always been closed in the case of the opt1 wan. I have also tried remote desktop from work and it have confirmed it does not work on opt1 even though the ports are forwarded. It works on the main WAN.

              1 Reply Last reply Reply Quote 0
              • H Offline
                hacktek00
                last edited by

                At work we have the exact same setup and it gives the exact same problem, OPT1 port forwards don't work. At work the providers are different than the ones i'm using at home so it's not that.

                No clues?

                1 Reply Last reply Reply Quote 0
                • I Offline
                  Itwerx
                  last edited by

                  For what it's worth, this should work fine.
                    That said, it's easy to get firewall traffic rules mis-matched with the NAT settings when making lots of changes.  If you "walk through" the traffic flow and nothing immediately obvious appears, then the logs are your friends…

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    joeswede
                    last edited by

                    I hade the same problem, this is what fixed it for me.

                    In Firewall Rules OPT1….changed Gateway from OPT1 to Default

                    In System Static routes......made a static route for OPT1 to DNS Server

                    For uTorrent you might need 6969 Torrent Connection Port in Firewall Rules.

                    These changes fixed all the problems I had with port forwarding and failover.

                    Hope this helps.

                    (pfsense is awsome, thanks to all the developers and programers.)

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