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

    [pfB_PRI1_v4] Too many alerts out for "196.55.215.129", 443, 5222

    Scheduled Pinned Locked Moved pfBlockerNG
    16 Posts 6 Posters 2.1k 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.
    • GertjanG
      Gertjan @denis_ju
      last edited by

      @rimaju

      Can you show the issue ?
      Isn't there a LAN (local !) IP listed ?

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

      D 1 Reply Last reply Reply Quote 0
      • D
        denis_ju @Gertjan
        last edited by

        @gertjan Not yet.
        My wifi is a mikrotik on NAT. I see only the mikrotik ip on pfsense.

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

          @rimaju said in [pfB_PRI1_v4] Too many alerts out for "196.55.215.129", 443, 5222:

          @gertjan Not yet.
          My wifi is a mikrotik on NAT. I see only the mikrotik ip on pfsense.

          Your AP is doing NAT ? Is it a router ?
          Don't do that .... just have it doing AP. Shut down the rest (at first).

          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
          • O
            Okijames
            last edited by

            I noticed a ton (30K+ attempts in a few hours) of block alerts to the same address. This is from a phone I recently rooted and installed lineageos. With very few apps installed, I was able to whittle it down to Telegram, the FOSS version in fact.

            I've uninstalled Telegram and the phone is no longer attempting to connect to 196.55.215.129.

            Spamhaus has the 196.52.0.0/14 CIDR block listed here... https://www.spamhaus.org/sbl/query/SBL510704

            My laptop, with Telegram installed, is also attempting to reach addresses in that CIDR block.

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

              @okijames said in [pfB_PRI1_v4] Too many alerts out for "196.55.215.129", 443, 5222:

              phone I recently rooted

              Ah, nice. A typical school-example of what happens when rooted.
              You have to answer the question : do you trust the root kit ?
              Telegram accessing https ports ? Euh .......... right, it does : https://core.telegram.org/mtproto/transports
              So it could be so that 196.55.215.129 is a front end CDN for telegram - and it's refusing your telegram phone app requests now. Better to check why if possible - maybe your root kit isn't that innocent.

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

              O 1 Reply Last reply Reply Quote 0
              • O
                Okijames @Gertjan
                last edited by

                @gertjan I never fully trust anything :)

                The phone was well behaved before installing Telegram, and is back to being quiet now that Telegram has been removed. Though now I'm doing packet captures of its traffic, where I was only looking at flow and firewall logs before.

                Stopping Telegram on my laptop has the same affect. No more connection attempts to the that address.

                I should note that Telegram functioned normally, it doesn't appear these specific connections are required for normal operation.

                1 Reply Last reply Reply Quote 0
                • n3xus_x3N
                  n3xus_x3
                  last edited by

                  I have the same problem, the smartphone does not have any type of root , the connections are many... , for now I leave it blocked, there is no disservice at the moment
                  block.png

                  O 1 Reply Last reply Reply Quote 0
                  • O
                    Okijames
                    last edited by

                    Another burst (47K so far) of attempts today, from both my rooted and unrooted phones. It appears to be the FOSS version of Telegram for Android is the culprit.

                    On my Mac the full desktop Telegram client is less aggressive, in the 100's of attempts per day. The Lite version does not exhibit this behavior.

                    1 Reply Last reply Reply Quote 0
                    • O
                      Okijames @n3xus_x3
                      last edited by

                      @n3xus_x3 I opened an issue on github. Please chime in... https://github.com/Telegram-FOSS-Team/Telegram-FOSS/issues/490

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

                        It is not only the Foss version but official Android Telegram app does the same. I have 11888 hits on the IP 196.55.215.129 in last 24 hours. Anyway the Telegram itself works OK. It is "just" annoying...

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