Messages

Hi Franco,
I had a power outage a week or so ago which might have been the cause of the db corruption. Since rebuilding I have installed the smart utilities and the SSD is clean. The worst part is that opnsense-bootstrap process deletes the user accounts before it gets to the db so once it failed, it was DOA. My only remaining issue is restoring the config, did not restore my firewall rules and I cannot remember what I had set up for zerotier.

Thanks for your assistance,
Roger

Thanks but too late. Bootstrap nuked my credentials before it failed so I couldn't log in any more. It was still passing traffic at least so I could download a new iso file and rebuild the device. Restored xml backup and it is mostly back to it's original setup.

Tried running the opnsense-bootstrap command and it fails with a message:
"pkg: sqllite error while executing DELETE FROM packages WHERE id +3222 in file pkgdb.c:2296: database disk image is malformed"

Any solution to this other that a fresh install?

Thanks,
Roger

Tried to load smart tools on the box and it needs 23.7.7 which I don't have.

Tried to upgrade when the release came out and am receiving the following error:

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.6 at Tue Oct 31 11:26:52 PDT 2023
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 851 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (10 candidates): .......... done
Processing candidates (10 candidates): .......... done
Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 315.
Child process pid=79470 terminated abnormally: Abort trap
***DONE***

The health audit is 4115 lines long and too large to attach. Lot's of missing files and checksum mismatches.

Additionally, cannot get ssh to start. Likely related but not sure.

Any help would be appreciated. Let me know what additional info you would like.

Just ran through the update from the GUI and it worked fine.

I was able to get softether installed on my OPNSense box on the Protectli 4 port switch. From my Android phone I can connect to my home network via Softether and OPNVPN. While connected I can See camera's and sites on my LAN as expected. I cannot connect to the internet using the VPN. When I view the status of the connection in OPEN VPN, the IP is 192.168.0.181 and the gateway is showing as 192.168.0.182. It should be 192.168.0.1. Not sure where it is getting that address from. anyone have any ideas? Any questions I need to answer to clarify my setup?

Thanks,
Roger

Hopefully this is my last question.

I currently have softether running on a rpi. I have a Port forwarding NAT setting and a floating rule to allow 1194 UDP traffic in to any. Not sure if that is the correct way, but it is working. Once I configure SoftEther on the opnsense box, how do I direct the 1194 UDP traffic to the firewall instead of the rpi?

Thanks

OK, figured out where to enable softether so it can be started from the cli. Need help on why it is not showing up in VPN menu and how to make it auto start at boot.

I have installed softether package and it is not showing up in VPN and not running. How do I get it to start so I can configure it?

Currently running softether on a rpi. Have protectli arriving Monday to run opnsense on and would like to migrate softether from pi to opnsense. Has anyone done this and if so is there any documentation on how to set up opnsence to see the softether service? NAT, firewall rules etc?

SoftEther VPN 4.34 Build 9745 RTM (June 24, 2020)
All cumulative updates bellow are included.
Build 9745 beta is determined to be stable enough and is remarked as RTM.
The contents of the packages are exactly the same as Build 9745 beta.

Current RTM build of softether is 4.34.9745. Version in package repository is 4.29.9680-4. How does that get updated?