PfBlockerNG

BBcan177 · Jun 17, 2016, 9:24 PM

Trying to suppress an internal IP (ie. 192.168.1.xxx).

I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.

blueduckdock · Jun 20, 2016, 12:43 PM

@BBcan177:

@blueduckdock:

Trying to suppress an internal IP (ie. 192.168.1.xxx).

I do not have ANY + sign in the alerts tab to add it to the suppression list. As far as I understand, you can add NATted local IPs to the list right? Even when I modify the alias directly and reload, pfblocker continues to block the packets.

You don't suppress Internal IPs.. Suppression is for External IPs and the Suppression Icon is only visible when "suppression" is enabled, and when the External IP is a /32 or /24. Also it won't suppress for Country Blocking…

To have some internal IPs excluded from the Block Rules… Best to use the "Adv. Inbound/Outbound" Rule settings.

Sounds good. Part of me thought that I'd have to adjust the rules and couldn't use the suppression but I figured I'd try.
Thanks again mate.

gerry · Jul 4, 2016, 8:31 PM

pfsense 2.2.6
I use the country lists to pretty much block anything outside of US/CA
I then have a whitelist set up for any exceptions
I am pretty sure that in the past this worked fine.
At some point the whitelist stopped having any effect.
The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
After poking around in the settings I found that setting the Rule Order to :
pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
Did something change that requires using this rule order rather than the default to get whitelists to work ?
I would have thought that this and the default would have been the same thing as far as whitelisting goes.
Although this works I am concerned that this may have unforeseen consequences.

BBcan177 · Jul 7, 2016, 4:02 AM

@gerry:

pfsense 2.2.6
I use the country lists to pretty much block anything outside of US/CA

Keep in mind that you could also just "Permit" the Countries that you want instead of blocking the world…

I am pretty sure that in the past this worked fine.
At some point the whitelist stopped having any effect.
The firewall rules order also seems incorrect in that the whitelist follows the pfb block lists
After poking around in the settings I found that setting the Rule Order to :
pfB_Pass/Match|pfB_Block/Reject|pfSense_Pass/Match
seems to get things working correctly - and the rules are now ordered as expected with the pass rule above the block rules.
Did something change that requires using this rule order rather than the default to get whitelists to work ?
I would have thought that this and the default would have been the same thing as far as whitelisting goes.
Although this works I am concerned that this may have unforeseen consequences.

Nothing has changed in that part of the code for awhile…

Pippin · Jul 10, 2016, 8:45 PM

Having a problem getting Bambenek "C2 All Indicator Feed" going.
I have tried to put it in DNSBL but get this in log when update:


[ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
 No Domains Found

Any ideas?

BBcan177 · Jul 10, 2016, 9:10 PM

@Pippin:

Having a problem getting Bambenek "C2 All Indicator Feed" going.
I have tried to put it in DNSBL but get this in log when update:
[ dnsc2allindicatorbambenek ] Downloading update  .. 200 OK
 No Domains Found

DNSBL
https://osint.bambenekconsulting.com/feeds/dga-feed.gz
https://osint.bambenekconsulting.com/feeds/c2-dommasterlist.txt

IP
https://osint.bambenekconsulting.com/feeds/c2-ipmasterlist.txt

Pippin · Jul 10, 2016, 9:37 PM

Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

The one that gives No Domains Found is:
http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

Or is it not suitable for pfB?
In text editor I see it`s different format then the rest.

BBcan177 · Jul 10, 2016, 10:13 PM

@Pippin:

Thanks, those I use without problem, only for dga-feed.gz I have dga-feed.txt.

The one that gives No Domains Found is:
http://osint.bambenekconsulting.com/feeds/c2-masterlist.txt

Or is it not suitable for pfB?
In text editor I see it`s different format then the rest.

It seems like that Feed is a mix of IPs and Domains…

The DNSBL parser is expecting the CSV line to be in a specific format. As you can see from your text editor, the CSV format is different between the two lists...

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists. The feeds that I listed above will work just fine as is...

I also recommend to use the .GZ feed, as that will save both BBC and yourself some bandwidth...

Pippin · Jul 10, 2016, 10:25 PM

Ok thanks, will adjust the feed to gz.

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

Ok but thanks for working on this, very nice.

Another thing, I forgot.
In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
Removing the line manually solves it, I should contact them?

BBcan177 · Jul 10, 2016, 10:34 PM

@Pippin:

Ok thanks, will adjust the feed to gz.

I would rather not add another function to the DNSBL parser as its just more overhead to go thru for all the other CSV formatted lists

Ok but thanks for working on this, very nice.

Another thing, I forgot.
In another feed is 127.0.0.1 listed and does not seem to work well with Squid.
Removing the line manually solves it, I should contact them?

Yes some feeds add RFC1918, and loopback addresses occassionaly… I've even seen 0.0.0.0 which is disasterous ;)

In the case of Firehol, that site updates those feeds once per day. I ususally update the Feeds more often depending on the frequency of updates for a particular Feed. A lot of Feeds make changes hourly... So getting a feed updated once per day, doesn't really do you justice, and I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…

Pippin · Jul 10, 2016, 10:46 PM

@BBcan177:

I recommend to add the Original Feed source directly into pfBlockerNG and not go thru a third-party to get a Feed.

Was thinking about that too now. Next time I have time enough will try to find the original ones.

Also note, that you can enable "Suppression" in the General Tab, which will remove all RFC1918 and loopback addresses automatically which will avoid this issue for the future…

Yeah I saw that but it`s not removing 127.0.0.0/8, 10.0.0.0/8 and 192.168.0.0/16.
0.0.0.0/8 is also on there (:

Will remove that list later, tomorrow another day.

theeddie · Jul 10, 2016, 11:06 PM

http://someonewhocares.org/hosts/hosts

Here is another advert list, this guy actually updates his. I have been VERY happy with it

BBcan177 · Jul 11, 2016, 9:56 PM

@theeddie:

http://someonewhocares.org/hosts/hosts

Here is another advert list, this guy actually updates his. I have been VERY happy with it

FYI - This, and other DNSBL Feeds are listed in this thread below: (Just in case you didn't see it before)

https://forum.pfsense.org/index.php?topic=102470.msg572943#msg572943
https://forum.pfsense.org/index.php?topic=102470.msg573159#msg573159

swedish-master · Aug 6, 2016, 7:27 AM

I have a problem when i use this my DNS stops to work out what am I doing wrong?

Alesk13Fr · Aug 7, 2016, 7:12 AM

Hello,

I'm encountering a problem since my update to PfSense 2.3.2.

I've reinstalled my PfSense Box 8 times in 3 days, each time where I'm using PfSense without PfBlockerNG all is fine, and when I'm installing PfBlockerNG, after few hours (30 minutes to 6 hours) my Box begin to be unaccessible, SSH and Serial, on serial I got a lot of lines of "swap_pager_getswapspace(X): failed".

**Material :
I'm using Lanner Box FW-7568B (spec here in 2 words the specs are :
Intel Atom Dual Core Pineview D-525
8 x GbE Ports (6 x Intel 82574L and 2x Intel 82541P1)
4 Gb DDR3 800 Mhz SODIMM (In fact it's 1 Gb on Motherboard and 4 Gb in SODIMM but the max used by system is 4 Gb)
SSD 128 Go SATA
Hitachi Travelstar 250 Go

**OS :
PfSense 2.3.2 AMD64 (built on Tue Jul 19 12:44:43 CDT 2016)
Full Install from USB Key, with Custom options, embed Kernel

**Interfaces setup :
I'm using a LAGG 8 x 1 GbE with 802.3ad switch behind (2 x Netgear M5300).
4 x WAN connection, all ADSL, 3 are fixed IP and one is dynamic.
All interfaces are on VLAN, just LAN is on LAGG0

**My Packages are :
Avahi : 1.11_2
Nut : 2.3.1
Notes : 0.2.9-2
Service_Watchdog : 1.8.3
PfBlokerNG : Before reinstall it was 2.1.1 after 2.1.1_2

**System tunables :
I'm using system tunables since this lot of crash for this parameters : kern.ipc.nmbclusters

I haven't modified my PfSense installation, I'm using my backuped config.xml who contains parameters for all my package listed upon, and for snort (I'm not using i since a lot of time)

The first time where this happen (10 days ago, with 5 days of balckout because I wasn't near of the box) on 2.3.1, with the update of PfBlokerNG 2.1.1 to 2.1.1_2, I was on vacation, and my Box become unaccessible, when I was back, I've seen my Box unable to boot after the "ldconfig" message during the boot process.

I've changed my first drive from SSD to HDD, to be sure it wasn't a failed drive problem (same if SMART was ok).

Can someone tell me what was wrong ? I'm not sure it's only a software problem, maybe hardware too or only, because my Box was up for 90 days (approx) without any problem and suddendly my problem begin with just PfBlokerNG update …
I don't understand why when PfBlockerNG was installed and did reload the configuration after installation process, my Box become slow specially for Rules and PfBlockerNG page from Web GUI, and for SSH and Serial too.

My config.xml don't have any "pf_*" rules, I've suppressed it manually for all my WAN interfaces, because latest backup (just before my precedent crash contain PfBlockerNG Rules), so I've clean it all PfBlockerNG related on rules, aliases URL, etc ... All my latest PfBlocker settings still on config.xml.

So if you can point me where my problem is I would realy appreciate ...

Thanks in advance.

Best regards,
Alex.**********

RonpfS · Aug 7, 2016, 7:35 AM

What do you see in System Log, pfblockerlog, Diagnostic System Activity, etc ?

Alesk13Fr · Aug 7, 2016, 8:04 AM

What do you need ?

I know top -aSH, system.log, but what other ?

The problem is, if the box was unnaccessible, I have no other way rebooting it, and after this, PfSense no longer boot, still blocked after system 32 ldconfig, just before loading fstab I assume, so if you know how to get back the information, i could give you a lot more … (I think too many process are writing, and finaly file system was corrupted, so I can't no longer mount the system, I've try by rescue mode from PfSense installation,w ithout success !)

I'll reinstall PfBlockerNG and wait for a crash and give you the results, juste let me know what's the best informations to keep before and after crash and Ill do !

Thanks in advance.

Best regards,
Alex.

RonpfS · Aug 7, 2016, 8:24 AM

The logs are located in /var/log/pfblockerng

Check to see if you have a loopback address with```
grep "^127" /var/db/pfblockerng/deny/*


When you restore the config, edit the config file first and change <enable_cb>on</enable_cb> to off, this way pfBlockerNG isn't enabled on reboot.

If you are using DNSBL, on restore a missing pfb_dnsbl.conf would prevent the Resolver from starting. You can :```
touch /var/unbound/pfb_dnsbl.conf

before the reboot in order to have unbound start and get Resolver service running.

Alesk13Fr · Aug 7, 2016, 9:41 AM

I don't know if this can help (I doubt) but on my SysLog Server, at the first day where my problem begin, I can see this :

2016-07-26	00:09:15	info		local7	dhcpd	171,16777216,,1000022611,lo0,match,pass,in,4,0x0,,64,21510,0,none,17,udp,72,127.0.0.1,127.0.0.1,21251,53,52
2016-07-26	00:09:15	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,7240,0,none,17,udp,69,81.210.11.173,212.27.40.241,22626,53,49
2016-07-26	00:09:15	info		local7	dhcpd	4747,16777216,,1429561533,lagg0_vlan30,match,pass,in,4,0x0,,100,5443,0,none,17,udp,58,192.168.191.245,192.168.191.250,8161,53,38
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(7): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(15): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(14): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(13): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(4): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(2): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(8): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(5): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(6): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(12): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(14): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(9): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:09:02	crit		local7	dhcpd	swap_pager_getswapspace(3): failed
2016-07-26	00:09:01	crit		local7	dhcpd	swap_pager_getswapspace(16): failed
2016-07-26	00:08:06	info		local7	dhcpd	4647,16777216,,1431955052,lagg0_vlan40,match,pass,in,4,0x0,,64,12387,0,DF,17,udp,63,192.168.194.1,192.168.199.250,37762,53,43
2016-07-26	00:08:06	info		local7	dhcpd	4747,16777216,,1429561533,lagg0_vlan30,match,pass,in,4,0x0,,100,5301,0,none,17,udp,58,192.168.191.245,192.168.191.250,8091,53,38
2016-07-26	00:08:06	info		local7	dhcpd	1656,16777216,,1770011086,lagg0_vlan91,match,block,in,4,0x0,,112,32706,0,none,17,udp,134,92.38.104.168,81.210.11.173,59402,38613,114
2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,20656,0,none,17,udp,69,81.210.11.173,212.27.40.241,39154,53,49
2016-07-26	00:08:05	info		local7	dhcpd	4714,16777216,,1429561478,lagg0_vlan10,match,pass,in,4,0x0,,64,0,0,DF,17,udp,88,192.168.190.114,23.234.53.67,26042,10001,68
2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,0,0,DF,17,udp,88,81.210.11.173,23.234.53.67,44638,10001,68
2016-07-26	00:08:05	info		local7	dhcpd	4714,16777216,,1429561478,lagg0_vlan10,match,pass,in,4,0x0,,64,0,0,DF,17,udp,88,192.168.190.114,23.234.53.61,26042,10001,68
2016-07-26	00:08:05	info		local7	dhcpd	178,16777216,,1000022712,lagg0_vlan91,match,pass,out,4,0x0,,64,0,0,DF,17,udp,88,81.210.11.173,23.234.53.61,44359,10001,68

This error from DHCPD only occur when PfBlokerNG is installed, I don't understand why …

oddworld19 · Aug 7, 2016, 12:12 PM

Out of swap space?

Too little ram?

Pfblockerng was starting to swap for me at 8 gigs, so I bought another 8 to be safe.