I saw the FAQ but wasn't really sure if I understood it correctly or if it was wrong : it seemed strange to me :-) .

I've installed rules on the CARP interface to accept anything from anyone (like all interfaces at the moment), but the message is the same. I read the first tutorial you indicated and followed it step by step. There are a few grey areas (like how to set up the CARP page). I could not load the second tutorial though...Why is it that I can't ever load the tutorials in that .ht format ?

Joseph


Holger Bauer wrote:
Looks like your machines can't talk to each other and don't see each
others heartbeats. The ARP message is normal and can be ignored (it's in
the faq). Additionally check
http://doc.pfsense.org/index.php/Setting_up_CARP_with_pfSense and
http://pfsense.org/mirror.php?section=tutorials/carp/carp-cluster-new.ht
m

Holger
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 16, 2007 7:28 AM
To: [email protected]
Subject: [pfSense Support] CARP problem or not?

Hi

I've set up 2 PFSENSE machines with CARP and it seems to work well
although I find the following messages in the system log of the BACKUP
machine :

"kernel : arp_rtrequest : bad gateway 111.222.333.444 (!AF_LINK)"

"A communications error occurred when attempting XMLRPC sync with
111.222.333.111"

Also, browsing the CARP status page on both machines shows that they are
both MASTER.

It seems that the sincronization process is not succeeding and that the
Backup system has become active. What can I do to correct/debug the
situation?

Regards

Joe




---------------------------------------------------------------------
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]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to