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

    Failover и сброс состояний

    Scheduled Pinned Locked Moved Russian
    15 Posts 3 Posters 3.5k 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.
    • P
      paran0id
      last edited by

      Нет. Поставить?

      1 Reply Last reply Reply Quote 0
      • P
        paran0id
        last edited by

        Поставил. Проблема не исчезла.

        Уточняю - состояния "залипают", когда происходит переключение обратно на основной канал.
        Если отключить оба канала, а потом  включить - не залипают.

        1 Reply Last reply Reply Quote 0
        • werterW
          werter
          last edited by

          http://forum.pfsense.org/index.php?topic=48030.0

          It will kill states for a down gateway by default, but it may depend on how you're monitoring ISP2 in System > Routing. If the monitor IP is actually local and not something on the other end, it may never appear to be down. Or if you have monitoring disabled it can't detect it.

          Also on gateway groups, the trigger should almost always be "packet loss or high latency" or it won't kick in.

          Make sure under System > Advanced, on the Misc tab at the bottom, that the state killing option is not disabled.

          1 Reply Last reply Reply Quote 0
          • P
            paran0id
            last edited by

            It will kill states for a down gateway by default, but it may depend on how you're monitoring ISP2 in System > Routing. If the monitor IP is actually local and not something on the other end, it may never appear to be down. Or if you have monitoring disabled it can't detect it.

            Мониторится внешний адрес, мониторинг успешно распознаёт проблемы на канале.

            Also on gateway groups, the trigger should almost always be "packet loss or high latency" or it won't kick in.

            Так и сделано.

            Make sure under System > Advanced, on the Misc tab at the bottom, that the state killing option is not disabled.

            Галочка State Killing on Gateway Failure снята.

            The monitoring process will flush states for a gateway that goes down if this box is not checked. Check this box to disable this behavior.

            То есть, опция убивания состояний не выключена.

            1 Reply Last reply Reply Quote 0
            • P
              paran0id
              last edited by

              https://doc.pfsense.org/index.php/Upgrade_Guide

              State Killing on Gateway Failure" now kills ALL states when a gateway has been detected as down, not just states on the failing WAN. This is done because otherwise the LAN-side states were not killed before, and thus some connections would be in limbo, especially SIP.

              именно эта проблема

              1 Reply Last reply Reply Quote 0
              • werterW
                werter
                last edited by

                @paran0id:

                https://doc.pfsense.org/index.php/Upgrade_Guide

                State Killing on Gateway Failure" now kills ALL states when a gateway has been detected as down, not just states on the failing WAN. This is done because otherwise the LAN-side states were not killed before, and thus some connections would be in limbo, especially SIP.

                именно эта проблема

                Ну так это не проблема - это фича.

                1 Reply Last reply Reply Quote 0
                • P
                  paran0id
                  last edited by

                  фича в том, что стейты должны убиваться, а проблема в том, что они не убиваются

                  1 Reply Last reply Reply Quote 0
                  • werterW
                    werter
                    last edited by

                    Вы 2.1 с нуля ставили или обновлением? Если обновлением - ставьте с нуля и проверяйте. Если и это не поможет - пишите разработчикам.

                    1 Reply Last reply Reply Quote 0
                    • P
                      paran0id
                      last edited by

                      Сначала я ставил обновлением, но после этого глючила статистика потерь на WANах. Потом ставил с нуля, применив поверх старый конфиг (отредактировав изменившиеся параметры).

                      1 Reply Last reply Reply Quote 0
                      • werterW
                        werter
                        last edited by

                        У вас реальная машина или виртуалка? Если виртуалка - не на MS HV случаем?

                        1 Reply Last reply Reply Quote 0
                        • P
                          paran0id
                          last edited by

                          реальное железо

                          1 Reply Last reply Reply Quote 0
                          • D
                            DasTieRR
                            last edited by

                            Галочка State Killing on Gateway Failure снята.
                            Как я понял, в этом случае, галка должна стоять.

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