Loadbalance/failover: get "Page Not Found" occasionally



  • Hello,

    I just setup pfSense 1.2-RC2 for a Client who has two WAN connections: ADSL and cable.

    I set everything up according to the wiki documentation at <http: olddoc.pfsense.org="" index.php="" multiwanversion1.2="">The good news is that the failover works nicely.

    The problem appears to be the load balancing: ever since this has been put in place several users have reported that at random times they will get a "Page Not Found" error when clicking on a link but then hit refresh or the back button and hit the link again and the page comes up.

    It almost sounds as though the page initially comes up over one connection but subsequently clicking on links takes it over the other one, thus messing up the routing.  I have also been able to experience this as well with some random web browsing as well, so I know it's not something they are hallucinating :-)  I have also made sure that both connections are up at the time, and they are.

    I have checked and made sure that I have "sticky connections" enabled (it already was), so I am not really sure what else could be at play here?

    Any other suggestions or explanations are welcome.  Please let me know if you require any further information on my part.</http:>



  • Bump, I'm having exactly this problem.
    Any ideas?



  • sounds like a DNS problem. Make sure that you have a DNS server from each ISP. If you do not have these as monitor IPs then you need to have static routes for them.



  • Try using opendns, it did help me a bit.
    But from my own experience it seems to be the downfall of using sticky connections.



  • I had the same problem until I set up static routes. Create a route for the DNS servers of each ISP, to direct all traffic destined to ISP_DNS1 through that ISPs WAN connection.



  • @tacfit:

    I had the same problem until I set up static routes. Create a route for the DNS servers of each ISP, to direct all traffic destined to ISP_DNS1 through that ISPs WAN connection.

    OK, just so I get this correct, say I have the following DNS servers defined, one from each ISP.  Let's say the info from ISP1 is as follows:

    Interface Assigned: WAN
      Gateway: 192.168.45.1
      DNS1: 192.168.1.234

    Would my static route for the DNS server for ISP1 look like this:

    Interface:  WAN
      Destination network: 192.168.1.234 /32
      Gateway: 192.168.45.1

    And for ISP2, I would use OPT1, ISP2-assigned gateway, etc.

    Is this correct?  TIA.

    -SilkBC



  • ^ Almost perfect. The interface you select needs to be the interface the rule will apply to (the interface the traffic is originating on). So you can change it to LAN, or whatever other LANs you're using.

    In my case, this problem only manifested itsself on my second LAN (not my default LAN) so I created two of these rules, both for the "Public" interface. (In my case I was using an interface called Public).


Log in to reply