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

    After restarting, the Static IPv6 address can't be accessed for around a day.

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 578 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
      Snapdragon100
      last edited by

      In my PFSense setup, I've set up the WAN interface with a Static IPv6 address and a dynamic IPv4 address from my internet provider. I've also configured WireGuard on PFSense to access my home network remotely. Everything works well until I restart PFSense or lose internet connection from my provider. After such events, my Static IPv6 address can't be accessed from the internet for about a day. After 24 hours, the connection comes back. During this time, my home network works fine, and I can use the internet normally. I suspect the issue might be with how my ISP routes IPv6. Has anyone else experienced this or have any other ideas about what could be causing it?

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

        @Snapdragon100 If you have an ISP router/modem I’d try restarting that to see if it recovers.

        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
        • S
          Snapdragon100
          last edited by

          @SteveITS I have tried restarting the Modem and it didn't solved the problem.

          1 Reply Last reply Reply Quote 0
          • S
            Snapdragon100
            last edited by

            SOLVED:

            The issue has been solved by checking "Do not wait for a RA" option in WAN interface.

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