Untagged Traffic ceased on LAN with 24.7.10_2

[tops4u]

Meanwhile there is 24.7.12 out... did anybody try?

[tsense]

Unfortunately the problem still exists in the current version. a rollback to version 24.7.9_1 works. However, that is not a solution either.

[cookiemonster]

Unfortunately the problem still exists in the current version. a rollback to version 24.7.9_1 works. However, that is not a solution either.

And repeating...

I have no deny rule on the Lan interface. There are only the standard 2 "allow all" rules ( IPV4 , IPV6 ).
And why does it work for X years with the rules only with the update not. Additionally others have similar problems ?

I've wondered for some time about OPNSense and if it is reliable to work with in all environments.

I'm using it primarily as a VM firewall. In that it seems to be 'not great but works'.

One culprit is now using an OPNSense VM with a hypervisor bridge which has a physical interface with multiple vlan assigned.

The hypervisor sets the PVID egress as untagged on the bridge and tagged for the vlans, which is as it is. However, the tagged vlan are visible as untagged inside OPNSense VM. And that's that. No docu pointing out what to do or not to do.

When using multiple vlan-id on a single bridge the only solution seems to be to create a bridge per vlan, which doesn't really make sense, but works.

I have no deny rule on the Lan interface. There are only the standard 2 "allow all" rules ( IPV4 , IPV6 ).
And why does it work for X years with the rules only with the update not. Additionally others have similar problems ?

Ermm. https://docs.opnsense.org/manual/how-tos/vlan_and_lagg.html
The manual for VLANs takes you to this URL which explains not to mix tagged and untagged traffic.
From this thread what I gather is that we have users who have not heeded the advice and have mixed traffic anyways. So far it has "worked" but not after an update. What might have happened is that the update has exposed the misconfiguration only.
p.s. I was one of those users for some time and it was also not giving me any trouble. Until I realised that one day (like with this update - if that is what it is) it was bound to catch me. So I fixed it, by reconfiguring to the recommended setup.

So the ideal course of action is to correct any remaining installations with mixed tagged and untagged traffic in an interface used with OPN, and then move to diagnose any other problems and thinking OPN is "reliable to work with in all environments."

The TLD. Mixing tagged and untagged has never been a supported configuration. Some setups will expose it in form of problems, others won't.
Expecting new versions to make it go away is an exercise in futility.
Correct your setup.

[tsense]

I don't have any mixed vlan traffic in my setup. But I also noticed that I no longer have internet connectivity when I update to a newer version. My setup is a CARP HA cluster with two machines. The backup machine has internet connectivity. However, the master node is not. When I roll back to version 24.7.9 it works without any problems

Currently running OPNsense 24.7.12 (amd64) at Mon Jan 20 11:08:24 CET 2025
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/sets/changelog.txz: Permission denied
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/meta.txz: Network is unreachable
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.pkg: Network is unreachable
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.txz: Network is unreachable
Unable to update repository OPNsense
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.

[cookiemonster]

I don't have any mixed vlan traffic in my setup. But I also noticed that I no longer have internet connectivity when I update to a newer version. My setup is a CARP HA cluster with two machines. The backup machine has internet connectivity. However, the master node is not. When I roll back to version 24.7.9 it works without any problems

Currently running OPNsense 24.7.12 (amd64) at Mon Jan 20 11:08:24 CET 2025
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/sets/changelog.txz: Permission denied
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/meta.txz: Network is unreachable
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.pkg: Network is unreachable
pkg: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/latest/packagesite.txz: Network is unreachable
Unable to update repository OPNsense
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.

So why are you posting on this thread that is/was about tagged/untagged traffic?

[tsense]

I saw that there were several problems starting with the subsequent versions 24.7.9. I have a similar problem in that I no longer have internet connectivity... Although the WAN traffic is not tagged. Internet access works permanently on the slave node. So it can't be a misconfiguration. Do you have an idea what I can check?

[cookiemonster]

I saw that there were several problems starting with the subsequent versions 24.7.9. I have a similar problem in that I no longer have internet connectivity... Although the WAN traffic is not tagged. Internet access works permanently on the slave node. So it can't be a misconfiguration. Do you have an idea what I can check?

Instead of latching to any thread with a reported problem, do a search and for your symptoms in case it has been posted already. If nothing found, create your own new thread with your setup, hardware, current version, what worked before, what changed and what is now not working. Add your diagnostics so far.
Try to avoid problem statements lacking andy technical detail. "internet is not working" is an example of what not to do as it just delays the time to resolve whatever problem exists.