Recent posts

#1

General Discussion / Re: How do you handle drive fa...

Last post by Patrick M. Hausen - Today at 12:33:25 PM

The dashboard is preconfigured. Yes, it also needs a separate Linux/Docker device. And an agent on OPNsense.

Start here:

https://www.beszel.dev/

#2

26.1, 26,4 Series / Re: Fatal error: Uncaught Erro...

Last post by BigFreddy - Today at 11:42:30 AM

Does the said monitoring infrastructure would give an option to deliver alerts when the S.M.A.R.T percentage of usage is below a certain treshold via various messaging apps or SMS messages?

Scrutiny can send notifications to Uptime Kuma, which in turn supports dozens of different notification channels. Alternatively two channels named "Shoutrrr" and "Apprise", respectively seem to be builtin. I use Uptime Kuma - another Docker container, but once you have the fundamental infrastructure in place, a container more or less is cheap.

So, coming back, Raspberry Pi + Scrutiny should be efficient as a monitoring solution?

A monitoring solution for what? Scrutiny only monitors HDD/SSD drive and Zpool health. Not CPU/system temperature, memory, disk usage, fan RPM, reachability, ... etc. There are other tools for that. I am not aware of a single one stop solution that does everything in one product. But a Pi with Linux is a good platform to start with, IMHO.

Thanks for the recommendations, I checked out Uptime Kuma and it looks like a cool monitoring tool that's free to use. That's what I meant, the monitoring of HDD/SSD drive and Zpool health.

[Block private networks]

#3

General Discussion / Re: WAN out connection Issues

Last post by lmoore - Today at 11:27:55 AM

Reading information about Spectrum in the US, it appears your router is registered with them for you to receive your Internet service.

I will make the assumption the modem (EU2251) is operating as a bridge for your Internet connection.

It is unclear if your router (SBE1V1K) is using DHCP to connect you to the Internet. You can check this by using OPNsense WAN port and changing the MAC address to that of your routers WAN port and see if you receive a public IP address. Before doing this enable Block private networks  on your WAN interface.

If your router is using DHCP, in future you could connect it to your Cisco switch and keep your mobile devices working behind OPNsense - double-NAT will occur.

You've not mentioned setting any port forwarding in OPNsense (Destination NAT). If you have not configured any rules I would expect outgoing pings from OPNsense to work just as they do for your other devices on the SBE1V1K's LAN ports.

With your current set up and testing an endpoint connected to the Cisco switch, my suggestions are:

OPNsense:
 - Check Interfaces -> [LAN] ensuring Block private networks is not enabled (not ticked).
 - Add a network alias for the first SVI network on the Cisco switch in OPNsense: Firewall -> Aliases and set it to 10.11.120.0/24
 - Add a firewall rule for the LAN interface to allow inbound traffic for all protocols from the network alias (10.11.120.0/24) to any

Cisco Switch:
 - Verify ping to 10.11.110.1
 - Verify ping to 192.168.1.101
 - Verify ping to 192.168.1.1
 - Verify ping to 8.8.8.8
 - Verify ping to your public IP

If the above tests work, move on to testing from the endpoint on the 10.11.120.0/24 network.

Endpoint:
 - Verify ping to 10.11.110.2
 - Verify ping to 10.11.110.1
 - Verify ping to 192.168.1.101
 - Verify ping to 192.168.1.1
 - Verify ping to 8.8.8.8
 - Verify ping to your public IP

Hopefully this will work for you, or at least show you where the ping requests are failing.

[Edit] Added advice to block Private Networks on WAN port.

#4

General Discussion / Re: How do you handle drive fa...

Last post by BigFreddy - Today at 10:46:09 AM

You are welcome,

Its really nice, and seamless to integrate. Basically I have all my LCXs, and whole network (expect mikrotik) in there.

Pic Of OPNsense ZFS pool monitoring.


Regards,
S.

This looks quite useful, mind sharing any links or insights how you setup and built the dashboard? I presume that dashboard is hosted on a spare device with some sort of agent installed on OPNsense?

#5

26.1, 26,4 Series / Unable to update issue

Last post by JeffF - Today at 09:53:02 AM

I am running into an issue where my device has apparently lost the ability to obtain updates. I would appreciate any help or suggestions people may have. Thank you in advance. Update log is below.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.11_10 (amd64) at Sun Sep  6 03:47:57 EDT 2026
Fetching changelog information, please wait... done
Updating FreeBSD-ports repository catalogue...
Fetching meta.conf: . done
Fetching data: .......... done
Processing entries: .......... done
FreeBSD-ports repository update completed. 37819 packages processed.
Updating FreeBSD-ports-kmods repository catalogue...
Fetching meta.conf: . done
Fetching data: ..... done
Processing entries: .......... done
FreeBSD-ports-kmods repository update completed. 239 packages processed.
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/meta.txz: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.tzst: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.tzst: Not Found
Unable to update repository OPNsense
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: .. done
Processing entries: .. done
SunnyValley repository update completed. 14 packages processed.
Error updating repositories!
Upgrading package manager from version '2.7.5' to ''
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/meta.txz: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.tzst: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.tzst: Not Found
Unable to update repository OPNsense
Error updating repositories!
Updating FreeBSD-ports repository catalogue...
Fetching meta.conf: . done
Fetching data: .......... done
Processing entries: .......... done
FreeBSD-ports repository update completed. 37819 packages processed.
Updating FreeBSD-ports-kmods repository catalogue...
Fetching meta.conf: . done
Fetching data: ..... done
Processing entries: .......... done
FreeBSD-ports-kmods repository update completed. 239 packages processed.
Updating OPNsense repository catalogue...
pkg: Repository OPNsense has a wrong packagesite, need to re-create database
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/meta.txz: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/data.tzst: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.pkg: Not Found
pkg: https://pkg.opnsense.org/FreeBSD:15:amd64/26.1/latest/packagesite.tzst: Not Found
Unable to update repository OPNsense
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: .. done
Processing entries: .. done
SunnyValley repository update completed. 14 packages processed.
Error updating repositories!
***DONE***

