Netgate ip address blocked by PF BlokerNG
-
I just tried logging into my Netgate 2100 and I get a page saying this website has been blocked by the Network administrator. WTF, I am the administrator.....
Was I hacked or am I missing something. -
@Stellir said in Netgate ip address blocked by PF BlokerNG:
I just tried logging into my Netgate 2100 and I get a page saying this website has been blocked by the Network administrator. WTF, I am the administrator.....
Was I hacked or am I missing something.
-
OK, I managed to get into the router by doing the following.
Used a console cable to access the router directly.
Listed the logs for config and saw no changes since last year.
Unplugged Internet feed from the Router
Chose the option in the SSH session to restart the device.
I was then able to log into the GUI interface using the Router IP address.
I then put the Internet feed back into the device.
Now seems my device's partition is too small for an update and I have to contact support. -
@Stellir said in Netgate ip address blocked by PF BlokerNG:
WTF, I am the administrator.....
Was I hacked or am I missing something.Noop.
Just a lazy administrator
as you forgot to do some of the admin's homework.You saw this :
So you know who or what blocked you.
That is, when you install pfBlockerng, by itself, it blocks (does) nothing. It's the IP and DNSBL feeds, installed by the admin, that do the work.
These lists are created by people like you, me and many others.
No need to wonder what would happen if in IP network like "192.168.1.1/24" makes it to a list you decided to use ^^
edit : that is : there is no 'feed' indicated : you added 192.168.1.1/24 yourself ? ?
edit : you've removed the RFC1918 IP ....
Maybe this sounds strange, but your should inspect these lists before you use them. After all, they do have a quality / price performance that is undefined.@Stellir said in Netgate ip address blocked by PF BlokerNG:
Now seems my device's partition is too small for an update and I have to contact support.
pfBlockerng creates its own log files, See here : /var/unbound/var/log/pfblockerng/ and these can become pretty big (check also your pfBlockerng log file size settings).
No need to contact Netgate, as you already know the answer : to use big packages you need a big(ger) drive.
-
R rcoleman-netgate moved this topic from webGUI on
-
Ok, could you please tell me how to modify the list in order to allow my IP into the router?
-
You mean : you have a pfSense LAN using some IP range - most surely RFC1918, and this RFC1918 is in the list you have selected ?
Plan A : most straight forward solution : ditch this list - it was a wrong pick.
Plan B : whitelist the IP or even entire networks.Still, the question is a bit strange :
to allow my IP into the router?
You control pfSense, right ? So you control who accesses your LAN (into pfSense), or whatever interface.
Please add more details to the question.
