Port forwarding on Route 10

Is there an easy way to input many ports to be forwarded?
I need to forward a block of port such as 3240 to 3259.
Could you give me some hint how to insert blocks of ports?

I seems like, if you are adding a block of ports, you can do so using a dash in between like so:

1 Like

Is there a way to add a list of ports?

for example: 80,443,8443,8080

OK thank you for the information.
Can I also write :3240-3259,3270 if I have a block and one additional port to forward?
This would be really a great help.

Ah, I was wondering about the same thing for firewall rules, but it applies to port forwarding rules too of course. Found this thread right after posting a feature request here:

@Astina14, no, as far as I’m concerned, it is not possible to separate multiple blocks of ports, at least not by the most obvious characters like comma or semi-colon.

it seems that port range forwarding e.g. 192.168.200.10:51820-51830 does not work, yes the panel saves it but the ports remain closed. I checked on two services that stopped working after replacing the router with Route10. bug-report

1 Like

What shows up in uci show firewall?

Peculiar. I did a quick test with Ping Master port scanner and it responds with open ports. Testing against media streaming ports on my NAS, 50001 & 50002. Placed a deny all inter-VLAN rule at the bottom, then Allow the specific IP, with destinations ports as below

  • 50001-65535 → 50001 & 50002 open
  • 50000-65535 → 50001 & 50002 open
  • 50002-65535 → 50002 open
  • 50003-65535 → none open

when scanning ports 50000-50005.

Need to change 65535 to the specific ports to be used…

E.g.:
firewall.@rule[31].dest_port=‘50001-65535’

It should give you a redirect, not a rule when you do a port forward. It worked when I did:

uci gives me:
firewall.@redirect[8].src_dport=‘1007-1010’
and netcat works from the wan

1 Like

I checked the firewall rules for the range syntax, which worked. Didn’t have any port forwarding rules with syntax range. So I might have been to hasty in my conclusion that the firewall rules working implicated the same syntax should work for port forwarding. :face_with_peeking_eye: