Cluster / Failover - doesn't work correctly
-
Hello,
Problem 1
If I delete an alias on master firewall then the alias will not deleted on backup firewall. The sync doesn't work correctly.
Tested with
PFSense 1.2.1 Beta Snapshot 20080729-0437
PFSense 1.2 ReleaseProblem 2
If I add an CARP IP on master firewall the IP will synced to backup firewall. On backup firewall is an manually "stop" and "start" of CARP needed.
If I don't manually restart CARP on backup firewall then the backup firewall doesn't set the new CARP IP in backup mode and doesn't work for this
IP.
… see attached imageTested with
PFSense 1.2.1 Beta Snapshot 20080729-0437
PFSense 1.2 Release -
It ABSOLUTELY works on 1.2. I am leaning toward PEBKC problems.
-
It doesn't work !!! I've tested today with latest snapshot.
-
1.2 =/= 1.2.1
It definitly works on 1.2
I just set that up yesterday and had no issues. -
1.2_RELEASE:
if you can't get it going on 1.2 you've probably got a config problem. 1.2.1 RC1: ~~~~~~~ About a week ago I tried to get the sync going here and gave up. The master of the pair would show that the message that it had failed to login as admin on the slave device. As far as I could tell I had set everything as I would on a 1.2 pair. The rule to allow all on the sync interface was in place. This maybe a HTTPS login issue that was preventing the connection for sync. At that stage I could not create certificates (can we do that now?) so I copied the certificate/key from a working 1.2 onto both of the 1.2.1 firewalls. No go, I gave up. So has anybody got the 1.2.1 rc1 synching happily? If so I'll have another go.
-
heres my build
1.2.1-RC1
built on Sun Aug 17 23:30:22 EDT 2008here is the error i get:
php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.
i am sure i typed in the right password for carp and the username was left default (admin)
-
1.2.1-RC1
built on Sun Aug 17 23:30:22 EDT 2008
…
php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.That's what I was getting. My message was "https://…:443" but I guess if you've not configured a certificate it will try port 80.
Multiple password tries etc... No joy. -
I have opened a ticket on 2008/08/07…..
http://cvstrac.pfsense.com/tktview?tn=1797,33