First of all, great that it started working!!
Right now, I need to figure out why it's still showing the TP-Link router login page even though I set up DMZ, changed the management port and management IP.
I think it might have something to do with the way how TP-Link is handling DMZ.
I don't see why it shouldn't... DMZ means all ports are open, not that the TP-Link "dissapears". It is still the gateway that pfSense "sees" and it's still doing NAT.
That worked. For some reason, when I initially told the setup to create a new certificate, it just created a private key and not the certificate. Jan 24 build however worked!
@nollipfsense
Did so. Now some of the participants in the bridged LAN aren't getting through and to the internet. Something is amiss with their parameters, etc. Plan is to take the bridge down, boot and start over with configuring the bridge.
3 out of 5 NIC's working fine. Just 2.... some times.....
The sleep it's referring to there is a sleeping thread rather than a system power state.
Yes comparing multiple crash reports is the next step here. If they are consistent it's probably a bug somewhere.
Steve
That appears to be a panic in the Realtek driver, so I'd start there. There is a package with a different driver (realtek-re-kmod-197.00) but it's anyone's guess if it helps on your hardware.
As for the performance loss, that is likely from the extra debug options we have enabled on development snapshots, though it's also possible it's related to the Realtek drivers.
@steveits This worked like a charm!!! I was getting worried when I wasn't getting any response back from the box after 20 mins. But this ran and completed without issues!!!!!
Cheers to netgate!
Nothing changed anywhere near booting or video in the FreeBSD src repo between then (or even slightly before/after), and I don't see anything relevant in the other repos either, so it's odd that it seemed to happen around then.
I followed the instructions in the link if you’re trying to update from a previous 2.7 development version.
It worked great.
The last two steps say go in Debug mode and check….
How do you get into Debug mode?
@jimp said in 2.7 Avahi missing interfaces:
The WAN interface is automatically excluded from Avahi because Avahi should not be run on a WAN.
Though these days with any interface being capable of acting in any role that doesn't make as much sense as it did in the past, it's primarily an anti-foot-shooting measure to make sure someone isn't exposing private data on a public link.
Should probably edit the Interface Action description to remove confusion.
[image: 1673446455739-avahi.png]
pfSsh.php is fine on PHP 8.1, the problem is in that code.
You can't blindly access multi-level arrays without initializing them properly anymore in PHP.
https://docs.netgate.com/pfsense/en/latest/development/php-config-arrays.html
You'll need to download and attach one of the crash dump files (e.g. textdump.tar.0, rename it to textdump.tar) or at least extract the text files from it and post their contents. The firewall should be offering to let you do this from the dashboard when you log back in after a crash.
The two most important parts are ddb.txt and msgbuf.txt which will have a lot more detail about the crash and why it happened.
@fireodo said in frozen pfsense, administration interface, openvpn...:
Flux capacitor
Yeah, doc, but we gotta cool it!
Thank you all for your intelligence of mind, and your responsiveness, long life to pfSense community.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.