Recent posts

#1

26.7 Series / Re: update 26.7.1 to 26.7.2 fa...

Last post by Patrick M. Hausen - Today at 05:22:25 PM

OPNsense has been installing both legacy and EFI boot side by side for years. This is also the default in the standard FreeBSD installer.

I would do a clean reinstall. Something in your file system is severly broken.

If you have the time boot a live system and make sure (SMART, dd) the target drive passes at least basic tests.

If you must have this system up again, e.g. to copy the configuration file, drop to a shell and try "fsck -y".

#2

26.7 Series / Re: Interfaces: Virtual IPs: S...

Last post by lmoore - Today at 05:07:56 PM

Other mode VIPs are doing: they allow traffic to be routed *without any static routes*.

I wonder if the routing issue back then was to do with ARP.

Glad it's all working for you!

#3

26.7 Series / Re: Interfaces: Virtual IPs: S...

Last post by MK4L - Today at 04:59:59 PM

The truth is that he only want a "layer 2 only / traffic shaping box".

In my interpretation; they want a traffic shaping box, but they were unable to get (layer 3) routing to work they way that they expected it to, so they cobbled something together with a transparent bridge instead...

That was exactly the case, 10 years ago!
For the question about what the Other mode VIPs are doing: they allow traffic to be routed *without any static routes*. The system does not even generate dynamic routes for the Other mode VIPs, but routing works exactly like I expect it to.

Not sure what I did back then, but I have just completed the testing *now* and it worked!
No VIPs, only static routing and 2 manual Gateways.


Thank you all so much for your interest to help.

#4

26.7 Series / Re: 26.7 upgrade failure - ope...

Last post by franco - Today at 04:56:48 PM

> pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible

Looks more like you had a FreeBSD version of the package manager which gets immediately installed when operating the FreeBSD packages manually, which doesn't work for us as is.


Cheers,
Franco

#5

26.1, 26,4 Series / os-dnscrypt-proxy Usage

Last post by DEC740airp414user - Today at 04:40:51 PM

Are there alot of users that utilize this plugin?  Then configure https over dns?

  I've always used services similar to nextdns but am using dns over tls, since Opnsense unbound doesn't have the setup for https over dns. Even though unbound states it's there.   Maybe I am missing how to do that on an out of box Opnsense install

Or is it better for hardware to use dns over tls
Browsers to use https over dns?

If you use this plugin what is your reason and setup?
Thanks

#6

26.7 Series / Re: 26.7 upgrade failure - ope...

Last post by vplanida - Today at 04:39:56 PM

Sorry for slow replies.

I think we are in.

Health status:

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.7 (amd64) at Mon Aug 17 17:37:30 MSK 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
os-isc-dhcp 1.0_6
os-theme-vicuna 1.51
>>> Check locked packages
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
>>> Check for missing package dependencies
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for missing or altered package files
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.7 has 68 dependencies to check.
Checking packages: ..
ca_root_nss-3.124 version mismatch, expected 3.125
Checking packages: .......
dpinger-3.4 version mismatch, expected 3.6
Checking packages: ....
hostapd-2.11_3 version mismatch, expected 2.12_2
Checking packages: .........
openssh-portable-10.3.p1,1 version mismatch, expected 10.4.p1,1
Checking packages: .
openvpn-2.7.5 version mismatch, expected 2.7.6
Checking packages: .
opnsense-26.7 version mismatch, expected 26.7.2_2
Checking packages: ...
opnsense-update-26.7 version mismatch, expected 26.7.2
Checking packages: .............
php85-phalcon-5.16.0 version mismatch, expected 5.18.2
Checking packages: ...........
py313-duckdb-1.5.4 version mismatch, expected 1.5.5
Checking packages: ......
py313-sqlite3-3.13.14_10 version mismatch, expected 3.13.15_10
Checking packages: ..........
unbound-1.25.1_1 version mismatch, expected 1.26.0
Checking packages: .
wpa_supplicant-2.11_7 version mismatch, expected 2.12_1
Checking packages: . done
***DONE***
Went on and done another update trough dashboard to get to .2 version. It went through just fine.

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.7.2_2 (amd64) at Mon Aug 17 17:44:47 MSK 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.7.2 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.7.2 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
os-isc-dhcp 1.0_7
os-theme-vicuna 1.51
>>> Check locked packages
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
>>> Check for missing package dependencies
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for missing or altered package files
pkg: warning: database version 39 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.7.2_2 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***
To round it up, the problem may lay in realtek 1.0 plugin.
At that I have to leave (had to for 2 hours).

Thank you, Franco, for you help.

#7

26.7 Series / Re: update 26.7.1 to 26.7.2 fa...

Last post by knowHoff - Today at 04:32:34 PM

I've been reading through BSD forum and found this

So I just tried to switch the Bios setting from legacy to UEFI.
The system is booting now, but is not able to finish the booting process.

It stops here:

You cannot view this attachment.

Is it possible that there is a fault in the upgrade process that just overwrites legacy boot with UEFI boot?

Cheers

#8

26.7 Series / Re: update 26.7.1 to 26.7.2 fa...

Last post by knowHoff - Today at 04:10:12 PM

Thank you for taking the time to look at my problem.

This is the output of gpart show, please take a look at the picture.

You cannot view this attachment.

It seems that the partition table is still valid.

Do you know how to restore the bootloader on  BSD?

#9

26.7 Series / Re: Interfaces: Virtual IPs: S...

Last post by dseven - Today at 04:00:52 PM

The truth is that he only want a "layer 2 only / traffic shaping box".

In my interpretation; they want a traffic shaping box, but they were unable to get (layer 3) routing to work they way that they expected it to, so they cobbled something together with a transparent bridge instead...

#10

26.7 Series / Re: 26.7 upgrade failure - ope...

Last post by franco - Today at 03:57:54 PM

Ok, sorry, the mirror URL is still wrong.  This then:

# opnsense-update -up -a FreeBSD:15:amd64/26.7


Cheers,
Franco