max number of RDR rules

[russellc]

i seem to onlybe able to have 12 RDR NAT rules. I require about
18 ports for all the applications. Is there a way to increase this

[el_lobo]

I've not needed to set up that many rules so can't comment directly - however the review done on adslguide (see http://www.adslguide.org.uk/hardware/reviews/2003/q1/sar_110.asp) would suggest the same limit.

Can you get away with enabling port ranges?

[russellc]

client access for the as400 requires about 10 ports plus other apps takes me above 12 rules

[el_lobo]

Yes, but are these ports all at separate locations or can you enable several (say 2000-2020) with one rule?

[el_lobo]

Apologies for responding to my own post but I have just realised my error in thinking that port ranges can be forwarded using a single RDR rule!

A range of WAN side ports can be forwarded but only to a single LAN side port :( . Just tested this and thats the way it works.

So basically there is a limit of 12 NAT rules which can also be taken as the limit for ports that can be forwarded too.

Steve/John - it would be really useful if the NAT rule limit could be extended in a new release of the firmware AND/OR the RDR rule capability be extended to cater for a range of local ports (or the facility to enable a range to be redirected to a local range 'starting at' the specified local port).

This is a nice router lets hope that it will continue to be improved!

[LeKeiser]

I'm not sure I'm getting this right... Do you mean that you can't open a wide range ports on both the LAN side and the WAN side?? I don't see the point to be able to open let's say 100 ports on the WAN side only to be able to forward them to ONE LAN port... It can't work, can it? :confused:

[el_lobo]

That seems to be what it does!

If you look at the RDR rule it provides for a range of incoming ports but only a single value for the re-directed port. I had originally assumed that this would be the starting port for the range, and that it would just use the equivalent number upwards (to match the chosen incoming range). It didn't work like that.

I set up a couple of different webservers on ports 80,81 and 82 of one of my machines (Note - I used different servers to ensure that I didn't get any virtual server mappings wrong), and then forwarded the range 8080-8082 to 80.

I then browsed the different ports (8080-8082) expecting to get the different intro pages from the different webservers. Instead I got the intro page from the webserver on port 80 each time! :confused:

As stated previously I'm not sure of the benefit of this, and can only assume that it is an error (unless somebody can give me an understandable reason for this behaviour?).

I'm hoping that Solwise will talk to Taiwan about this and get it fixed/changed, as it will be a useful feature when it works. Additionally I'm also hoping that they will get the 12 NAT rule limit increased.

I would be interested if anybody else has tested this and got different results, as I would like to know where I'm going wrong!