03-29-2012 02:30 PM
Hi,
I am replacing an ancient SOHO 90 series router with our new RV016, I was told this thing would do everything we needed which I didn't doubt, however, I am wondering if I made the wrong choice now. We have 5 IP's on one line coming into the current router, that isn't an issue, if needed I can make 5 seperate drops with each IP, but, now we have several servers hosting services on the same ports. For example 5.2 host a web server which is called to by the .250 address, 5.3 has one as well from .251, we have one on each of the 5, there are other servers too though on each of the 5 using the same ports. When I go to port forwarding the only option is to forward the single port to a single server, can I not forward ports from each WAN connection to a different server? Any help would be appreciated.
Here is a short sample from the old soho of what I want to do
ip nat inside source static tcp 192.168.5.5 443 *.*.*.250 443 extendable ip nat inside source static tcp 192.168.5.6 443 *.*.*.251 443 extendable ip nat inside source static tcp 192.168.5.5 80 *.*.*.250 80 extendable ip nat inside source static tcp 192.168.5.6 80 *.*.*.251 80 extendable ip nat inside source static tcp 192.168.5.22 80 *.252 80 extendable ip nat inside source static tcp 192.168.5.22 443 *.252 443 extendable ip nat inside source static tcp 192.168.5.96 6437 *.251 6437 extendable ip nat inside source static tcp 192.168.5.96 6438 *.251 6438 extendable ip nat inside source static tcp 192.168.5.96 6439 *.251 6439 extendable ip nat inside source static tcp 192.168.5.93 7437 *.251 7437 extendable ip nat inside source static tcp 192.168.5.93 7438 *.251 7438 extendable ip nat inside source static tcp 192.168.5.93 7439 *.251 7439 extendable ip nat inside source static tcp 192.168.5.101 8437 *.251 8437 extendable ip nat inside source static tcp 192.168.5.101 8438 *.251 8438 extendable ip nat inside source static tcp 192.168.5.101 8439 *.251 8439 extendable ip nat inside source static tcp 192.168.5.90 9437 *.251 9437 extendable ip nat inside source static tcp 192.168.5.90 9438 *.251 9438 extendable
03-29-2012 03:00 PM
The multi-WAN feature of RV016 is designed for redundancy and load balancing, so basic port forwarding is not tied to a specific WAN port. If a LAN server is exposed to the internet by the 1-to-1 NAT feature of RV016, the server can be accessed by a specified public IP address.
03-29-2012 03:09 PM
That would work if there weren't more servers than external IP's, I guess it is not possible then? Is there a similar product that can do this with as many ports? I don't even need multiple WAN ports as I can use the IP Aliasing.
03-30-2012 08:20 AM
Excellence,
Yes the SA500 device does support 1 to 1 nat rules... IP aliasing and then you set your ACL's accordingly.
Jasbryan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide