Fabrice DURAND <fdurand@...> writes: > > > Hello, > so here the secret of the HA. > In pf.conf on the management interface it should be something like > that: > [interface eth0] > ip=192.168.0.1 > type=management,high-availability > mask=255.255.255.0 > vip=192.168.0.3 > Regards > Fabrice > Le 2014-01-03 03:34, Nicola Canepa a écrit : >
Thank you for the secret. I will give this a try. I currently have DRBD running on one node with packetfence up and running on 4.1.0. I already installed corosync and pacemaker and i took an image of the computer so I can roll back. I was going to reimage my other computer using the image from the first computer and update the IP's so they don't conflict. > Could it be a firewall issue? > Maybe the PF rules interfere with the cluster. > > Maybe adding the required ACLs to > /usr/local/pf/etc/iptables.conf may do the trick. > I muck about with iptables and since i didn't know well how to make it work with the labeled action fields, I put then into INPUT. This seemed to help. So once i get it working, i will try to muck about with iptables some more to secure things properly. > I would allow all the traffic between the cluster IPs, plus > the broadcast addresses (224.0.0.0/4 I think). I did forget about the broadcast addrs. Thanks. > > Nicola > > ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