#6

26.7 Series / Re: Confused by 26.7 upgrade

Last post by Patrick M. Hausen - Today at 01:47:02 AM

@Plethodon a very supportive conclusion. Thanks.

#7

26.7 Series / Re: Confused by 26.7 upgrade

Last post by Plethodon - Today at 01:41:32 AM

Some people are not aware, but it bears repeating:

In the context of the BSD licenses, the "as is" provision means that the software is provided without warranties, and the authors generally disclaim liability for issues, failures, or damages resulting from its use, including operational errors.

We try our best to describe the changes. The code is open so it also documents the changes in a straightforward (but still very technical) way. If you want more you may want to consider participating in this process: the documentation is open and the changelogs are open too.


Cheers,
Franco

Seems I unintentionally stirred up a lot of feelings about the upgrade.

First, it's safe to say that I failed to read the upgrade notes prior to upgrading. That's on me. And, in an odd way, it's a testament to the previous upgrades, which were so smooth that I never felt compelled to read the notes. That was my mistake.

Second, I can't speak to whether the release notes would have adequately prepared me for the big change, since I didn't read them. It sounds like some people were fine with the communication and some were not. In the future, I'll examine the release notes closely.

Thanks to the devs for all their work.

#8

General Discussion / Re: WAN out connection Issues

Last post by Tetra - Today at 01:30:59 AM

My end goal in the future is to have all my devices besides mobile devices behind OPNsense. Important note the Modem and ISP Router are equipment from Spectrum, so I have very limited control over them.

Modem:
-It has no management address I can find
-No
-I believe Bridge due to the ISP Router having a public IP
-Not that I can see
-The model # is EU2251

ISP Router:
-It doesn't have a explicit management IP, but I used the gateway IP from my desktop directly connected to it and I did get a page directing me you use my mobile app without any other UI options
-Not any true configurations
-I can only add/edit Port forwarding, IP Reservations, DNS Servers, UPnP, and Security Shield
-Preferably I don't want to take my ISP router out topology but if I have to then I will
-Model # is SBE1V1K

Cisco Switch:
-The Switch is connected to OPNsense LAN using a L3 interface. IP routing is enabled
-As of now I only have one VLAN setup on this switch with a SVI(only has a IP and description in config). The IP of the SVI is a 10.11.120.1/24 IP
-The DHCP pool gives the endpoints IPs with a DNS(OPNsense LAN IP) and Gateway(VLAN SVI IP)

OPNsense:
-Routing Table: (Of course these aren't my actual IPs and Subnets)
Internet:
Destination        Gateway        Flags    Netif Expire
default                192.168.1.1        UGS         re0
10.11.110.0/30      Link#2            U               re1
10.11.110.1               Link#3           UHS         lo0
10.11.120.0/24      10.11.110.2         UGS         re1
127.0.0.1                Link#3           UH            lo0
192.168.1.0/24    Link#1            U               re0
192.168.1.101        Link#3           UHS         lo0
-Automatic Source NAT mode (All these rules are auto generated)
 LAN | IPv4 | Source Loopback Network --> Destination Port 500 | Translate Source IP LAN Address
 LAN | IPv4 | Source Loopback Network --> Translate Source IP LAN Address
 WAN | IPv4 | Source Loopback Network --> Destination Port 500 | Translate Source IP WAN Address
 WAN | IPv4 | Source Loopback Network --> Translate Source IP WAN Address
-LAN rules
LAN | IPV4 | Direction: BOTH | ALLOW ANY | (Note: For now this is just for test and will change later)
LAN | IPv4 | Direction: BOTH | ICMP | ALLOW |

#9

General Discussion / Re: troubleshoot potentially b...

Last post by newsense - September 05, 2026, 11:42:25 PM

Do you see the flip flops when setting igc0 on 1000baseT ?

Is the appletv nic flopping if connected to the USW-pro-8 ? Try both auto negotiation and static on the switch side

#10

26.7 Series / Re: Network Driver Install

Last post by newsense - September 05, 2026, 11:30:53 PM

Download and install os-realtek-re and realtek-re-kmod packages from here

https://pkg.opnsense.org/FreeBSD:15:amd64/26.7/MINT/26.7/latest/All/

 Copy to a stick, move to the minipc box and install.

Once installed the nics should be available upon restart.

If you have a mix of Intel and realtek cards then use the Intel one as wan so you'll be able to install the driver and perform the upgrades a lot easier than fiddling around with a usb stick.