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

    Feed Update Issue -- Talos

    Scheduled Pinned Locked Moved pfBlockerNG
    17 Posts 9 Posters 8.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.
    • NogBadTheBadN
      NogBadTheBad
      last edited by NogBadTheBad

      @Gertjan said in Feed Update Issue -- Talos:

      These lists, used by "pfBlockerNG", have to be maintained, also by you. Nothing is static, they can change.

      [ ISC_1000_30_v4 ]		 exists.
      [ ISC_Block_v4 ]		 exists.
      [ Spamhaus_Drop_v4 ]		 exists.
      [ Spamhaus_eDrop_v4 ]		 exists.
      [ Talos_BL_v4 ]			 Downloading update .. 403 Forbidden
      
       [ pfB_PRI1_v4 - Talos_BL_v4 ] Download FAIL
        Firewall and/or IDS (Legacy mode only) are not blocking download.
      

      I wonder if its the redirect it's not liking, I just noticed this.

      Screenshot 2019-05-02 at 16.13.43.png

      Screenshot 2019-05-02 at 16.14.31.png

      Andy

      1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

      1 Reply Last reply Reply Quote 1
      • GertjanG
        Gertjan
        last edited by

        One point for @NogBadTheBad : you just discovered that a browser is probably somewhat smarter as the 'wget' or 'curl' used by 'pfBlockerNG'.

        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 1
        • linuxmanr4L
          linuxmanr4
          last edited by

          It's exactly the same for me.

          I provisionally changed the url to Amazon hosted and it seems to work.

          https://talos-intelligence-site.s3.amazonaws.com/production/document_files/files/000/066/901/original/ip_filter.blf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIXACIED2SPMSC7GA%2F20190502%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190502T162159Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=3e1120e4e5e9b3d2b5e516f03adcfa299a9ef616c0aa859424a12d8d41c5d2d7

          [ Spamhaus_Drop_v4 ]		 exists.
          [ Spamhaus_eDrop_v4 ]		 exists.
          [ Talos_BL_v4 ]			 Downloading update .. 200 OK. completed ..
          

          I took note of the previous url in case it works again.

          https://www.talosintelligence.com/feeds/ip-filter.blf

          Greetings. ☺

          provelsP 1 Reply Last reply Reply Quote 0
          • provelsP
            provels @linuxmanr4
            last edited by

            @linuxmanr4 Your link doesn't seem to work anymore. I believe the extended information has caused it to expire. Same with me. Things are munged server-side.

            Peder

            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

            linuxmanr4L 1 Reply Last reply Reply Quote 0
            • linuxmanr4L
              linuxmanr4 @provels
              last edited by

              That's right @provels , it worked for a while and then it did the same thing again.

              I am going to report this problem to pfBlockerNG.

              RonpfSR 1 Reply Last reply Reply Quote 0
              • RonpfSR
                RonpfS @linuxmanr4
                last edited by

                @linuxmanr4
                There is an "Expires=3600" in the redirect URL 😒

                2.4.5-RELEASE-p1 (amd64)
                Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                BBcan177B 1 Reply Last reply Reply Quote 0
                • BBcan177B
                  BBcan177 Moderator @RonpfS
                  last edited by

                  https://twitter.com/BBcan177/status/1124471820940468224

                  "Experience is something you don't get until just after you need it."

                  Website: http://pfBlockerNG.com
                  Twitter: @BBcan177  #pfBlockerNG
                  Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                  1 Reply Last reply Reply Quote 0
                  • N
                    neoaeon
                    last edited by neoaeon

                    The user agent curlopt was resulting in a 403 from Cloudflare, seems they didn't like Google Chrome 43 circa 2015.

                    I changed my user agent to plain old 'curl' and everything is working again.

                    edit /usr/local/pkg/pfblockerng/pfblockerng.inc line 118:
                    from:

                    $pfb['curl_defaults'] = array(  CURLOPT_USERAGENT       => 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 Chrome/43.0.2357.65 Safari/537.36',
                    

                    to:

                    $pfb['curl_defaults'] = array(  CURLOPT_USERAGENT       => 'curl',
                    

                    edit /usr/local/pkg/pfblocker/pfblockerng_install.inc line 59:
                    from:

                    curl_setopt($ch, CURLOPT_USERAGENT, 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 Chrome/43.0.2357.65 Safari/537.36');
                    

                    to:

                    curl_setopt($ch, CURLOPT_USERAGENT, 'curl');
                    

                    -neo

                    P.s. @BBcan177 if you're going to fix this, while you're in there can you replace 1.1.1.1 with the RFC 5737 compliant 192.0.2.0 so we can use Cloudflare DNS w/o having to edit pfblockerng.inc and pfblockerng.sh please? :) (don't forget about the regex on pfblockerng.sh line 992)

                    Edit: BTW, not sure what's going on with caching, but restart php-fam didn't cause an update, I had to delete the /usr/local/pkg/pfblockerng/.pfblockerng.* files and then restart php-fam for the change to activate.

                    Edit2: diff for 2.1.4_17, fixes cloudflare DNS and Talos blacklists. pfblockerng_2.1.4_17.diff

                    1. scp/sftp the diff file to /usr/local/pkg/pfblockerng
                    2. run the following command from a shell:
                    cd /usr/local/pkg/pfblockerng ; patch -p0 < pfblockerng_2.1.4_17.diff
                    
                    D linuxmanr4L 2 Replies Last reply Reply Quote 3
                    • D
                      Digital_ADHD @neoaeon
                      last edited by

                      This worked for me, Thanks!

                      [ Talos_BL_v4 ] Downloading update .. 200 OK. completed ..

                      @neoaeon said in Feed Update Issue -- Talos:

                      edit /usr/local/pkg/pfblockerng/pfblockerng.inc line 118:
                      from:
                      $pfb['curl_defaults'] = array( CURLOPT_USERAGENT => 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 Chrome/43.0.2357.65 Safari/537.36',

                      to:
                      $pfb['curl_defaults'] = array( CURLOPT_USERAGENT => 'curl',

                      edit /usr/local/pkg/pfblocker/pfblockerng_install.inc line 59:
                      from:
                      curl_setopt($ch, CURLOPT_USERAGENT, 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 Chrome/43.0.2357.65 Safari/537.36');

                      to:
                      curl_setopt($ch, CURLOPT_USERAGENT, 'curl');

                      1 Reply Last reply Reply Quote 0
                      • linuxmanr4L
                        linuxmanr4 @neoaeon
                        last edited by

                        Thanks @neoaeon, after modifying the files the problem has been solved. ☺ 👍

                        1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS
                          last edited by

                          The feed now download without any modification to User agent.

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          D 1 Reply Last reply Reply Quote 3
                          • D
                            Digital_ADHD @RonpfS
                            last edited by

                            @RonpfS said in Feed Update Issue -- Talos:

                            The feed now download without any modification to User agent.

                            Thanks for the update!

                            1 Reply Last reply Reply Quote 0
                            • provelsP
                              provels
                              last edited by provels

                              Looks like this feed is borked again. Worked fine for a while. Redid the useragent mods to fix.

                              Peder

                              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                              D 1 Reply Last reply Reply Quote 0
                              • D
                                Digital_ADHD @provels
                                last edited by

                                @provels updating useragent fixed this again for me

                                1 Reply Last reply Reply Quote 0
                                • N
                                  neoaeon
                                  last edited by

                                  Zombie thread resurrection as this issue is back due to a regression.

                                  Link to new thread: https://forum.netgate.com/topic/161817/pfblockerng-2-1x-fix-for-talos-feed-and-cloudflare-1-1-1-1-dns

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