@Renat hello sir thanks for this thread it help me a lot. I have to observed this machine if error still exists. Thumbs up! ;)

AMD A6-6400K APU with Radeon(tm) HD Graphics
2 CPUs: 1 package(s) x 2 core(s)
AES-NI CPU Crypto: Yes (inactive)

I have 1 NIC card attached on my machine. Winyao E350T4 PCI-E X1 Quad Port 10/100/1000Mbps Gigabit Ethernet Network Card Server Adapter LAN I350-T4 NIC This is the specs the NIC card having 4 ports. I hope that the error be fixed. ;)

@Erly-Araújo it was on older version of pfsense https://www.netgate.com/blog/pfsense-2-4-1-release-now-available.html

"Truncated ELF file" => standard OS commands are unreadable.

Leave the disk as is.
Salvage config.xml
Reboot using a install device and install from scratch.

When you are asked to format the destination drive, do no go for quick one, but chose the non-default total format with check (I didn't re install pfSense on a physical disk, mine just wont die after nearly 10 years ...)

https://forum.netgate.com/topic/146189/crash-report-after-update

Thanks for the reply, but I think I got it all set and figured out.

After reading about the XG-7100's setup, I created VLANs for each of my LANs with the one LAGG, and then reassigned the interfaces to the new VLANs. Everything is all good now.

@kiokoman said in Locked out of WebGUI:

from the console using option 15

15) Restore recent configuration

or you can try

pkg delete pfSense-pkg-darkstat-3.1.3_4

you probably have to manually delete all reference to darkstat from the xml config later
or
reinstall everything

Thanks for your help.

I actually had tried that but only tried reinstalling the backup prior to installing Darkstat. What I didn't notice was that it had, for some reason, installed Darkstat about 4 times in a row. So I restored a configuration from last week and it worked and let me have access to the WebGUI. This seems like a weird happening.

I then restored a local backup and everything appears to be working again. I installed Darkstat again it appears to be working as well.

uhm 1.7.11 was my doing, a trivial patch to permit uppercase name for the tabs on status monitoring
https://github.com/pfsense/FreeBSD-ports/pull/662
idk but i don't think it can't be that
I just ran the same commands on my 2.4.4-p3 and i had same results of @Gertjan. so all fine here

@stephenw10 That is a perfect temporary solution for us! Now I can at least get back into my LDAPS and user configs. Thanks! I'm going to do some testing in our non production environment and see if I get get things syncing again. Thanks for your help with this

@pfsensenoobie
You need more than 4GB RAM in order to enjoy zfs's file caching. I have three pfSense boxes running with zfs and M.2 stripes. No problems so far. I think the greatest advantage of zfs is that you don't have to think about how you want to partition the drive.

In case of heavy storms, one cannot exclude the risks due to induction damages caused by lightning...

@kiokoman

yeah, i see the post now. why long time not fixed it?

alt text

@viragomann
Thank you so much again. Everything is working, after disabling the hardware checksum offload. :)

It depends on how you configure the hypervisor interface.

Unless you put VLAN 4095 on it the guest will see an interface with untagged traffic on the configured vswitch VLAN.

@KOM
but this reinstalls all installed packages, doesn't it?
I only need the missing ones.

With HPA you can hide memory from your operating system to over-provision the memory and increase its lifetime.

It looks to me that your SSD indeed got bricked. Even if you can get it to work again (e.g. reflash its firmware if that is even possible with that specific drive) I would not use it again for anything critical like a router.

I do not believe this happened due to a bug in pfsense. Updates are just very "hard" on disks compared to normal routing operation, so it could really just be a coincidence it broke during the update.

Ok, but what are you actually doing to get into 'safe mode' currently?

Have you unlocked the modem or replaced it's firmware? The second Ethernet port is not normally active on Openreach modems.

Is it still running in modem mode?
The only way you could connect two pfSense devices to the modem is if it's running as a router. In the default modem mode you use a PPPoE session from pfSense and you can't create two PPPoE sessions.

You should use just one pfSense box behind the modem connected via PPPoE and have two subnets on separate interfaces behind that. You can that have them fully isolated or allow connectivity between them as required.

Steve

This guide will get you going on how to create the VLANs you want.

https://docs.netgate.com/pfsense/en/latest/book/vlan/pfsense-vlan-configuration.html

You can then create firewall rules on each interface to restrict access outbound. By default, only the LAN interface gets a Default Allow rule that passes all traffic from LAN to anywhere. All other interfaces, ie your VLANs, will require at least one rule added in order for them to talk.

I would stick with pfB instead of pihole as you then only have one device to worry about, and if pfSense goes down then you have bigger fish to fry then adblocking, ha!

Bandwidth monitoring can be done with ntop or lightsquid, depending on if you want all traffic or just http/s.

https://www.youtube.com/watch?v=_jBufEhP_IU

You can do scheduling with pfSense but the interface is a little clunky, and you're limited to 15 minute intervals IIRC. You create a schedule and then create a firewall rule and link to it.