Multiwan load balancing and monitor IP
-
i just configured multiwan with 3 links we have at campus . I somehow used public DNS servers of opendns as monitor IP. Out of 3 connections i had one disconnected but still status page showed all 3 as online. I didn't create any static route to any monitor IP, is this the reason pfsense showed all interfaces online ?? Also in the given scenario, accessing internet through pfsense became ridiculously slow ( tryin to push conn from dead link ?? ) . Also from a client machine when i tried to do speedtest.net, it doesn't work.. :( .
Bottom line: Is it important to have a static route to multi wan load balance monitor ip's for each link ?
-
Bottom line: Is it important to have a static route to multi wan load balance monitor ip's for each link ?
Yes.
Also do not use the OpenDNS servers as monitor IP.
Find out (with traceroutes on each link) what the IPs of the routers of the next hops are.
Use these IPs as monitor. -
GruensFroeschl's advice is technically correct but perhaps better to monitor IPs that are outside of your ISP. That way you (hopefully) also catch if your ISP has routing issues.
-
well it took me some time to figure this out since documentation doesn't clearly mentions static route part and assume that people will use gateway as monitor ip ( i will try to change the wiki page ) . Other than that pfsense is working very well in our college campus with 3 x 2 Mbps load balanced :) .
-
Which static routes are you talking about now?
I mean the static route for the DNS servers for each link.
This is described in this howto: http://doc.pfsense.org/index.php/MultiWanVersion1.2#Setting_up_DNS_for_Load_BalancingYou dont need a static route for the monitor IP: Such a static route is added automatically behind the scene.
