We already had this feature in earlier releases but dropped it due to not working correctly and machines crashing. Maybe things have changed a bit since we were running something between alpha and beta of freebsd these days. However, it's not considered a good solution even from the developers of CARP. I think the carp tutorial at pfsense.com even explains this option still as it was not updated after that item had gone.
Holger > -----Original Message----- > From: Robert Mortimer [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 05, 2006 11:14 AM > To: support@pfsense.com > Subject: RE: [pfSense Support] CARP Load balance > > > > On 8/25/06, Robert Mortimer > <[EMAIL PROTECTED]> wrote: > > > > You'll want to reboot after making that change. This > naturally isn't > > > > supported, but if you understand how carp balancing > works, it's still > > > > configurable. > > > > > > This is the case outlined in the Docs > > > > Yeah, see, the problem is that most people would (and do) > configure it > > w/out understanding what it does and then complain that > they randomly > > have packet or connection loss. Most people would and have tried to > > use it to load balance FIREWALLS, not network connections. If you > > have any suggestions on how to reenable this w/out also making the > > support of it's incorrect usage a nightmare, we're all ears (hint: > > putting a description next to the checkbox won't cut it ;)) > > > > --Bill > > Had a further look at the docs. To load balance across 2 > machines requires > 2 pairs of carp interfaces each pair skewed to a different > box. Further > pfsense > hacking will be required to get this going > > From Man page ---------------------- > > In order to set up an ARP balanced virtual host, it is > necessary to con- > figure one virtual host for each physical host which would > respond to ARP > requests and thus handle the traffic. In the following > example, two vir- > tual hosts are configured on two hosts to provide balancing > and failover > for the IP address 192.168.1.10. > > First the carp interfaces on Host A are configured. The > advskew of 100 > on the second virtual host means that its advertisements will > be sent out > slightly less frequently. > > # ifconfig carp0 create > # ifconfig carp0 vhid 1 pass mekmitasdigoat 192.168.1.10 \ > netmask 255.255.255.0 > # ifconfig carp1 create > # ifconfig carp1 vhid 2 advskew 100 pass mekmitasdigoat \ > 192.168.1.10 netmask 255.255.255.0 > > The configuration for host B is identical, except the skew is > on virtual > host 1 rather than virtual host 2. > > # ifconfig carp0 create > # ifconfig carp0 vhid 1 advskew 100 pass mekmitasdigoat \ > 192.168.1.10 netmask 255.255.255.0 > # ifconfig carp1 create > # ifconfig carp1 vhid 2 pass mekmitasdigoat 192.168.1.10 \ > netmask 255.255.255.0 > > Finally, the ARP balancing feature must be enabled on both hosts: > > # sysctl net.inet.carp.arpbalance=1 > > ----------------------------- > > I will let you know how I get on > > Rob > > > --------------------------------------------------------------------- > 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]
