I am having the same problem, my interfaces go up and down 10 - 15 times per day. I now have the monitor IPs set to my cable modem configuration address and have no more problems with the lines going up and down, except if a line actually goes down. I assume I would have to unplug the Ethernet connector from the modem to get it marked as down. However, I have not yet seen one line go down by itself as both my connections go through the same ISP. I do have a problem with duplicate MAC addresses. I don't know how Comcast sets their hardware up, but I have two very different IP addresses and gateways for the two accounts, however the MAC addresses of the gateways shown in the ARP status page are the same. I think that is causing me some some problems. If that does cause problems, is there a way to fix it from my end? Thanks for such a stable and reliable solution (as compared to my old Netgear router).
Bob Smith On 1/24/07, Holger Bauer <[EMAIL PROTECTED]> wrote:
This is not possible atm. It's hardcoded in the slbd binary but we are discussing to either lower sensitivity or make it configurable. I would prefer configurable to be able to include links with higher delay for example (like wireless links) or links where provider do some shaping to give pings low priority. Holger > -----Original Message----- > From: Nelu Sofrone [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 2:36 PM > To: support@pfsense.com > Subject: Re: [pfSense Support] Carp failover & ISP Load balance > > Thank you for replay. > > My issue with loadbalancing is only from one of ISP and I've > tried some different monitor IP with no change. Can I make > the loadbalancing test less sensitive by increasing the ping > time out or number of pings? > > Nelu > > > ----- Original Message ----- > From: "Holger Bauer" <[EMAIL PROTECTED]> > To: <support@pfsense.com> > Sent: Wednesday, January 24, 2007 9:41 AM > Subject: RE: [pfSense Support] Carp failover & ISP Load balance > > > What you see is caused by unreliable monitor Ips (they don't answer to > pings all the time). Try to use different monitor IP for your pools. > Loadbalancing is stable. I'm using it at several locations without > issues. However with the latest snapshots a new feature > (failover pools) > was added and the pool creation mechanism was changed to make > configuration easier. This *should* work but is not yet as much in > detail tested like the 1.0.1 balancing code. I don'T have > issues with it > at our office though where I now run failoverpools and > loadbalancingpools. I also know there are some installations out there > using CARP and pools successfully. Make sure your Outbound > nat settings > are correct. > > Holger > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
