{"id":819,"date":"2015-02-05T01:34:28","date_gmt":"2015-02-05T01:34:28","guid":{"rendered":"http:\/\/www.ber10thal.com\/blog\/?p=819"},"modified":"2015-02-05T16:15:26","modified_gmt":"2015-02-05T16:15:26","slug":"multiple-wan-ip-address-vlans-one-to-one-nat-and-port-forwarding","status":"publish","type":"post","link":"https:\/\/ber10thal.com\/blog\/multiple-wan-ip-address-vlans-one-to-one-nat-and-port-forwarding\/","title":{"rendered":"Multiple WAN IP address VLANS – One to One NAT and Port forwarding"},"content":{"rendered":"

How to setup a Cisco router with multiple WAN IP address and forward ports to multiple VLANS.<\/strong><\/p>\n

The router I used was the Cisco RV220W. I believe other Cisco routers have this functionality, but I have not tested them. I suspect if it’s a Cisco router that has One to One NAT it can do this. The problem is in one to one nat you can only add one rule per WAN IP. It gives you three choices; forward all ports, forward a single port or sequential port range. For example you could not forward port 80 and 443. You would have to forward either 80 through 443, or forward all ports from a single WAN to Lan or Vlan. Here is how to forward multiple ports for each\u00a0wan to a Lan or Vlan.<\/p>\n

First I setup One to One Nat. Click on any image for a larger view.<\/p>\n

\"one-to-one-nat\"<\/a><\/p>\n

This is where I added the rules. For this configuration to work I needed one to one nat. Simply adding port forwarding or firewall rules would not forward multiple WAN IP’s to multiple VLAN’s. <\/strong>For each WAN IP you can only add one rule, and\u00a0<\/strong>once a single rule for one to one NAT is established a firewall rule with port forwarding starts working.<\/p>\n

Note: you can\u00a0forward all internet traffic to any internal VLAN or IP, but for security reasons I didn’t want all ports forwarding to a single internal LAN.<\/p>\n

\"one-to-one-nat-detail\"<\/a><\/p>\n

This is the detailed view of the rule. The range length specifies that a single WAN IP is used. For example if I had selected 2 for Range Length. This rule would have applied for two IP address: xxx.xxx.122.147 and xxx.xxx.122.148.<\/p>\n

\"firewall_access_rules\"<\/a><\/p>\n

I added a firewall \/ port forwarding rule, the router was smart enough to add the rule to the list of port that were forwarded.<\/p>\n

\"firewall_access_rules_detail\"<\/a><\/p>\n

The OpenVPN is defined as a single port or a port range. I can’t remember, but either way it should work. The part at the bottom is important. Sent to local server (DNAT IP) destination nat. I added my VLAN IP here. I checked Use other WAN Destination IP and added the WAN IP that I wanted to forward the OpenVPN port.<\/p>\n

\"port_forwarding\"<\/a><\/p>\n

Once I added the firewall rule it showed up in the port forwarding section.<\/p>\n

\"port_forwarding_detail\"<\/a><\/p>\n

Here is the details of the port forwarding rule. I guess it’s important to add the rule in the firewall section because it give you the ability to specify the VLAN and WAN IP address.<\/p>\n

Remember:<\/strong>\u00a0If you want to forward multiple ports on different external WAN’s to the internal network, VLAN or otherwise, you only need to add a single 1 to 1 nat rule. Do this in the one to one rule, (NATing a single port) then add your firewall \/ port forwarding rules to add additional forwarded ports under the Firewall setting.<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

How to setup a Cisco router with multiple WAN IP address and forward ports to multiple VLANS. The router I used was the Cisco RV220W. I believe other Cisco routers have this functionality, but I have not tested them. I suspect if it’s a Cisco router that has One to One NAT it can do … Continue reading Multiple WAN IP address VLANS – One to One NAT and Port forwarding<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-819","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/posts\/819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/comments?post=819"}],"version-history":[{"count":15,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions"}],"predecessor-version":[{"id":845,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions\/845"}],"wp:attachment":[{"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/media?parent=819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/categories?post=819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ber10thal.com\/blog\/wp-json\/wp\/v2\/tags?post=819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}