@bradsm87 said in October 26 snapshot bugs:

If there is another better way I should be reporting issues, please let me know. I presumed that netgate staff would monitor the forums and create redmine issues as needed.

That can happen sometimes, but the better way is to create the Redmine Issue yourself if convinced you have indeed uncovered a bug.

It may be that your issue is restricted to a limited set of hardware, so providing a list of what you are running pfSense on can be helpful. If this were a widespread bug impacting many different hardware platforms, you would expect to see more posts about it.

@jimbob-0

I got it. Of course I kept searching and poking around for possible solution.

Had to set the Update for PFSense back to Stable Version. NUT installed just fine after that.

@TyphooN:
I don't have the Traffic Graph widget enabled on the dashboard of my test virtual machine, but I am able to successfully view stats by using STATUS > TRAFFIC GRAPHS.

Your problem is almost certainly related to having the admin account disabled and depending on permissions assigned to other user accounts.

There are still several PHP 8.1 related bugs in the pfSense 2.7.0-DEVEL GUI code. The Netgate team is fixing them as they are discovered and they have time to get them done. Around a month or so ago they moved 2.7.0-DEVEL from FreeBSD 12.3-STABLE to FreeBSD-CURRENT (which is 14.0) and also upgraded the PHP engine from 7.4 to 8.1. The move to PHP 8.1 is what has generated all of the PHP errors because 8.1 changed what were formerly just notices and warnings to full-blown errors.

You can dive in and play with PHP code yourself, or wait for the Netgate team to fix the issue you reported via Redmine.

Okay, having done a little digging, and hand-editing, I have haproxy running in a very quick and dirty way.
First I edited /usr/local/pkg/haproxy/haproxy.inc and changed lines 1284, 1285 and 1298 to:

$serverprefix = (new haproxy_utils)->haproxy_hostname_get_prefix($be['address']); $serveraddress = (new haproxy_utils)->haproxy_hostname_strip_prefix($be['address']); if ($addrprefix && $serverprefix && $serverprefix !== $addrprefix) { continue; // skip the server if its not 'usable' in this transparent-backend } if ($be['forwardto'] && $be['forwardto'] != "") { $unix_socket = true; $servers[] = "/{$be['forwardto']}.socket send-proxy-v2-ssl-cn"; } else { if (in_array($serverprefix, array('unix@'))) { $servers[] = $serveraddress; } elseif (is_ipaddr($serveraddress) || $use_haproxyresolvers) { $servers[] = $serveraddress; } elseif (is_hostname($serveraddress)) { $dnsresult_servers = (new haproxy_utils)->query_dns($serveraddress, $dnsquerytype);

(The change is to replace haproxy_utils:: with (new haproxy_utils)-> which seems to work just fine)

I'll also note this in the ticket.

Or try re-installing 2.6 and upgrading to 2.7 again. See if the problem is at least repeatable.

If you enable a serial console you can get the full boot output that way. Otherwise you can get the dmesg output and /var/log/dmesg.boot via ssh.

Steve

@stephenw10 Has been rebooted and no errors during boot that I can catch. I only have the vga console access to the appliance. I have no lan access which makes for more difficult troubleshooting.

I have since trashed the installation and will take another run at it next week (it's Canadian Thanksgiving this weekend).

Ted Quade

OK, it wasn't the <lagg> section of the config that was the problem, but the <vlans> list being empty.

I put in a fix: https://github.com/pfsense/pfsense/commit/960388e0dbd4ab2c4ac96c8709dcdcb27460b1bc

@jimp said in colored separators in more places?:

The separators use bootstrap colors (something like info, success, warning, or whatever) so they are limited to those four. Not sure what it might take to expand that without a lot of extra effort.

You're too fast ;) Just wanted to add, I know those are the predefined bootstrap sets and having them in more areas would be a much higher priority. And I know, there has to be some backend code to service those new seps, as they are managed in their own config.xml array etc. etc. So yeah, I'm sure there are more pressing matters, would be nice to add at least to the other NAT tabs though sometimes.

But it would be great to just have a "sort of" alternative colors, so defining like bg-danger2 (a dark violet perhaps as a sort of darker red) and bg-info2 (with a cyan/bluegreenish like coloring) as well as a bg-warning2 (simply orange) would go a long way to help.
Just an idea as the bootstrap bg-xy's should be relatively easy to add to the stylesheet. :)

edit: If I'm not mistaken, the colors are simple CSS blocks in /css/pfSense.css, so one could simply sneak 2-3 new ones in there, too and just try them out ;) Would need a little bit of frontend code for the new color-blips for the selector, but saving the bg-xy value should be safe and selecting it from the stylesheet if it's in there should be pretty straightforward. :)

I guess the problem is potentially here in firewall_rules.php. I'm missing a rewriting to "address" instead of "network" here.
Also all the rules - if multiple are selected - get the same (int)microtime(true).
An additional array_cnt of the $_POST['rule'] would be easy to add, then if >1 simply add +1 to microtime every time the foreach hits.

} elseif (isset($_POST['dstif']) && !empty($_POST['dstif']) && isset($iflist[$_POST['dstif']]) && have_ruleint_access($_POST['dstif']) && is_array($_POST['rule']) && count($_POST['rule'])) { $confiflist = get_configured_interface_list(); foreach ($_POST['rule'] as $rulei) { $filterent = $a_filter[$rulei]; $filterent['tracker'] = (int)microtime(true); $filterent['interface'] = $_POST['dstif']; if ($_POST['convertif'] && ($if != $_POST['dstif']) && in_array($_POST['dstif'], $confiflist)) { if (isset($filterent['source']['network']) && ($filterent['source']['network'] == $if)) { $filterent['source']['network'] = $_POST['dstif']; } if (isset($filterent['destination']['network']) && ($filterent['destination']['network'] == $if)) { $filterent['destination']['network'] = $_POST['dstif']; } if (isset($filterent['source']['network']) && ($filterent['source']['network'] == ($if . 'ip'))) { $filterent['source']['network'] = $_POST['dstif'] . $ip; } if (isset($filterent['destination']['network']) && ($filterent['destination']['network'] == ($if . 'ip'))) { $filterent['destination']['network'] = $_POST['dstif'] . $ip; } } $a_filter[] = $filterent; } if (write_config(gettext("Firewall: Rules - copying selected firewall rules."))) { mark_subsystem_dirty('filter'); } header("Location: firewall_rules.php?if=" . htmlspecialchars($_POST['dstif'])); exit; }

OK, the errors you saw should be fixed on future snapshots.

https://github.com/pfsense/pfsense/commit/0d121100f17790fe12a44ea0edb8026ad626fb4b

@jimp said in AES module not loading?:

We're still working on that one. AES-NI is now in the kernel, and the output of pciconf changed so it isn't detecting loaded devices properly, so that's all a bit in flux. We haven't decided if we're keeping AES-NI in the kernel or moving it to a module, but either way the dashboard reporting is broken for the time being for everything.

Alright, had a hunch it's that one :) Thanks to clarify just wanted to report it so it won't go unnoticed ;)

@jimp said in Service installation problems / service widget display(?) bug:

https://github.com/pfsense/pfsense/commit/ade64ca64752c23ccec69640397aa034c648da85

Checked this, too - works as expected!
Services show up when enabled and configured properly and show their status again :)

Thanks again

@jimp said in ntp won't find peers:

https://github.com/pfsense/pfsense/commit/941eca9a6fe02cda70a4c5b5697fd6c0f6e2c3a9

Can confirm that works. After restarting, NTP immediatly pulls pool servers into the mix and connects to peers :)
Great!

BTW:

How do i close a Thread?