It makes no sense to specify more than one port as a destination.
Colons (21:23) or separate entries. Not sure the use case here, perhaps you could elaborate?
Sorry, my mistake.How does it not make sense? I want to block outbound connections to servers on that port range.
That page is wrong, or out of date. (Notice how they changed the port number in image #8From the Asus docs, they are delimited by commas: https://www.asus.com/us/support/FAQ/1013636/
The Network Services Filter blocks traffic from the LAN to the WAN, not the other way around.
That page is wrong, or out of date. (Notice how they changed the port number in image #8)
Selecting FTP from the Well-Known Applications it creates 20:21. The pop-up help for that field says that only individual ports or ranges (defined by : < or >) are allowed.
Can you give an example of what you're trying to block.so how do I block LAN clients from connecting out to a port range? If I have a large range to block, I'm not going to list each port number.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!