"Recent posts
#1
German - Deutsch / Re: Opnsense bei Update kaputt...
Last post by Patrick M. Hausen - Today at 07:33:03 AMWas meinst du mit "nur drei Einträge"? Da dürfen grundsätzlich gar keine aktiv sein. Wenn man Zeug aus dem FreeBSD Repo installiert, macht man sehr wahrscheinlich die OPNsense kaputt.
#2
German - Deutsch / Re: Opnsense bei Update kaputt...
Last post by Zapad - Today at 07:29:20 AM@Patrick
Danke, das hat was gebracht, zwar waren nur 3 Einträge die auf FreeBSD gezeigt haben uns sonst nichts, aber die habe ich deaktiviert und
nach mehreren pkg update/upgrage und bootstrap hat sich die Sense berappelt und ich bin jetzt fehlerfrei auf 26.7.
Danke, das hat was gebracht, zwar waren nur 3 Einträge die auf FreeBSD gezeigt haben uns sonst nichts, aber die habe ich deaktiviert und
nach mehreren pkg update/upgrage und bootstrap hat sich die Sense berappelt und ich bin jetzt fehlerfrei auf 26.7.
#3
General Discussion / Re: Periodic NIC issues (?) wi...
Last post by BrandyWine - Today at 07:10:49 AMI am not sure if .1q tagging in i226 is good or not. Best to always run latest NVM.
but this note below. Try disabling vlan tagging from offloading, this brings it back to kernel.
See if that helps.
Known Issues with Intel I226-V NICs and VLAN Tagging
VLAN Tagging Offload Problems
There are several reported issues when using Intel I226-V Network Interface Cards (NICs) for VLAN tagging offload:
Untagged Traffic Works: While untagged traffic typically functions without issues, tagged traffic often fails or is missing.
Intermittent Functionality: In some configurations, tagged networks may work intermittently or only under low load conditions. This can lead to unreliable network performance.
DHCP and Guest Traffic Issues: Problems are frequently observed with DHCP requests and guest traffic not functioning correctly across VLANs.
but this note below. Try disabling vlan tagging from offloading, this brings it back to kernel.
Code Select
ifconfig igc0 -vlanhwtag -vlanhwtso -vlanhwcsumWhere igc0 is your LAN port, but change it as needed.See if that helps.
Known Issues with Intel I226-V NICs and VLAN Tagging
VLAN Tagging Offload Problems
There are several reported issues when using Intel I226-V Network Interface Cards (NICs) for VLAN tagging offload:
Untagged Traffic Works: While untagged traffic typically functions without issues, tagged traffic often fails or is missing.
Intermittent Functionality: In some configurations, tagged networks may work intermittently or only under low load conditions. This can lead to unreliable network performance.
DHCP and Guest Traffic Issues: Problems are frequently observed with DHCP requests and guest traffic not functioning correctly across VLANs.
#4
General Discussion / Re: apc ups commlost
Last post by JediFonger - Today at 06:58:36 AMi honestly can't remember because i this setup is new and i coulda sworn it worked? maybe, but i was plugging it in at the same time i was upgrading to 26.7. maybe i dreamt it, i dunno if there logs to check.
it's not the UPS/cable because i can take my w11 laptop plug it in and everything is detected and APC UPS software can see it everything works 100% fine.
currently os-nut tool service isn't running, i assume it's supposed to run? i dunno. i haven't ever gotten this to work yet, but i suspect usbconfig not detecting the ups is probably a big issue.
it's not the UPS/cable because i can take my w11 laptop plug it in and everything is detected and APC UPS software can see it everything works 100% fine.
currently os-nut tool service isn't running, i assume it's supposed to run? i dunno. i haven't ever gotten this to work yet, but i suspect usbconfig not detecting the ups is probably a big issue.
Quote from: lmoore on Today at 05:27:49 AMI haven't made the switch to OPNsense 26.7 yet.
Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?
Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?
Have you ruled out the USB cable by using another known working cable?
Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.
#5
26.7 Series / Increased CPU usage from Crowd...
Last post by josephistired - Today at 06:09:46 AMAfter updating my firewall to OPNsense 26.7, I've noticed that the CrowdSec plugin appears to be using significantly more CPU (upwards of 100%) than it did before the update.
Has anyone else experienced this after upgrading, or is this a known issue with 26.7?
For reference, here's some information about my system:
OPNsense version:
OPNsense 26.7 (amd64)
CrowdSec version:
version: v1.7.8_1-6322745
Codename: alphaga
BuildDate: 2026-07-06_18:59:29
GoVersion: 1.26.4
Platform: freebsd
libre2: C++
User-Agent: crowdsec/v1.7.8_1-6322745-freebsd
Constraint_parser: >= 1.0, <= 3.0
Constraint_scenario: >= 1.0, <= 3.0
Constraint_api: v1
Constraint_acquis: >= 1.0, < 2.0
Has anyone else experienced this after upgrading, or is this a known issue with 26.7?
For reference, here's some information about my system:
OPNsense version:
OPNsense 26.7 (amd64)
CrowdSec version:
version: v1.7.8_1-6322745
Codename: alphaga
BuildDate: 2026-07-06_18:59:29
GoVersion: 1.26.4
Platform: freebsd
libre2: C++
User-Agent: crowdsec/v1.7.8_1-6322745-freebsd
Constraint_parser: >= 1.0, <= 3.0
Constraint_scenario: >= 1.0, <= 3.0
Constraint_api: v1
Constraint_acquis: >= 1.0, < 2.0
| Built-in optional components: datasource_appsec, datasource_cloudwatch, datasource_docker, datasource_file, datasource_http, datasource_journalctl, datasource_k8s-audit, datasource_kafka, datasource_kinesis, datasource_loki, datasource_s3, datasource_syslog, datasource_victorialogs, datasource_wineventlog, db_mysql, db_postgres, db_sqlite Excluded components: cscli_setup Hardware: hw.model: Intel(R) N200 If there are any additional logs or diagnostics that would be helpful, please let me know, and I'd be happy to provide them. Thanks! |
#6
General Discussion / Re: apc ups commlost
Last post by lmoore - Today at 05:27:49 AMI haven't made the switch to OPNsense 26.7 yet.
Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?
Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?
Have you ruled out the USB cable by using another known working cable?
Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.
Was Apcupsd communicating with the UPS just prior to the upgrade to 26.7?
Have you ruled out the USB port by plugging the cable in to other USB ports on OPNsense firewall?
Have you ruled out the USB cable by using another known working cable?
Another test is to disable Apcupsd and configure NUT to monitor the UPS using the UPS Type 'USBHID-Driver' and see if it is able to communicate with the UPS.
#7
Tutorials and FAQs / Re: [How-To] NPTv6 with dynami...
Last post by OPNenthu - Today at 04:41:16 AMWhat can we practically gain from that change?
#8
Tutorials and FAQs / Re: [How-To] NPTv6 with dynami...
Last post by Maurice - Today at 03:30:17 AM@OPNenthu
Interesting approach. But I'm pretty sure an NPT rule for a prefix which includes the WAN address will make services which run on OPNsense itself (like Wireguard) unreachable.
Interesting approach. But I'm pretty sure an NPT rule for a prefix which includes the WAN address will make services which run on OPNsense itself (like Wireguard) unreachable.
#9
26.1, 26,4 Series / IPv6 breaks after a while and ...
Last post by DWM89 - Today at 03:25:15 AMHi!
I was running opnsense 25 for a good while and everything worked fine, now i tried to update to the current version 26.1.11_10 and all seemed fine at first.
I still had to manually tell my WAN interface to reload so I could get a DHCP lease from my ISP but then I got an IPv4 address and an IPv6 address and routes/dns and I was finally happy (I tried upgrading from 25 to 26 twice in the past with the same result as now!).
i could ping IPv4 and IPv6 hosts and generally use IPv6 sites normally.
Then, a few hours later (maybe 2 or 3) i realize that my IPv6 is not working anymore!
But I still have an IP...forcefully renewing the WAN interface didn't help.
IPv4 traffic still works like a charm.
the last 2 times I tried this upgrade I ended up ditching 26.1 and reverted back to my older opnsense 25 because i couldn'T solve the problem.
I am annoyed by this because it is obviously something that changed from opnsense 25 to 26 since when i revert to a backup from before the upgrade it works again with no problem.
On a side note:
I get a static public IPv4 and a static /56 prefix from my ISP
EDIT:
my configuration:
opnsense VM running on TrueNAS scale with dual intel i-226 NIC directly passed through to the VM
previously working version: 25.7.11_9 (Commit 2e9ac2def)
I have WAN and LAN configured on the 2 NICs, WAN DHCP on v4 and v6
LAN uses Track WAN Interface for v6
I use ISC-DHCP for lan addresses and unbound for dns resolving
Could someone PLEASE help me with that issue?
Best regards
I was running opnsense 25 for a good while and everything worked fine, now i tried to update to the current version 26.1.11_10 and all seemed fine at first.
I still had to manually tell my WAN interface to reload so I could get a DHCP lease from my ISP but then I got an IPv4 address and an IPv6 address and routes/dns and I was finally happy (I tried upgrading from 25 to 26 twice in the past with the same result as now!).
i could ping IPv4 and IPv6 hosts and generally use IPv6 sites normally.
Then, a few hours later (maybe 2 or 3) i realize that my IPv6 is not working anymore!
But I still have an IP...forcefully renewing the WAN interface didn't help.
IPv4 traffic still works like a charm.
the last 2 times I tried this upgrade I ended up ditching 26.1 and reverted back to my older opnsense 25 because i couldn'T solve the problem.
I am annoyed by this because it is obviously something that changed from opnsense 25 to 26 since when i revert to a backup from before the upgrade it works again with no problem.
On a side note:
I get a static public IPv4 and a static /56 prefix from my ISP
EDIT:
my configuration:
opnsense VM running on TrueNAS scale with dual intel i-226 NIC directly passed through to the VM
previously working version: 25.7.11_9 (Commit 2e9ac2def)
I have WAN and LAN configured on the 2 NICs, WAN DHCP on v4 and v6
LAN uses Track WAN Interface for v6
I use ISC-DHCP for lan addresses and unbound for dns resolving
Could someone PLEASE help me with that issue?
Best regards
#10
Virtual private networks / Re: Problem migrating from Leg...
Last post by NevadaTech - Today at 02:19:48 AMSure enough, yesterday was a maintenance day. I took the main router down for 20mins. When I got home my VPN to the main site was offline. Tried a couple changes, nothing. Completely deleted the PSK and the Connection on both sides, restarted the VPN/IPSEC service on my side, rebuilt on both sides, and it connected.
Sadly, my home office also has a link to a remote site (not main) which has been up and working for weeks is now down.
Sadly, my home office also has a link to a remote site (not main) which has been up and working for weeks is now down.
