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

    cURL error in IP log files

    Scheduled Pinned Locked Moved pfBlockerNG
    1 Posts 1 Posters 198 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.
    • S
      Sissy
      last edited by Sissy

      I am running pfBlockerNG-devel version 3.0.0_16.

      I believe that where ASN should be, my IP log files are showing "cURL Error | 0". Here is an example from ip_block.log:

      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      Jun 14 20:58:19,1461429920,igb0,WAN,block,4,6,TCP-S,91.191.209.236,192.168.0.200,32880,25,in,BG,pfB_Europe_v4,91.191.208.0/20,BG_v4,Unknown,local ip addresses for #########.### servers,cURL Error | 0,-
      

      Please note that I substituted "#########.###" for my domain name for reasons of privacy.

      Is this an indication that something is misconfigured? This is an instance of pfSense that has been reliably running for many years. I've just now started looking at the raw logs and wanted to know if there's something I can do in order to get the ASN (I assume of the source IP) to be resolved properly?

      Thanks in advance to anyone who lends a hand resolving this.

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