We have Point to point T1 environment where 3 additional WAN sites get internet access through our RV042. When we setup load balancing we have problems with https traffic, so we setup protocol binding for https and everything worked great from the local LAN. When trying to access https content from the remote LAN across the WAN the sites failed and I see no option to add additional subnets to the protocol binding.
Is there a command line feature that supports adding additional subnets for protocol binding or is the local LAN the only option?
You mean from command line? In the web GUI by default there is only the local LAN available for protocol binding and I was wondering if there was a way in the command line for adding additional subnets to the protocol binding. The only answer I have found from Cisco was from 2007 when they stated that protocol binding and static nat were only supported with the local LAN and they may support it in the future. That post was from 2007, so I wasnt sure if there was any progress.
could your remote traffic be binded if you routed the remote site traffic?
I am simply looking for an answer from Cisco if this is possible. All internet traffic is currently bieng routed to the RV042 and it works perfectly. As I stated in my original post, there is a limitation in the firmware GUI that limits the protocol binding to the local LAN. We cannot enable load balancing because it will only allow the https binding on the local LAN interface. We dont need a VPN tunnel to duplicate what is already working. Also we will still be running into the same problem as there will still be remote LAN subnets to contend with.
I am having trouble opening a case with support. Is there anyway to get a link to this workaround? The support site is so disjointed now that its not easy to find where to open a case for a low end device like this.
The Linksys RV042 GUI does have a limitation in configuring a protocol binding rule for the non-default LAN subnet. The limitation has been lifted in the Cisco branded RV042. However the engineering is working on a workaround using command line. Please open a case with the Support Center to receive the workaround instruction.