Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    CARP Vlans doesn't work

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    2 Posts 2 Posters 448 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      bisssane
      last edited by

      I have a VLAN, its network address is: 192.168.1.0
      I have 2 pfsense to do the FailOver
      the vlan address on the Pfsense 1: 192.168.1.1
      the vlan address on the Pfsense 2: 192.168.1.2
      the virtual address: 192.168.1.3
      I also enabled DHCP

      when I'm on my machine, I do Ipconfig, I have the default getway: 192.168.1.1. I think the gateway must be 192.168.1.3 ?? (the virtual IP address)

      to test if my failover works, I deactivated the interface of the vlan on the pfsense master. it must switch to the 2 ieme pfsense, but it did not work

      I disabled the DHCP and I entered my address manually, I put 192.168.1.3 as gateway but it does not work as well

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        CARP VLANs work fine.

        Are the CARP VIPs MASTER and BACKUP on the primary and secondary respectively (Status > CARP)?

        Did you instruct your DHCP server to give the CARP VIP as the default gateway in its leases?

        but it does not work as well

        What does "does not work" mean?

        https://www.netgate.com/docs/pfsense/routing/connectivity-troubleshooting.html

        https://www.netgate.com/docs/pfsense/highavailability/troubleshooting-high-availability-clusters.html

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.