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

    Unstable ipv6

    Scheduled Pinned Locked Moved Routing and Multi WAN
    10 Posts 4 Posters 1.4k Views 4 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.
    • H Online
      helento1
      last edited by

      My operator provides both ipv4 and ipv6 adresses with dhcp, but ipv6 is often unstable with 20-30% packet loss. Can i use gateway monitor so it would disable ipv6 traffic and only use ipv4 when high packet loss happens?

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @helento1
        last edited by

        @helento1 said in Unstable ipv6:

        Can i use gateway monitor so it would disable ipv6 traffic and only use ipv4 when high packet loss happens?

        That's a pretty close description of the functionality of the gateway monitoring ๐Ÿ˜Š

        Here : System > Routing > Gateways > Edit, you could enter an IPv6 of your choice that does reply correctly en constantly to the ping requests.
        Have a look at what this button hides :

        42a48ae6-f19d-43f0-a06e-a278d5d164a4-image.png

        where you can set up : how much, after what delay, what type of packet etc etc.
        Normally, the default settings should work just fine.

        @helento1 said in Unstable ipv6:

        but ipv6 is often unstable with 20-30% packet loss

        IPv4 has still some years left, so no need to hit the panic button.
        But prepare yourself by locating this button, as an ISP should do IPv6 as it does IPv4.
        Not doing so means : example : You're paying Netflix but you can't receive their video's. My suggestion would be : stop paying ...

        Be ware that your upstream ISP link can transport at any time : IPv4 packets, or IPv6 packets (or some other type of packets).
        If some local IPv4 device is saturating the ISP IPv4 connection completely, then IPv4 and IPv6 ICMP packets, who have a lower priority (!), will start to drop => packet loss.
        Not your ISP fault.
        This time : solution : pay them more ?! (or stop charging your ISP connection ^^)

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        H 4 2 Replies Last reply Reply Quote 0
        • H Online
          helento1 @Gertjan
          last edited by

          @Gertjan

          Gateway monitor wont disable ipv6 like i would like. My windows computer behind firewall still uses ipv6 as default and its very laggy because of packet loss. While ipv4 works fine.

          gateway status.png
          ping.png

          1 Reply Last reply Reply Quote 0
          • U Offline
            Uglybrian
            last edited by

            Did you change your MTU (stock should be 1500) and are you allowing ICMPv6?

            H 1 Reply Last reply Reply Quote 0
            • H Online
              helento1 @Uglybrian
              last edited by

              @Uglybrian How does MTU or ICMPv6 help if i want to disable ipv6? Problem is on my operator side. Ipv6 can work many days just fine and then there goes something wrong on my operator side and its broken for few hours. I would like my firewall disable ipv6 when it goes broken and enable it again when its ok. Now i must manually go to wan adapter and disable ipv6 from there and then test again later if its ok and enable it. I would like to do this automatically.

              I have made a problem ticket to my operator and they are still investigating it, but havent find a solution.

              1 Reply Last reply Reply Quote 0
              • 4 Offline
                4920441 0 @Gertjan
                last edited by

                @Gertjan

                sorry... but why want you switch from ipv6 to ipv4 gateway and vice versa in case any of them occur packet loss? Those are two totaly different protocols and it does not make sense at all to use ipv4 to ipv6 failover whatsoever.....

                GertjanG H 2 Replies Last reply Reply Quote 0
                • GertjanG Offline
                  Gertjan @4920441 0
                  last edited by

                  @4920441-0

                  Me ?
                  Not me ... ^^

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  1 Reply Last reply Reply Quote 0
                  • H Online
                    helento1 @4920441 0
                    last edited by

                    @4920441-0

                    I dont want to switch gateways. I would like ipv4 gw be active all time and ipv6 gw to shut down when my operator has problems and high packet loss. Now ipv6 gw stays online while packet loss is high and ping response time 5000ms.

                    GertjanG 1 Reply Last reply Reply Quote 0
                    • GertjanG Offline
                      Gertjan @helento1
                      last edited by

                      @helento1 said in Unstable ipv6:

                      I would like ipv4 gw be active all time and ipv6 gw to shut down when my operator has problems and high packet loss

                      Every 'modern' OS, IPv4 and IPv6 capable, will use IPv6 if it is available.
                      Available means : the OS can open a UDP or TCP stream to the destination IP.
                      If the connection fails, it's the application that should handle the error, and retry several times.
                      The OS, if it is using IPv6, will introduce a gadget : if IPv6 fails, it will auto fall back to IPv4.
                      This process happens nearly, if not entirely, invisible for the end user.

                      pfSense, will, if the monitoring detects "no more pings over IPv6" will reset the IPv6 gateway. LAN connected devices won't be aware of this, but the will notice that open IPv6 connections will drop.
                      These connections, as stated above, will get re opened - as long is IPv4 is working.

                      @helento1 said in Unstable ipv6:

                      Now ipv6 gw stays online while packet loss is high and ping response time 5000ms.

                      Go here : System > Routing > Gateways > Edit, on the bottom of the page click on :

                      8e67c306-2e78-4b14-8b76-c499586ee4f0-image.png

                      and there you can fine control the monitoring 'ping' settings.

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      H 1 Reply Last reply Reply Quote 0
                      • H Online
                        helento1 @Gertjan
                        last edited by

                        @Gertjan said in Unstable ipv6:

                        @helento1 said in Unstable ipv6:

                        I would like ipv4 gw be active all time and ipv6 gw to shut down when my operator has problems and high packet loss

                        Every 'modern' OS, IPv4 and IPv6 capable, will use IPv6 if it is available.
                        Available means : the OS can open a UDP or TCP stream to the destination IP.
                        If the connection fails, it's the application that should handle the error, and retry several times.
                        The OS, if it is using IPv6, will introduce a gadget : if IPv6 fails, it will auto fall back to IPv4.
                        This process happens nearly, if not entirely, invisible for the end user.

                        There is my problem ipv6 is available, but with high packet loss 20-30%. My modern operating systems wont start using ipv4 when ipv6 still works. If packet loss would be 100% they would start using ipv4. This would happen ip pfsense could disable ipv6 gw automatically.

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