pfblockerNG ASN bgpview trouble
-
I also tried
- disabling pfblockerNG ASN cache,
- deleting the /var/db/pfblockerng/original/ files
- Deleting the /var/db/pfblockerng/native/ files
- Rerunning Firewall / pfBlockerNG / Update -> Reload, IP
But still only empty files result
-
@Patch I tried it myself, making this alias and failed. I see the same as you. Older ASN-aliases aren't affected as far as I can tell. So you are not alone. I guess I will try another ASN next.
Edit: Also no luck, old ones work. -
and yet it works for me (still) (Don't read any of this as directed at you. I'm just tagging you because:
You might recall, as I think you where part of a thread, I'm guessing about a year ago, with the same OMG it is creating 127... Empty files
You have to ask "why does it work for me ?"
They patch I created then still works. However words of
WARNING: That version no longer applies directly on 3.0.2_9 (I had to tweak it a bit because of an underlying file change. On my end that tweak took less than five minutes. Unfortunately I can't just provide my updated patch because I have "fixed/added" several other things that are "not important" to either the developer and/or the public.. (or so I'm told)
WARNING: Not sure that the older version of the patch specifically addresses this issue, which I know I've tweaked it a couple of times over the past year. I'm to lazy to look at, code change log to find out. So, the patch you might still find floating around might only address the specific case at the time and not additional cases I've encountered in daily use since then.I can clearly prove it on both my 2.7.2 test box or 23.03 production box, simple to do - revert the patch watch it fail as being discussed, apply the patch watch it work. Clearly it is NOT the feed at this point as demonstrated by the direct curl command test I suggested earlier in this thread.
After the last go around and being told (by several) that the patch was "silly", "not needed" and not going to be incorporated because what is there, "works fine" I just moved on, hence the I can't release an updated patch I'm currently using. In part, some of those other changes are direct updating to remote syslog in real time, for example.
When this all started going down again last week, my graylog immediately started informing me of the download issue, (filtered on level 2) (critical enough but not notifications.)
part of that most recent outage was the opportunity for me to simulate the case of the system creating an empty file --- to you know -- "test the emergency broadcast system." I had the OMG (filtered on level 1) failure event email within seconds of creating the "empty file manually" --
Sorry, not sure what else I can do to help. I've given up on trying to create tickets, discuss with the developers, suggest improvements etc Now I just "twist" the "silly" into the code so that it suits my application, requirements and use of the device... I been through a few OS upgrades and other than the small adjustment I had to make to one patch, going to 24.03 and pf 3. _9 I have never had a problem
Moving on..
-
@jrey said in pfblockerNG ASN bgpview trouble:
You might recall, as I think you where part of a thread, I'm guessing about a year ago, with the same OMG it is creating 127... Empty files
Sure, I do remember and am following you for that.
What I didn't remembered, that the patch is still needed. And I can confirm, once again, that your patch is working. I applied it a few seconds ago, thanks again @jrey .
-
Cool
for the record can you just confirm what versions of things you are currently running ?Edit: because what I couldn't remember is what specific change I may have made in that patch, caused the specific hiccup when I upgraded to 24.03 and 3.0.2_9 came with it. I just recall having to tweak my current version of the patch to make it apply. (I guessing it might have been something else I've changed in the patch since that earlier one)
-
This post is deleted! -
24.03-RELEASE, pfBlockerNG 3.2.0_10
2.7.2-RELEASE, pfBlockerNG 3.2.0_8@jrey When I tested with CE, it failed with one AS for me (AS8881). I then retested with another and this one was working (AS1299)...
I have not tested (AS8881) on Plus though. So there might be a problem still. -
Great thanks - so then the version of the patch I originally provided you still applies to both. good to know (I guess)
Means something I changed since that earlier version is what sent me down the path won't apply path when I upgrade to 24.03 --
Oh darn, I just shut my 2.7.2 virtual network down. Let me fire it back up and look at those two ASnumbers you provided ..
Thanks
-
@jrey Retesting this ASN again, now works everywhere. So I think we are good. Maybe it was just a hiccup.
-
Interesting, can you share the log snippet where it failed ?
I tried 2.7.2 and for me it failed on the first attempt but picked it up on the auto retry.
[ AS40027_v4 ] Downloading update [ 08/18/24 11:01:12 ] . Downloading ASN: 40027. .. completed (Download Valid) . completed .. [ AS8881_v4 ] Downloading update . Downloading ASN: 8881. .. Failed to download ASN . .. completed (Download Valid) . completed .. [ AS1299_v4 ] Downloading update [ 08/18/24 11:01:13 ] . Downloading ASN: 1299. .. completed (Download Valid) . completed .. -
@jrey said in pfblockerNG ASN bgpview trouble:
Interesting, can you share the log snippet where it failed ?
Where is that exactly, sry still not an experienced pfBlocker User.
Also I thought I hadn't this bevor on that firewall but I guess I am wrong and it was there so it could be an old list... -
In the log here -- you will have to scroll through to find the one that failed (don't need the whole file just the part for the one that failed.
-
Restoring previously downloaded file contents... [ 08/9/24 20:45:57 ] [PFB_FILTER - 2] Invalid URL (not allowed2) [ AS8881 [ VERSATEL, DE ] ] [ 08/17/24 18:21:15 ] [PFB_FILTER - 2] Invalid URL (not allowed2) [ AS8881 ] [ 08/17/24 18:21:32 ] -
That's different.
Doesn't look related to the actual "download" of the file. but rather something bad left over from when it didn't download -- so it though it needed to restore the previous one 08/9/24 and then tried to process it.
if the latest download worked (the file in question has IPs listed) and "worked" as you stated above "Retesting this ASN again, now works everywhere. So I think we are good. Maybe it was just a hiccup." would likely be a good caption for the event.
if the [PFB_FILTER - 2] error shows up again, that might be something else to look at, I've never logged one of those and it is a completely different block of code.
Cheers
-
@jrey Sry, reading the log again, the first line I posted is not related to this but something before that.
And yes the file is working fine. Maybe I was to fast klicking reload again or something, it is an install on a VPS.
-
The problem is with BGPview.io which is now owned by Recorded Future. They are rate limiting their service due to some users who hit their services too much. The current code in pfB contains a User Agent Header which is being blocked en masse by them. I have requested that if they rate limit to block specific Agent strings as the suffix of the Agent String is unique to the user.
I have been emailing their support team for several weeks and they are saying it's low priority. I have also asked for their usage policy which they say they will add to their FYI page but it's low on their to do.
So I assume if it's working for some users, it could be they changed the Agent String. But if that were to happen en masse, it's back to the same result.
I am looking at an alternative ASN source as BGPview.io and previously Hurricane Electric don't want to support Open Source projects. Most likely will try to use ipinfo if their free options are accurate enough.
-
M michmoor referenced this topic on
-
Came across the same issue on one of our boxes. For the time being, have disabled the ASN download and copied over the relevant original files to reload into the affected system.
-
B Bob.Dig referenced this topic on
