Recent posts

#1

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.

#2

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.

#3

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 |

#4

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

#5

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.

#6

26.7 Series / Re: Upgrade 26.1 to 26.7 - bnx...

Last post by newsense - September 05, 2026, 10:56:40 PM

Ok but that means the bnxt driver on 15.1 is broken for the Broadcom 57504 chipset and a ticket needs to be opened upstream.


While using the driver provided by the manufacturer clearly works it clearly has issues - nontechnical - that prevent its redistribution both in FreeBSD and OPNsense.

The best path forward here is to have the driver maintainers look into this issue by opening a FreeBSD ticket.


As soon as this issue is addressed upstream you can be sure the next OPNsense release will include the patch.

#7

26.7 Series / Re: os-vnstat: Interface?

Last post by defaultuserfoo - September 05, 2026, 09:15:59 PM

Thanks!  I don't think it can be unassigned, see pictures.

It seems to be working fine --- but is/was it a good idea to change the configuration file from the console first?

It seems that the instruction to do so may be a remnant from when there was no way to configure vnstat through the GUI.  Perhaps it interferes?

[!!! Upgrade your Bootloader after upgrading to 26.7 !!!]

#8

26.7 Series / Re: Confused by 26.7 upgrade

Last post by defaultuserfoo - September 05, 2026, 07:58:15 PM

And what is 'config.xml'?

Ehh... seriously... ?!?!

It's the file that holds your complete OPNsense configuration and can be easily downloaded for backup purposes via the webGUI so you can restore it in the current or new installation of OPNsense ;)

Yeah I download the configuration every now and then, but the file has a pretty long name I don't pay a lot of attention to other than always saving it in the directory designated for it.  Besides, 'config.xml' is a very generic name.  What do you think how many files with that name do you have?

And what are these items


o firewall: move config.xml default LAN allow rules to new rules GUI
o firewall: legacy rules pages move to plugin


in the change log supposed to tell me?  I'm not familiar with the format and the contents of a file with the generic name 'config.xml'.  I don't know where and how firewall rules are stored.  What's with 'default LAN'?  That entry doesn't tell me anything because it's incomprehensible and meaningless to me.

What are the 'legacy rules pages'?  I happen to have an idea because I migrated my rules.  After migrating, there were still the automatic rules left and I didn't dare to delete those.  Now I can't see them anymore, if they are still there.  Will they stay forever now?  If I hadn't migrated, that entry would also be completely meaningless to me.

Where do the release notes tell me that I can't en-/disable firewall rules without installing a plug-in?  That would have been a relevant information.

You have just hit a bad spot in time during the history of OPNsense in my opinion where a lot of migrations need to be done to be compatible with future source code upgrades or whatever it's officially called :
- ISC DHCP got moved to a plug-in.
Luckily migrating to either KEA or DNSmasq is pretty easy thanks to .CSV file exports for your Static DHCP Mappings.

Dunno, ISC DHCP is still there.  I was wondering if there is a way to migrate and hoping for one.  It would be very tedious and error prone to do it all manually.

Where in the release notes were we told that there is some kind of DHCP migration tool and how to use it?

- Firewall Rules (Leagacy) got moved to a plug-in.
Firewall Rules [New] is now the only Firewall Rules section and needs to be migrated indeed.
The official plan was before upgrading from 26.1 to 26.7 but luckily it's not that strict and can be done afterwards too!

A couple weeks ago I was told it'll be years before a migration is required.  I do hope it's still many years because if I'd have to migrate, I'd have to completely redo those installations because the migration tool doesn't work.  That would take a week or so.

- Port Forward just got renamed to Destination NAT.
So that was pretty easy :)

- Outbound NAT is going to be the new Source NAT from now on.
So this also needs migrating now.
The offical plan is during 26.7 and before upgrading to 27.1 next year, but maybe you can get away with doing that later on too... Dunno...

Yeah I noticed.  From my perspective, fortunately it was merely a change in naming.  I didn't do anything with source NAT.

And last but absolutely not least :
!!! Upgrade your Bootloader after upgrading to 26.7 !!!
However this is a FreeBSD thing and not OPNsense specific ;)

Upgrade the bootloader?  Was that mentioned anywhere?  Doesn't that work automatically?  How would I upgrade it?

Once we get all this stuff behind us I am sure the updates/upgrades will be a lot less hassle than they seem to be now :)

The firewall rules were a nightmare, and that was handled badly by not telling us that we don't need to migrate and that the migration will break all the rules.  Instead it was made to appear as a harmless migration, using that tool, taking a look at the export to see if it looks messed up or not, and importing it.  It looked fine and all the rules were broken after the import.

A big fat warning is required, but there was none, and there still doesn't seem to be one.

Good luck! with all of the above...

Thanks, to you too.

#9

26.7 Series / Re: Confused by 26.7 upgrade

Last post by defaultuserfoo - September 05, 2026, 07:27:51 PM

This is neither a consumer product nor a commercial solution. This is the community edition of an enterprise firewall. If you choose to use it, you need to educate yourself and read the release notes of every update before pressing the button. Community support relies on users doing their homework. Expecting enterprise-grade stability and active hand-holding without carefully reading the changelog misses the point of a community edition.

That the idea of 'community' --- whatever that idea might be --- is attributed to something doesn't mean that everyone who comes in contact with that something has to be educated to such an extend as, for example, to be able to read the very source code of all the components of a product like OPNsense.  Communities running (school) busses to transport residents (kids) usually do not require such residents (kids) to able to rebuild the engines of the very busses in order to use them, and they don't require the users of the busses to follow all the maintenance logs in detail in case a bus might have a flat tire or needs an engine rebuilt.  They don't even expect something like that from the bus drivers.

'Community' is a horribly overinflated word since a long time now such that it has become virtually meaningless.

There is only so much anyone can do.  Don't expect the bus drivers to rebuild the engines.  Don't expect the manufacturers of the busses to produce perfect busses the engines of which never fail.  And when someone suggests how the bus could be easier to use, don't just ignore his suggestion, and don't blame the user as uneducated and not sufficiently competent to use the bus.

Make it so that the bus driver can easily change a flat tire.  Make it so that everyone can understand the timetable.

Fortunately I don't need to use busses.  Last time I tried there wasn't even a timetable.  If there had been one, I probably wouldn't have been able to understand it.  These timetables are not for 'normal users'.  Busses suck.

#10

26.7 Series / Re: Wireguard vs. DNS resoluti...

Last post by oc - September 05, 2026, 07:25:22 PM

seems like I'm not the only one - 26.7: https://forum.opnsense.org/index.php?topic=52711.0

and a much older entry: https://forum.opnsense.org/index.php?topic=37223.0

I'll provide the requested diagnostic information shortly. Thank you!