Netgate blocked my public IP on ACB
-
Oh I see it. Yes your IP was blocked because it was hammering the pkg repos. 11000 requests in 24hrs!
That was done back in July though. Was ACB working more recently?
Do you have multiple firewalls using that public IP?
-
Hey @stephenw10, thank you for answering and checking! Appreciate it.
11,000 requests in 24 hours is crazy!!!
It wasn't intended, nor was it obviously done by me personally (11,000 clicks in one day is record-breaking).Anyway, no, my public IP is managed by a single pfSense...
Have you had similar experiences? What could it have been? I don't want it to happen again.
But above all, can it be fixed?Thank you very much again.
-
@stephenw10 forgot to say: I don't know if it was working, I realized today it is not.
I can't, obviously, check my uploaded backup to verify they worked. -
Mmm, OK found your ticket. It does look like it hasn't checked in since July 12th. Does it show a very large number of alerts?
Can you think of any reason there might have been such a high request rate? Multiple firewalls behind it is most likely.
-
@stephenw10 Yes, it showed a high number of alerts saying “An error occurred while uploading the encrypted pfSense configuration to https://acb.netgate.com/save (Connection timed out)”.
I noticed it today because I wanted to upgrade the build and install some packages.I can confirm that I only manage one pfSense, with a fairly standard segmented LAN behind it.
Today I ran several analyses to see if there were any rogue devices on my network, but I didn't find anything, and in any case, I don't think that even if there were, it would hit the ACB repositories, but never knows...
I really don't know what to think.
-
It wasn't ACB it was hitting it was the repo data servers. As though it was running 'pfSense-repoc' continually, or multiple devices running it. Let me see....
-
I wonder if this post is relevant perhaps?
-
I believe is was actually a home assist plugin misbehaving.
-
@tinfoilmatt Thank you very much for the suggestion.
As Stephen said, the most likely hypothesis is that a Home Assistant integration caused the problem.
Unfortunately, I don't have any logs to confirm this hypothesis, but the integration was (afaik) the only thing besides me that had control over pfSense, so it's the main suspect. -
@tinfoilmatt said in Netgate blocked my public IP on ACB:
I wonder if this post is relevant perhaps?
This post shows : at 7 AM, 30 minutes, so ones a day, an "pkg update" is executed, a bit like option 13 on the console or visiting System > Package Manager inn the GUI, although the latter might work with a cache.
You could decide to do the update test every 5 minutes (or even less ?), and that means the Netgate update servers are hit 288 times per day by your pfSense.
Common sense would tell us this isn't a wise thing to do. -
Yeah, it was a lot more than that. I don't think it would be possible to do it deliberately. It seems more likely a bug in the plugin at that time.
