Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    [RESOLVIDO] Problema com portal de DVR ecotronic

    Scheduled Pinned Locked Moved Portuguese
    8 Posts 2 Posters 4.2k 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.
    • marcosjostM
      marcosjost
      last edited by

      BOm dia pessoal, estou com um problema com um dvr ecotronic…vamos a situação:
      Pfsense 2.1 com squid 2.7.9 e squidguard em modo transparente. Ele não tem nenhum bloqueio, por enquanto so estou gerando relatorios no ligthsquid....
      Tenho um dvr da ecotronic na rede interna, fiz o NAT das portas 9000 e 8081 no pfsense, de fora eu consigo acessar normalmente pelo ip externo do firewall e dentro da rede tambem.
      A conexao de internet e fibra por ppoe ( o pfsense faz a autenticacao e recebe um ip fixo). Antes era um roteador microtik que fazia a conexao, nele constam so os nats da portas 8081 e 9000....

      Mas tem outra situacao:
      A ecotronic tem um portal ( portal.ecotroniccftv.com.br ), esse portal comunica com os dvrs. È nele que nao funciona, quando acesso ele e ponho o numero de serie ele nao acha o dvr ....
      Ja rodei um tcpdump e vi que ele usa a porta 110 para comunicar com o dvr, alem das 8081 e 9000, fiz o nat dela do ip do portal para o dvr e nada ainda....
      No squid, coloquei Bypass proxy for these source IPs o ip do dvr inerno e no Bypass proxy for these destination IPs o ip do portal
      Mas nada ainda.....
      Se alguem pduer dar uma luz .... :)

      Manual dele: http://www.ecotroniccftv.com.br/produtos/linha-nova/manual_completo_dvr_ecotronic.pdf

      1 Reply Last reply
      Reply Quote 0
      • marcosjostM
        marcosjost
        last edited by

        o tcpdump rodando na interface de rede interna e o ip do dvr ( 192.168.1.10)
        tcpdump -ni re0 host 192.168.1.10

        
        14:03:46.480835 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:03:50.709923 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:03:51.239278 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:51.239401 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:52.239505 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:52.239628 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:54.322396 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:54.356624 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:54.940295 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:03:55.371859 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:55.372032 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:03:59.180364 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:03:59.878964 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 312
        14:04:03.411128 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:04:07.629652 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        
        

        199.36.78.198 é o ip do portal da ecotronic….

        e o tcpdump na pppoe
        tcpdump -ni pppoe0 host 192.168.1.10

        
        listening on pppoe0, link-type NULL (BSD loopback), capture size 96 bytes
        14:06:46.649762 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:06:46.649891 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:06:47.650113 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:06:47.650245 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:06:48.155802 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 312
        14:06:48.459835 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:06:52.695445 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:06:56.921316 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:07:01.150831 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:07:03.159233 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:07:03.159858 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:07:04.159514 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:07:04.159673 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:07:05.383183 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:07:09.167974 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 312
        14:07:09.609443 IP 192.168.1.10.44220 > 64.4.10.33.123: NTPv4, Client, length 48
        14:07:11.161478 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        14:07:11.161648 IP 192.168.1.10.34738 > 199.36.78.198.110: UDP, length 188
        
        

        So há fluxo do dvr para fora….

        Ps> No momento desses tcpdump ninguem estava acessando o dvr pelo sistema dele, somente tentando pelo portal da ecotronic.
        Se acesso diretamente o dvr funciona e o tcpdump mosta todo fluxo de comunicao na 8081 e 9000 normalmente.

        Nas configuracoes do dvr, ele tem um App net que tem ativos os servicos de DDNS ( com o propio portal ecotronic como server) e o e-mails ( por isso o uso da porta 110)

        1 Reply Last reply
        Reply Quote 0
        • L
          lucaspolli
          last edited by

          vc percebeu que sao portas UDP? verifique suas regras se nao estao para portas TCP

          1 Reply Last reply
          Reply Quote 0
          • marcosjostM
            marcosjost
            last edited by

            @lucaspolli:

            vc percebeu que sao portas UDP? verifique suas regras se nao estao para portas TCP

            as regras estao como TCP/UDP

            1 Reply Last reply
            Reply Quote 0
            • L
              lucaspolli
              last edited by

              o sincronismo da hora esta sendo feito corretamente? ja vi casos de problemas por hora diferente e ate  mesmo por timezone diferentes

              1 Reply Last reply
              Reply Quote 0
              • marcosjostM
                marcosjost
                last edited by

                Exemplo de um trecho do tcpdump com um acesso externo ao sistema de monitoramento do dvr ( que funciona normalmente)
                200.200.200.200 é o ip externo do qual acessei o sistema do dvr

                
                14:21:39.375573 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.395782 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4620918, win 64800, length 0
                14:21:39.396471 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.396594 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.400256 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4628118, win 64800, length 0
                14:21:39.401275 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.401395 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.401515 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.401643 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.401760 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.421722 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4630998, win 64800, length 0
                14:21:39.422526 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.422649 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.432192 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4633878, win 64800, length 0
                14:21:39.432582 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4636758, win 64800, length 0
                14:21:39.432592 IP 200.200.200.200.46831 > 192.168.1.10.9000: Flags [.], ack 4639638, win 64800, length 0
                14:21:39.432899 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.433019 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.433287 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.433408 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.433531 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                14:21:39.433651 IP 192.168.1.10.9000 > 200.200.200.200.46831: Flags [.], ack 154, win 6432, length 1440
                
                
                1 Reply Last reply
                Reply Quote 0
                • marcosjostM
                  marcosjost
                  last edited by

                  @lucaspolli:

                  o sincronismo da hora esta sendo feito corretamente? ja vi casos de problemas por hora diferente e ate  mesmo por timezone diferentes

                  Sim, estao certas….ele esta com o sincronismo ativo com o time.windows.com , e fuso GMT-03:00 Brasilia

                  Se coloco o microtik como roteador de volta funciona normalmente....

                  1 Reply Last reply
                  Reply Quote 0
                  • marcosjostM
                    marcosjost
                    last edited by

                    Bom…faltou "apenas" uma porta .....53.... liberei ela na wan para o ip do dvr e ok
                    Entao ficou assim> Nat das portas 8081 e 9000 tcp/udp e liberacao da porta 53 para o ip do dvr....

                    1 Reply Last reply
                    Reply Quote 0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    • First post
                      Last post
                    Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                    Privacy Policy · Cookie Policy