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

    CARP IPv6 with routed network

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    2 Posts 2 Posters 2.0k Views
    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.
    • S
      skid9000
      last edited by

      Hello there,

      I have some difficulties getting IPv6 at work working properly so i'm seeking for advice.

      We have two physical pfsense (2.6.0) box with for each one a physical WAN interface, a physical LAN interface (+ vlans), and a physical SYNC interface for pfsync and XMLRPC.

      I have a /64 for my wan interface and a /56 that is routed to the first address of that /64

      So i configured my first box with ::2 and my second with ::3 and then set up CARP on ::1

      I cut my /56 in many /64 for each VLAN with the same topology, ::2 for box 1, ::3 for box 2, ::1 for CARP.

      However, i had trouble making it working : i started with a first vlan, didn't work, tried to troubleshoot and i don't know what i did but it worked... Until i configured another VLAN.

      I tried to remove that second VLAN, still dosen't work, it seems that there is an issue with CARP, but on pfSense GUI, everything shows it's fine when it's not.

      WAN ::2 pings internet fine, WAN ::1 dosen't and LAN ::1 or LAN ::2 dosen't.

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @skid9000
        last edited by

        @skid9000 Perhaps some screenshots of the setup? Can you get it working without the VLANs and add those in after? I've not had occasion to set HA up with VLANs but have done so with aliases for other subnets on LAN.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

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