Messages

So then how do we solve dpinger being stuck indefinitely for single WAN? Are you saying that isn't an issue?

Sent from my SM-S916B using Tapatalk

It is not PPPoE. It's IPoE (DHCP). And this is only single WAN. I'm guessing the problem with the multi-WAN being described here is the same as the one I'm having as they both use dpinger anyways. I'm reading other threads saying that this has been fixed a long time ago but apparently it is not.

I'm new to opnsense (coming from using pfsense for a very long time). So if I apply that patch now, do I need to "remove" it or something when the next version (the one that has this fix incorporated) of opnsense comes?

After an Internet outage, my WAN gateway does not go back up until I disable and re-enable it in the opnsense GUI. This has happened twice already and I see a lot of these in the logs since the Internet went down:

2024-07-23T08:32:34   Warning   dpinger   WAN_GW 8.8.4.4: sendto error: 65   

I don't have any custom time settings in the gateway. The only custom setting I have there is the monitor IP (8.8.4.4) and everything else is at their default.

Thoughts?

Got it. In the conf file:

1. Will I be able to see which version it is from? And is it best to create a new opnsense vm that's exactly the same version as my old corrupted opnsense VM?

2. Does it list all third-party plugins that I have installed? Aside from AdGuard Home, I'm pretty sure there are a few more third-party plugins that I installed but haven't used yet. I just want to make sure I'm not missing anything.

Do I need to reinstall all packages even after installing with the recovery xml?

Sent from my SM-S916B using Tapatalk

I also tried fixing the ufs fs:

https://cdn.discordapp.com/attachments/1271505834261614713/1271540560439541952/image.png?ex=66b7b5ed&is=66b6646d&hm=7777d32610eeb1cc0f9e01dae43fe4d59b4758ec48462719151f91294be6156f&

Then tried booting normally again and I didn't see the mounting warning anymore. However, it still rebooted like before and then I'm back to square one with the mounting warning/error.

Correct. The trim command is used to discard the blocks. Under Proxmox, you can even enable SSD emulation.

BTW: If /dev/vtbdp03 is only 7.1 of 54 GByte, the maybe it was not logging that caused the problem. But I do not know which partitions are used under UFS, so do not know it that one holds the log data.

Ok, I think I'm convinced to use ZFS on the VM. However, I need to have this corrupted VM running first so I can just copy the settings from the old to the new VM manually, side-by-side. Or can I use a UFS opnsense backup xml to reload the config in a ZFS opnsense?

These are the partitions in a UFS system:

https://media.discordapp.net/attachments/1271505834261614713/1271537474346287147/image.png?ex=66b7b30d&is=66b6618d&hm=8b8941d81ef22e5536dc55d384c91b787e610f4e9614211d3f68fd740733d484&=&format=webp&quality=lossless

I checked the size of /dev/vtbdp03 which is the freebsd-ufs partition and only 7.1G out of 54G is used.

Correct, ZFS on ZFS does not excatly help with performance, but OpnSense does not need disk performance and having an indestructible filesystem like ZFS is a plus - as you can see here.

Using something like cv4pve-autosnap prevents you from ever coming into the situation where you think: Damn, I wish I had done a snapshot before this. And it comes cheap if Proxmox is running on ZFS.

So ZFS on ZFS it is then. Do I still get the advantage of ZFS even if I just have one disk for Proxmox (copies = 2) and one vDisk for opnsense?

As for the thin provisioning concern, I have thin provisioning enabled on the Proxmox ZFS disk but I can't see an option for the opnsense VM vDisk so not sure what it is set to currently. No to thin provisioning on vDisks too if I want ZFS on ZFS?

Ahh, that makes sense.

I forgot to also mention that I forgot to take even a single snapshot of this VM! I'm new to Proxmox and opnsense (I'm a longtime pfsense user but I had enough of their BS) so forgive my noobness.

As for the reason why I chose UFS over ZFS for opnsense is because proxmox is already running on ZFS. According to my research, running a ZFS vDisk on a ZFS Proxmox OS is useless and redundant. Is this not the case?

Yesterday at around 12PM GMT+8, my whole network at home went down. I wasn't at home until now so I thought it was just an ISP issue. But then I checked my opnsense VM (proxmox hypervisor) and saw that opnsense was rebooting in an endless loop as shown here:

https://youtu.be/EovhQ0KbWnc

I forgot which version I am on but I last updated within a month or so, so it's pretty recent. I have cloud backups to my Google drive and for some reason the latest backup i see there is July 24, 2024. I don't remember making any changes since then so I guess that's fine if I need to restore from backup.

However, before restoring, I want to know what caused the issue in the first place so I'm good with troubleshooting this. I don't have a lot going there aside from having the AdGuard Home plugin running as a plugin and a couple of other plugins that I'm not yet actively using.

Thoughts?

After an Internet outage, my WAN gateway does not go back up until I disable and re-enable it in the opnsense GUI. This has happened twice already and I see a lot of these in the logs since the Internet went down:

2024-07-23T08:32:34   Warning   dpinger   WAN_GW 8.8.4.4: sendto error: 65   

I don't have any custom time settings in the gateway. The only custom setting I have there is the monitor IP (8.8.4.4) and everything else is at their default.

Thoughts?

@pfop did you have the same results?

Does this mean that I also don't need to enable PowerD in the opnsense settings?

Ok, that makes sense. Thanks for confirming!