Problem with CARP



  • I have configured CARP for pfSense redundancy on two locations and they work OK (pfS 1.2). On this 2 locations setup is simple without VLAN's.
    Now I have need for VLAN's + CARP. On this location pfS is working for 1 year with some minor (and some not so minor) problems. Now customer is asking for redundancy. I added another server (intel server 1U 4 eth ports) and folowed same procedure as I have before but all ended messed up. I have been forced to go back to single pfS system.

    Setup is such that I have one WAN interface, one internal with 9 VLAN's, one DMZ int bridged to WAN and one int for SYNC. When I deploy CARP, bridge traffic is interrupted, some addresses are unreachable (in DMZ) and sometime DMZ is totally dead. Rules sync doesn't work at all.

    This are some messages from syslog:

    kernel: arp_rtrequest: bad gateway 172.16.84.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp9: INIT -> MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 172.16.28.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp8: INIT -> MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 172.16.24.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp7: INIT rp MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 172.16.20.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp6: INIT -> MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 1 2.16.16.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp5: INIT -> MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 172.16.12.254 (!AF_LINK)
    May 7 19:30:20  kernel: carp4: INIT -> MASTER (preempting)
    May 7 19:30:20  kernel: arp_rtrequest: bad gateway 172.16.8.254 (!AF_LINK)

    Please advice.

    Sasa


Log in to reply