RV082 Dual-wans and 1-to-1 NAT

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by klubar, Jun 29, 2006.

  1. klubar

    klubar LI Guru Member

    A have a RV082 (firmware 1.3.2) with two internet connections. The RV082 is configured to for load sharing. WAN1 is static IP in the range of - 94, WAN2 is a static IP - 54.

    My internal LAN range is

    One-to-one NAT is set up for> and>

    From the outside the 1-to-1 NATing works on both WAN1 and WAN2. Traffic coming in on is correctly sent to .42 and traffic coming in on is sent to .43.

    Outbound traffic from .43 goes out on address (which is correct). The problem is that outbound traffic from .42 goes out on (which is incorrect--it sould be .54). is the first address in the IP range for WAN2.

    It's not a problem with the WAN connections, as I've swapped WAN1 and WAN2 cables and addresses and the problem moves.

    Has anyone else seen this problem, and is there a solution?
  2. Toxic

    Toxic Administrator Staff Member

    could you possibly setup a rule for routing the .43 perhaps? this is probably a bug in the firmware on WAN2 I'll forward this to someone at linksys.
  3. klubar

    klubar LI Guru Member

    I don't quite understand what you mean by "setting up a rule". The router is correctly handling .43 (out on

    Neither .43 or .42 have any firewall rules. The reason it's important to have the 1-to-1 NATs working correctly is that the box at .43 and .42 is a e-mail server with 2 LAN cards. The email going out from .42 (should be now doesn't match any of our MX records. This is causing some email servers to reject our mail.

  4. Toxic

    Toxic Administrator Staff Member

    sorry i meant .42 since the router is NOT handling this correctly. it is a suggestion only. you did want help yes?

    could you explain however why do you need outgoing traffic to go through specific WAN port.
  5. klubar

    klubar LI Guru Member

    Appreciate your help.... the reason traffic needs to go out over a particular port is the Comcast does a reverse IP lookup on IP address of email sent to it. If the real IP address of the incoming email does not match a reverse DNS lookup for sender's domain they reject it as spam.

    For example... if the mail coming into comcast is from IP and claims to be from joe@emiboston.com, Comcast does a lookup on and checks to make sure that IP is "owned by" emiboston.com. If not they reject the email as spam.

    We've got around the problem by adding reverse DNS records for all our addresses. But I was a little perplexed at the beginning when our email was sometimes bouncing when it went out over WAN2.

    I was generally unsuccessful in reporting this to linksys.
  6. Toxic

    Toxic Administrator Staff Member

    thanks for the explaination i'll pass this on to the powers that be since the they are fixing issues with the RV series atm
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice