Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    After upgrade to 26.03, IPv6 VIPS do not work on WireGuard interfaces

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 302 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.
    • C Offline
      ChrisJenk
      last edited by

      I just upgraded my NetGate 6100 to 26.03 from 25.11. The good news is that, as described in the release notes, 26.03 fixes the issue introduced in 25.11 that broke IPv6 VIPs on PPPoE interfaces, especially those using the if_pppoe driver.

      The bad news is that 26.03 now seems to have broken IPV6 VIPs on WireGuard interfaces.

      I have one WireGuard tunnel on which I have created an IPv6 VIP. This was fine in 25.11 and earlier but now the VIP does not get created and the log shows:

      Apr 8 09:53:49 php_wg 97182 NOTICE The command '/sbin/ifconfig tun_wg1 inet6 '2a02:390:62fb:dd::1' -alias' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address'
      

      Executing the same ifconfig command manually also faisl in the same way.

      Can I have a fix or patch for this ASAP please?

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        Hmm, interesting. Not sure what could have changed to cause that. Let me replicate....

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          That's an IPAlias VIP I assume?

          Not able to replicate that here dircetly. Adding IPAlias VIPs in the GUI works as expected. As does the CLI:

          [26.03-RELEASE][admin@5100.stevew.lan]/root: /sbin/ifconfig tun_wg0 inet6 2a02:390:62fb:dd::3 alias
          [26.03-RELEASE][admin@5100.stevew.lan]/root: ifconfig tun_wg0
          tun_wg0: flags=10080c1<UP,RUNNING,NOARP,MULTICAST,LOWER_UP> metric 0 mtu 1500
          	description: WG0
          	options=80000<LINKSTATE>
          	inet 10.110.20.10 netmask 0xffffffc0
          	inet6 2a02:390:62fb:dd::1 prefixlen 64
          	inet6 2a02:390:62fb:dd::2 prefixlen 64
          	inet6 2a02:390:62fb:dd::3 prefixlen 64
          	groups: wg WireGuard
          	nd6 options=101<PERFORMNUD,NO_DAD>
          

          The error you're seeing there looks like it's trying to remove an alias that doesn't exist yet.

          What IPv6 IPs do you have on that?

          C 1 Reply Last reply Reply Quote 0
          • C Offline
            ChrisJenk @stephenw10
            last edited by

            @stephenw10 Okay, I tried again and yes it does work. The issue with the '-alias' is that it gets executed by the system after the interface has been taken down. That doesn't seem good. Probably the same issue as in my other post about the 'arp' related stuff.

            1 Reply Last reply Reply Quote 0
            • stephenw10S Offline
              stephenw10 Netgate Administrator
              last edited by

              Yeah that seems like a bug though it's probably just ugly since all the interface values are removed when it's set down anyway.

              So the VIPs are actually working correctly in 26.03?

              C 1 Reply Last reply Reply Quote 0
              • C Offline
                ChrisJenk @stephenw10
                last edited by

                @stephenw10 yes. Not sure why they didn't seem to be previously. Probably a mistake on my part, sorry.

                1 Reply Last reply Reply Quote 1
                • First post
                  Last post
                Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                Privacy Policy · Cookie Policy