1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RV016 and webmail not working

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by alousteau, Sep 28, 2005.

  1. alousteau

    alousteau Network Guru Member

    Here is what we got!!!

    two dsl connections, with the router connecting via ppoe.

    any time we try to connecto to webmail, no matter what company or service we get that the session has timed out. the only time it will work is when only one modem is plugged into the router.

    What I think is happening is that to initial connection is being made on one modem, and we are getting moved to the other modem for the rest of the connections?????

    How can I make this work, and still have the auto load balance work???? I am sure I can assign static ips to the clients and designate them to use only one modem, but we have roaming users and it could lead to our heavest users ending up on the same modem, we wanted the r 016 because of the auto load balance!!!

    I have upgraded to the latest firmware and been on the phone with Linksys and have gotten nowhere fast!!!!

  2. net_eng

    net_eng Network Guru Member

    I have a question as I cant seem to find the answer in your text. Are all your clients behind the RV16? Are remote clients whatever using quickvpn to the RV16 then going out to webmail? Or is your webmail behind your RV16 and you want to access it?

    If you are all behind the RV16(physical or quickvpn/IPSEC) then you will probably have to use protocol binding. Usually load balance is fine with connections that are one port to one port. When you start having things like webmail(connect to 443 then it spawns a billion windows, which may run on different ports) you can run into problems as the load balance may run them through the other port.

    Try forcing them with protocol binding to go to one WAN port for the webmail. Basically the easiest way is to force all connections through one WAN port of your choosing for the destination webmail machine.

    Now if you are just looking for the RV16 to load balance and have half your users go through one wan port and the other half through the other, that is more difficult as it uses the following.

    Here is the text from linksys support site:


    Load Balance

    Load Balancing can be utilized when both Internet ports are connected to two Internets connections and used at the same time. Using both the primary and secondary interfaces, load balancing enhances maximum bandwidth efficiency and reduces unnecessary waiting time. If one of the connections is lost, the remaining link will provide the network with Internet traffic until the other link is up again – similar to Smart Link Backup.

    The Load Balance feature is ideal when the two Internet ports are connected to two different broadband Internet Service Provider (ISP) connections that have an equivalent bandwidth rating.

    Intelligent Balancer

    The Intelligent Balancer feature is automatically activated when Load Balance mode is selected. The Load Balancer will dispatch IP session packets based on the upstream bandwidth ratio of the two Internet connections. The upstream bandwidth monitoring is set to determine the ratio of outbound load balancing.

    A special “round robin†algorithm is used to enhance the automatic Load Balance calculation. Round robin works on a rotating basis: when a server IP address is handed out, it moves to the back of the list. This step loops repeatedly as the next server IP address is received.

    Bandwidth Ratio (weight equation)

    The weight of equalization is calculated from the ratio of WAN1 upstream bandwidth and WAN2 upstream bandwidth. For example, if the rates are sets at 2M and 512K for WAN1 and WAN2, respectively, the ratio for the load balance will be 4:1. This means that sessions forwarded by WAN1 are four times the sessions of WAN2, but if WAN1’s load is in excess of over 60%, Intelligent Balancer will redirect the overflow to WAN2, avoiding traffic congestion.


    A session, defined by the Load Balance system, consists of the following fields in a TCP/UDP packet:

    Source IP Address
    Destination IP Address
    Type of Service (TOS)

    Packets with the same session (i.e., the same Source IP, Destination IP, and Type of Service) will be routed via the same interface. This avoids packets reaching their destination out of order, although port numbers are often used in conjunction with the Source and Destination IP addresses to determine the correct route of a packet.

    If port numbers were used primarily, sessions could be directed through different interfaces, resulting in incorrect packet routing. Certain applications generate packets with several different port numbers, so both IP addresses and the Type of Service must be used for session identification.

    For ICMP packets, sessions are not used, so each packet can be forwarded by either interface, packet by packet.

    Dispatch Rules

    In Intelligent Balancer mode, the Load Balance system will dispatch IP packets based on the following rules:

    The same sessions are forwarded (routed) to the same interface.
    Different sessions are dispatched to different interfaces based on configured bandwidth ratios.
    Sessions are dispatched based on a static bandwidth (upstream and downstream) utilization threshold of 60% with the following routing sub-rules:

    If the bandwidth utilizations of both WAN1 and WAN2 are under 60% (i.e., both downstream and upstream utilizations are less than 60%), a new session will be routed based on rule (1) and (2) normally.
    If the bandwidth utilizations of WAN1 or WAN 2 is over 60% (i.e., either downstream or upstream utilizations are higher than 60%), a new session will be routed to the WAN which has the higher available bandwidth.
    If the bandwidth utilizations of WAN1 and WAN2 are over 60%, (i.e., both downstream and upstream utilizations are higher than 60%), a new session will be routed to the WAN which has the higher available bandwidth.
  3. alousteau

    alousteau Network Guru Member

    All the computers are behind the rv016, and are trying to connect to the webmail servers of their ISPs to check their email at home. I was going to bind all conncections to the web mail servers to one WAN interface, but I couldn't figure out how.
  4. net_eng

    net_eng Network Guru Member

    Since it appears that the webmail servers are on different IP's, its best to just bind all https or http traffic to go through one WAN port. This way the port the http(s) traffic goes out on, it will come back on that port. That will mean all http or https traffic will go through that port and other traffic will randomly be sent out on either port unless you bind it as well.

    I downloaded the RV16 manual and it doesnt have protocol binding that the RV082 and RV042 has. Though it may be included in the newest firmware. It would show up under

    System Management-> multi-lan->load balance

    If it doesnt, then you can't bind protocols(odd why they would leave that on the RV16 and not the others).

    If you see protocol binding, then its as easy as selecting the http or https service and force it to go out one of the WAN ports(from all private IP's to the default 0(anywhere)).

    If you dont see it, ask Linksys to include it.

    Let us know either way.
  5. alousteau

    alousteau Network Guru Member

    I bound https and that didn't work, but if I bind http doesn't that mean all http traffic would go through that one wan port? What about the other 2 modems. They would only be used for other protocols. 90 % of the traffic is regular old web surfing, so that would put 90% of the traffic on that one modem. We wanted the router to auto balance that traffic over the three modems. Now I will have one jammed up connection and two basically doing nothing.
  6. DigiGuru

    DigiGuru Network Guru Member

    You can use a filter based on destination, so if you can find the destination IPs of the webmail server(s), you will be able to bind them.

    I definately recommend passing all HTTPS traffic over 1 line, as we've had all sorts of issues with that otherwise :)

    It is an unfortunate side effect of load balancing, but it's never QUITE that intelligent :)

    On the plus side, splitting a download into 2-4 parts, I can get about 440KB/s download speeds! :D (not bad off 2 2MB lines!)

Share This Page