OPNsense Forum
Archive => 21.1 Legacy Series => Topic started by: yeraycito on April 21, 2021, 07:03:29 pm
-
I have outdatet a never versión by gui: opnsense dead
Internet: not working
Access opnsense by lan: not working
Access opnsense by ssh: connection refused
-
I updated 4 boxes today. All 4 went perfectly.
Are you able to see something on the console directly?
-
It has started to install the update, a small error window has appeared that has disappeared quickly, the installation, packages, base, firmware has continued and it has proceeded to the automatic restart without further errors
-
Console not working
Specials packages installed in opnsense: adguard, wireguard-kmod
-
Maybe broken FS or HDD. Any chance to plug in a display?
-
hardware without problems, I just reinstalled opnsense. as I said before I tried to access the console using putty without succeeding. Updating I got a small error window, before the kernel was updated, but it disappeared so quickly that I couldn't read the message. The update continued without any further errors and restarted automatically.
-
Update wireguard kmod plugin error?
-
Clean install of opnsense 21.1. No Adguard or wireguard installed. Upgraded without problems or error messages to 21.1.5. Probable cause of error: Updated wireguard-kmod.
-
I installed wireguard + adguard + wireguard-kmod and everything works perfectly. I still think the problem was when updating wireguard-kmod. By the way, the wireguard service is still stopped although wireguard-kmod is working perfectly. Another thing, the wireguard-kmod dns connection still doesn't go through Adguard even though Adguard listens to the wireguard interface.
-
The stack trace would have been helpful.
That being said kmod is experimental, mentioned nowhere in our official statements and AdGuardHome is from a community repository. Are you sure you are not placing too much risk on your installation coupled with the sequence of forum updates about your update experience?
Cheers,
Franco
-
...Are you sure you are not placing too much risk on your installation coupled with the sequence of forum updates about your update experience?
Cheers,
Franco
Personality profile: risk taker :-D
-
I mean it's fine, but I certainly can't sleep reading this and not being able to help because there is no verifiable clue as to what went wrong yet.
Cheers,
Franco
-
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.
-
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.
Don't have any stability issues with the OPNsense implementation of WireGuard. Can't say anything bad about the perfomance as the clients are maxing out their bandwidth.
-
...and it's not "the OPNsense implementation" of wg, but the offical version in GO, afaik...
-
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
-
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
-
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)