pfSense Plus and SG-3100

stephenw10 · Mar 12, 2021, 3:21 PM

Yes, I did that on another test box that has never had pfBlocker installed and there are no default lists.

 UPDATE PROCESS START [ 03/12/21 15:20:15 ]

Clearing all DNSBL Feeds... 
** DNSBL Disabled **


===[  Continent Process  ]============================================


===[  Aliastables / Rules  ]==========================================

No changes to Firewall rules, skipping Filter Reload
No Changes to Aliases, Skipping pfctl Update

 UPDATE PROCESS ENDED

So if you are seeing lists it's because they already exist on your config and pfBlocker is using them.

What lists do you see?

Steve

SteveITS · Mar 12, 2021, 3:22 PM

The PHP dump has been replicated at the command line: https://redmine.pfsense.org/issues/11466#note-21

mcury · Mar 12, 2021, 3:24 PM

@stephenw10 said in pfSense Plus and SG-3100:

Yes, I did that on another test box that has never had pfBlocker installed and there are no default lists.
 UPDATE PROCESS START [ 03/12/21 15:20:15 ]

Clearing all DNSBL Feeds... 
** DNSBL Disabled **


===[  Continent Process  ]============================================


===[  Aliastables / Rules  ]==========================================

No changes to Firewall rules, skipping Filter Reload
No Changes to Aliases, Skipping pfctl Update

 UPDATE PROCESS ENDED
So if you are seeing lists it's because they already exist on your config and pfBlocker is using them.

What lists do you see?

Steve

If that is the case, the same lists that pfblockerng 3.0.0_15 has, because it was the last pfblockerng version installed.

mcury · Mar 12, 2021, 3:35 PM

@teamits found another way to trigger it.. not sure if it's the same problem, but try:

ssh to pfsense and type:
gpioctl 2 0

stephenw10 · Mar 14, 2021, 1:58 PM

@mcury said in pfSense Plus and SG-3100:

gpioctl 2 0

Hmm, interesting. Not the same issue though, php is not involved there:

Mar 14 13:52:52 	kernel 		pid 32606 (gpioctl), jid 0, uid 0: exited on signal 11 (core dumped)

Likely that's because the first GPIO device cannot be set like that. You can set a PWM duty there. It should not segfault though.

Steve

mcury · Mar 24, 2021, 3:03 PM

Any news about this issue?

#11466 latest update on 03/11/21, nobody is assigned to that task..

Searched for this PHP bug in https://bugs.php.net/ and couldn't find anything about this PHP interpreter error for ARM 32 bits and/or Freebsd..

stephenw10 · Mar 24, 2021, 9:51 PM

Nothing specific yet I'm afraid. We are looking at it though just no-one has been assigned in Redmine. Details will be on the bug report there as we confirm them.
We have a separate internal report we use until we have something useful to add publicly.

Steve

mcury · Mar 24, 2021, 9:55 PM

@stephenw10 Thanks Stephen.

I didn't know about the separate internal report.

bigchimpin · Mar 25, 2021, 3:53 PM

I can't believe I paid almost $500 for this router lol

mcury · Mar 26, 2021, 2:38 PM

There is one bug that the affected version is incorrect for the SG-3100 , #11473

Luketa · Apr 22, 2021, 5:07 PM

I continue with version 2.4.5_1 on the SG-3100
I saw that it came out of version 21.02.2, is it stable?

I plan to update this week from 2.4.5 to 21.02.2

NOCling · Apr 22, 2021, 5:13 PM

My SG-3100 runs nice with 21.02.2.

mcury · Apr 22, 2021, 5:25 PM

Same here, didn't try snort/suricata.
Running smoothly with pfblockerng-devel 3.0.0_16

NokkieF · Apr 22, 2021, 5:27 PM

@mcury still experiencing same kernel alerts here

Amarand · Apr 22, 2021, 5:31 PM

@luketa

There was a bug, during the standard upgrade from 2.4.5 to 21.02_2 (the hot fix), where the SG-3100 hung post-install with the triple-flashing-lights.

After connecting a serial console, and verifying no output, I power cycled the SG-3100, and it came back up fine, with the 21.02_2.

I upgraded from 21.02_2 to 21.02.2 (note the _ versus the .) yesterday, and it A) upgraded fine and B) has been running fine with no issues.

Please make sure you take a look at some of the persistent plugin related bugs associated with the 21.x line that are not present in the 2.4.5 code, to make sure you won't be impacted by these bugs, before you upgrade.

Edit: the SG-3100 comes with a serial cable, which you can connect up to a computer and run a serial terminal (like PuTTY or whatever), to watch the upgrade process. I'd recommend doing this, especially from 2.x to 21.x

mcury · Apr 22, 2021, 5:32 PM

@nokkief Can you share more details about your setup?
I've been testing for about 4 days, trying to crash the SG-3100 with high loads, and it seems to be pretty stable..

Are you using suricata/snort ?
Are you using pfblockerng-devel_3.0.0_16, and if so, what feeds?

NokkieF · Apr 22, 2021, 5:39 PM

@mcury
I am seeing this:

2021-04-22 19:30:04.062460+02:00 	kernel 	- 	pid 73327 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 19:15:03.967524+02:00 	kernel 	- 	pid 27459 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 19:00:03.889566+02:00 	kernel 	- 	pid 8141 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 18:45:04.012638+02:00 	kernel 	- 	pid 56654 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 18:30:03.934697+02:00 	kernel 	- 	pid 48931 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 18:15:04.057781+02:00 	kernel 	- 	pid 94150 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 18:02:36.622513+02:00 	php 	25838 	[pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
2021-04-22 18:00:04.180824+02:00 	kernel 	- 	pid 25987 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
2021-04-22 18:00:01.142905+02:00 	php 	25838 	[pfBlockerNG] Starting cron process.
2021-04-22 17:45:04.303922+02:00 	kernel 	- 	pid 79696 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped) ```
code_text

I am running the following packages
acme security 0.6.9_3
haproxy net 0.61_1
pfBlockerNG-devel net 3.0.0_16

Not sure how I can easily retrieve the lists I am using, but I am using quite a few.

mcury · Apr 22, 2021, 5:48 PM

@nokkief Those are the same errors I was getting before.
I'm suspecting that the number of feeds is causing the crash.

I would like to suggest you to remove pfblockerng-devel completely and reinstall.
There is an option "keep settings" in pfblocker that you shouldn't tick before package removal.

After that, save the pfsense xml configuration, edit it and confirm that there isn't a single entry for pfblockerng...
I'm saying this because the 'old feeds' from previous versions remained in my XML configuration.

After removing all the pfblockerng entries in xml, restore it, then reinstall pfblockerng.

I did add dnsbl_easylists feed after the wizard, for me it is enough.
You should add one feed at a time to test..

NokkieF · Apr 22, 2021, 5:50 PM

Thanks, I will give it a go later. See if I can make them go away. It might also be haproxy, but it might be worth a shot trying

stephenw10 · Apr 25, 2021, 11:55 AM

Yes, this looks like it's almost certainly php choking on a large list parsing function for as yet unknown reasons. Loading fewer or smaller lists in pfBlocker will likely avoid it.