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

    NAVEGAÇÃO

    Portuguese
    5
    12
    1.4k
    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
      cristianojcruzzz
      last edited by

      Bom dia, estou com um problema e não estou identificando a origem do problema.

      As vezes acontece que a navegação em páginas cai, mas, temos uma rádio tocando aqui no estabelecimento, que é em um computador, ela se mantem e toda a rede também.

      SYSTEM LOGS GERAL

      
check_reload_status: Reloading filter
Apr 6 08:13:22	check_reload_status: updating dyndns WANGW
Apr 6 08:13:22	check_reload_status: Restarting ipsec tunnels
Apr 6 08:13:22	check_reload_status: Restarting OpenVPN tunnels/interfaces
Apr 6 08:13:22	check_reload_status: Reloading filter
Apr 6 08:13:27	check_reload_status: updating dyndns WANGW
Apr 6 08:13:27	check_reload_status: Restarting ipsec tunnels
Apr 6 08:13:27	check_reload_status: Restarting OpenVPN tunnels/interfaces
Apr 6 08:13:27	check_reload_status: Reloading filter

      SYSTEM LOGS GATEWAY

      Apr 4 08:07:55	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:08:15	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:08:26	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:08:55	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:09:05	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:09:05	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:09:20	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:09:40	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:10:10	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:10:20	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:10:30	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:11:15	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:11:40	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:11:55	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:12:26	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:12:30	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:13:26	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:13:30	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:14:50	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:15:20	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:15:35	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:15:41	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:20:52	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:21:03	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 4 08:21:13	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 4 08:22:03	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:08:12	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:08:12	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:08:27	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:08:57	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:09:19	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:09:32	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:09:52	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:09:57	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:10:17	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:10:17	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:10:27	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:10:57	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:11:07	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:11:47	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:12:47	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:12:47	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:13:12	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:13:17	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:15:02	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:15:08	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***
Apr 6 08:15:58	apinger: ALARM: WANGW(192.168.0.1) *** delay ***
Apr 6 08:16:43	apinger: alarm canceled: WANGW(192.168.0.1) *** delay ***
Apr 6 08:20:59	apinger: ALARM: WANGW(192.168.0.1) *** down ***
Apr 6 08:21:19	apinger: alarm canceled: WANGW(192.168.0.1) *** down ***

      O que pode estar ocasionando o problema? Obrigado !!

      1 Reply Last reply Reply Quote 0
      • T
        tomaswaldow
        last edited by

        A conexão dessa interface WAN está estável? Já vi situação parecida e era problema de hardware (cabo ou switch).

        Tomas @ 2W Consultoria

        1 Reply Last reply Reply Quote 0
        • C
          cristianojcruzzz
          last edited by

          Aparentemente está sim.
          O modem está com o DHCP desabilitado, e o IP da wan do pfsense está estático, pode ser isso a causa do problema?

          Obrigado!!!

          1 Reply Last reply Reply Quote 0
          • R
            reinaldo.feitosa
            last edited by

            quando cai verifica se o modem responde o ping.

            1 Reply Last reply Reply Quote 0
            • C
              cristianojcruzzz
              last edited by

              Habilitei o log do modem, creio que o problema está na minha provedora de internet "OI".

              Caso não seja o modem, só pode ser o pfSense, ai eu aviso.

              1 Reply Last reply Reply Quote 0
              • C
                cristianojcruzzz
                last edited by

                Então, verifiquei, e fiz alguns testes, não aparenta ser o modem.
                Ao cair a internet não consigo pingar o modem.
                Eu retiro o cabo do modem, e conecto diretamente no meu computador e a navegação está normal.

                O que será a causa desse problema?

                Está aparecendo um log estranho no computador

                
Apr 7 14:25:27	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:25:33	syslogd: exiting on signal 15
Apr 7 14:25:33	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:25:36	syslogd: exiting on signal 15
Apr 7 14:25:36	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:26:00	syslogd: exiting on signal 15
Apr 7 14:26:00	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:26:13	syslogd: exiting on signal 15
Apr 7 14:26:13	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:26:17	syslogd: exiting on signal 15
Apr 7 14:26:17	syslogd: kernel boot file is /boot/kernel/kernel
Apr 7 14:26:20	syslogd: exiting on signal 15
Apr 7 14:26:20	syslogd: kernel boot file is /boot/kernel/kernel
                1 Reply Last reply Reply Quote 0
                • C
                  cristianojcruzzz
                  last edited by

                  Ainda persiste o problema, alguém tem ideia da causa do problema?

                  1 Reply Last reply Reply Quote 0
                  • R
                    reinaldo.feitosa
                    last edited by

                    @reinaldo.feitosa:

                    quando cai verifica se o modem responde o ping.

                    Qual a resposta para este tópico???

                    1 Reply Last reply Reply Quote 0
                    • H
                      henriquejensen
                      last edited by

                      Vc precisa nos dar mais detalhes. As vezes pode ser a placa de rede do pfsense que está com problema.

                      Vc já tentou deixar o modem em bridge e discar pelo pfsense configurando a wan dele como PPPOE? Tenho aqui GVT e Oi no meu pfsense, ambos com modem em bridge e funciona bem.

                      1 Reply Last reply Reply Quote 0
                      • C
                        cristianojcruzzz
                        last edited by

                        Quais detalhes preciso?
                        Troquei a placa de rede do pfSense, são duas iguais, a da LAN funciona perfeitamente.

                        Tanto é que; quando eu pingo o modem varia de 200ms a 800ms, e se eu pingo no pfsense é 1ms.

                        Quanto a deixar em Bridge ainda não fiz.

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

                          @cristianojcruzzz:

                          Tanto é que; quando eu pingo o modem varia de 200ms a 800ms

                          Muito alto o tempo de resposta.
                          Configure o modem em modo bridge e autentique ele na wan do pfsense. Isso diminui o processamento do modem.

                          Já vi isso acontecer em links sobrecarregados na entrada e/ou saída.

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

                          Help a community developer! ;D

                          1 Reply Last reply Reply Quote 0
                          • C
                            cristianojcruzzz
                            last edited by

                            Será que desta forma corrigirá o problema? Vou efetuar os testes e respondo quando obter um resultado.

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