Update 21.1.5 dead opnsense

[franco]

I still think the problem was when updating wireguard-kmod.

Look I'm not claiming anything. The kmod suspicion was yours. I'm saying wireguard-go will not panic the kernel as easily just by mere maturity of the code and it being userspace.

As a side note, if I understand Michael correctly Jason may discontinue the wireguard-go route now that wireguard-kmod is available. This isn't the geatest news IMHO, but we will have to wait and see.


Cheers,
Franco

[mimugmail]

Dangerous? I don't think so. Adguard works much better than Sensei and without consuming any hardware resources unlike Sensei. Wireguard-kmod works much better than the Opnsense implementation of wireguard. Much more stable and with far superior performance.

Dont use -kmod, its marked as Experimental everywhere, No matter about performance or stability

[homenetworkguy]

Not to hijack the thread, but I upgraded to 21.1.5 and experienced an odd issue. I did not experience a dead OPNsense but I was not able to log into the web UI. The routing/firewall functionality seemed ok and the Internet and various accesses to other networks seemed ok. I could not SSH into the box from another VLAN but I could SSH within the same network. I rebooted the machine, still no luck.

So I connected my OPNsense box up to my KVM (since I do not normally need direct access to the box). I only saw a blank display (perhaps since I did not boot with a monitor). I then rebooted the machine so I can take a look at what was going on more easily. After rebooting the machine, I could see the login prompt and I realized that I could now access the web UI. The problem resolved itself after I connected a display/mouse/keyboard and rebooted.

I never experienced anything like it before since using OPNsense in late 2017. I saw in the notes that there was a change to the installer and some mention of migration of the Phalcon framework so not sure if there was a hiccup but I'm glad it recovered. I tried looking at a few logs but did not see anything that stood out. I thought I would mention the issue I had in case someone else had such a unique experience... (I also immediately made a configuration backup since I realized I had a slightly out of date one... just in case)