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

NAT - Source Port - Range

Scheduled Pinned Locked Moved NAT
5 Posts 4 Posters 2.5k 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.
  • M
    mnsmani
    last edited by Mar 21, 2007, 4:30 PM

    I defined the Source Port Range from 9000 to 9900….. Port forwarding works fine for port 9000 and rest of the ports it is ignored.....

    GUI has the facility to enter Range.... but it does not work.... why ? Any reasons.... or any patches ?

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by Mar 21, 2007, 4:35 PM

      Show us the relevant rules from /tmp/rules.debug so we can verify that it is created correctly.

      1 Reply Last reply Reply Quote 0
      • J
        jeroen234
        last edited by Mar 21, 2007, 6:55 PM

        for port forwarding you normaly don't set the sourche port only the destination port
        source ports are random

        1 Reply Last reply Reply Quote 0
        • M
          mnsmani
          last edited by Mar 22, 2007, 10:52 AM

          @sullrich:

          Show us the relevant rules from /tmp/rules.debug so we can verify that it is created correctly.

          Entry in /tmp/rules.debug

          System Aliases

          ng0 = "{ rl0 ng0 }"
          wan = "{ rl0 ng0 }"

          #NAT Inbound Redirects
          rdr on ng0 proto tcp from any to any port 2000:5000 -> 192.168.19.160 port 3000:*

          http://wanip: <port>-> it should get redirected to http://192.168.19.160:3000 where <port>user can enter anything, it should redirected to 3000 of the IP specified. (This IP is part of the lan of the device)

          but, I found 2000 maps to 3000 and 5000 maps to 6000….. one to one match.....</port></port>

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by Mar 22, 2007, 9:13 PM

            That is correct behaviour. You can shift ports with it but not redirect a range of ports to the same port.

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received