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

    Conexão caindo.

    Scheduled Pinned Locked Moved Portuguese
    5 Posts 2 Posters 729 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.
    • M
      marcelob23
      last edited by

      Boa tarde senhores,

      Seguinte instalei a versão 2.2.4 do pfsense e estou tendo um problema com acesso ao meu sistema.

      Basicamente o acesso funciona da seguinte forma:

      Conecto no ip x.x.x.x na porta 1515 ou 1262 .

      O que acontece e que ele consegue a conexão e depois de mais ou menos 30 segundos a conexão cai.

      Alguém tem alguma ideia do que possa estar acontecendo ?

      Quando desabilito todos os filtros de pacotes ele conecta normal.

      Obrigado desde já.

      1 Reply Last reply Reply Quote 0
      • M
        marcelob23
        last edited by

        Acho que pode ser esse o problema:

        Sep 17 12:47:46 check_reload_status: Syncing firewall
        Sep 17 12:48:43 check_reload_status: Syncing firewall
        Sep 17 12:48:46 check_reload_status: Reloading filter
        Sep 17 12:50:40 check_reload_status: Syncing firewall
        Sep 17 12:50:40 check_reload_status: Reloading filter
        Sep 17 12:56:34 check_reload_status: Syncing firewall
        Sep 17 12:56:35 check_reload_status: Reloading filter
        Sep 17 12:56:53 check_reload_status: Syncing firewall
        Sep 17 12:57:35 check_reload_status: Syncing firewall
        Sep 17 12:58:55 check_reload_status: Syncing firewall
        Sep 17 12:58:58 check_reload_status: Syncing firewall
        Sep 17 12:59:07 check_reload_status: Reloading filter
        Sep 17 12:59:50 check_reload_status: Syncing firewall
        Sep 17 12:59:53 check_reload_status: Reloading filter
        Sep 17 13:00:44 check_reload_status: Syncing firewall
        Sep 17 13:02:52 check_reload_status: Syncing firewall
        Sep 17 13:02:55 check_reload_status: Reloading filter
        Sep 17 13:04:37 check_reload_status: Syncing firewall
        Sep 17 13:04:41 check_reload_status: Reloading filter
        Sep 17 13:05:04 check_reload_status: Syncing firewall
        Sep 17 13:05:07 check_reload_status: Reloading filter
        Sep 17 13:06:28 check_reload_status: Syncing firewall
        Sep 17 13:06:30 check_reload_status: Reloading filter
        Sep 17 13:08:20 check_reload_status: Syncing firewall
        Sep 17 13:08:20 check_reload_status: Reloading filter

        Alguém sabe o porque do firewall estar restartando tanto assim ? Qual o motivo que pode estar causando isso ?

        Obrigado.

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          Veja o histórico do status dos gateways.

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • M
            marcelob23
            last edited by

            Sep 15 09:29:17 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:29:29 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:29:46 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:30:09 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:30:19 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:30:22 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:30:38 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:30:40 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:31:43 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:31:53 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:33:19 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:33:33 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 15 09:48:09 apinger: Starting Alarm Pinger, apinger(15347)
            Sep 15 15:06:32 apinger: SIGHUP received, reloading configuration.
            Sep 16 08:52:24 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 16 08:52:26 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 16 10:23:26 apinger: ALARM: GW_LAN(192.168.2.2) *** down ***
            Sep 16 10:23:36 apinger: alarm canceled: GW_LAN(192.168.2.2) *** down ***
            Sep 16 10:23:38 apinger: SIGHUP received, reloading configuration.
            Sep 16 15:06:26 apinger: SIGHUP received, reloading configuration.
            Sep 17 12:40:01 apinger: Starting Alarm Pinger, apinger(18279)

            Ja estou pensando em instalar uma outra versão. Quebrando a cabeça . . .

            Monitorei um host aqui com tcpdump e a porta 1515, e ele não pega nenhum tipo de anormalidade.

            1 Reply Last reply Reply Quote 0
            • marcellocM
              marcelloc
              last edited by

              Os logs mostram que seu gateway não está legal, o que força uma "ação" a cada teste.

              Se tem certeza que seu gateway não está com problema, desabilita a monitoria dele em system->routing.

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

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