"Recent posts
#1
Hardware and Performance / Re: Adapts to Marvell AQC113C-...
Last post by Seimus - Today at 02:00:37 AMYou can get it from pciconf
Code Select
# pciconf -llcvVBa aq1 | grep Version
VPD ro V1 = 'Bundle Version: 1.3.37'
VPD ro V2 = 'Fw Version: 1.0.124'
# pciconf -llcvVBa aq0 | grep Version
VPD ro V1 = 'Bundle Version: 1.3.37'
VPD ro V2 = 'Fw Version: 1.0.124'
#2
Hardware and Performance / Re: Adapts to Marvell AQC113C-...
Last post by pfry - Today at 01:23:35 AMI don't see a firmware blob. Any idea of the version on your device? The driver has:
...but I didn't look at where aq_log logs. I have a Linksys appliance (MX8500) with an AQC113 (I believe), and OpenWRT includes (instruction to acquire) a firmware blob (loaded by U-Boot), v5.6.5. I also didn't see a firmware loader offhand; I didn't check the OpenBSD or Linux drivers.
Code Select
aq_log("MAC F/W version is %d.%d.%d",
hw->fw_version.major_version, hw->fw_version.minor_version,
hw->fw_version.build_number);
...but I didn't look at where aq_log logs. I have a Linksys appliance (MX8500) with an AQC113 (I believe), and OpenWRT includes (instruction to acquire) a firmware blob (loaded by U-Boot), v5.6.5. I also didn't see a firmware loader offhand; I didn't check the OpenBSD or Linux drivers.
#3
25.7, 25.10 Series / Re: Hostwatch - high disk writ...
Last post by Slybunda - Today at 01:00:42 AModd thing is im still at around 800-900mb writes per day, mostly seems to be crowdsec and zfs.
is this normal or excessive?
is this normal or excessive?
#4
26.1 Series / Crowdsec LAPI not working for ...
Last post by Nephiria - Today at 12:54:01 AMHi All,
Can someone help? I'm stuck.
Everything seems to be working fine, but there's apparently a problem I can't solve.
Everything seems to be working fine, but there's one problem I can't seem to fix.
Perhaps someone has an idea why LAPI can't connect.
Thanks in advance.
Can someone help? I'm stuck.
Everything seems to be working fine, but there's apparently a problem I can't solve.
Everything seems to be working fine, but there's one problem I can't seem to fix.
Code Select
... time="2026-02-22T00:49:24+01:00" level=error msg="auth-api: auth with api key failed return nil response, error: dial tcp 127.0.0.1:8080: connect: connection refused"
time="2026-02-22T00:49:24+01:00" level=error msg="Get "http://127.0.0.1:8080/v1/decisions/stream?additional_pull=false&community_pull=false\": dial tcp 127.0.0.1:8080: connect: connection refused"
I read that it might be blocked, but I've already opened ports 8080 and 6060 on the LAN, and I've also configured floating-point access. I've opened ports 127.0.0.1, but that doesn't seem to have any effect. What I find strange, though, is that even though I've configured the internal LAN, it's still trying to send its requests to the looping device.Perhaps someone has an idea why LAPI can't connect.
Thanks in advance.
#5
26.1 Series / Re: fixing WIFI after 26.1 upg...
Last post by notspam - Today at 12:52:05 AM #6
German - Deutsch / Re: IPV6 Tunnel mit Route64
Last post by Swtrse - Today at 12:16:50 AMRoute64 bietet neben GIF auch Wireguard an.
Ev. Probier ich es mal damit.
Ich denke, nur das Problem liegt eher auf meiner Seite, weil es so aussieht, als ob der Kernel komplett aufhört, die Pakete zu verarbeiten. Ich sehe nach den 120 s nämlich nichts mehr, weder in den Logs noch sonst wo.
Ev. Probier ich es mal damit.
Ich denke, nur das Problem liegt eher auf meiner Seite, weil es so aussieht, als ob der Kernel komplett aufhört, die Pakete zu verarbeiten. Ich sehe nach den 120 s nämlich nichts mehr, weder in den Logs noch sonst wo.
#7
General Discussion / Re: Native NAT64 support
Last post by Napsterbater - February 21, 2026, 11:41:18 PMI would like to chime in, running the current latest version of OPNsense and Tayga,
Both on an iPhone and Android, Android on T-Mobile, iPhone on Verizon, both currently seem to be able to make and receive VoWiFi calls.
I'm going to do a little bit more prolonged testing.
I also feel Tayga has much better performance than it used to have, It used to limit nat64 throughput on the same hardware quite a bit, and now I'm able to max out my 2 Gbps internet service with NAT64 traffic, again on the same hardware.
I would still like to see the day of native built-in NAT64, but this is great improvements.
Both on an iPhone and Android, Android on T-Mobile, iPhone on Verizon, both currently seem to be able to make and receive VoWiFi calls.
I'm going to do a little bit more prolonged testing.
I also feel Tayga has much better performance than it used to have, It used to limit nat64 throughput on the same hardware quite a bit, and now I'm able to max out my 2 Gbps internet service with NAT64 traffic, again on the same hardware.
I would still like to see the day of native built-in NAT64, but this is great improvements.
#8
General Discussion / Re: sophos utm9 migration to O...
Last post by pjottrr - February 21, 2026, 10:36:29 PMwe did buy the business edition, but everything is already configured in HA proxy now, but thnx for the tip
#9
General Discussion / Re: sophos utm9 migration to O...
Last post by Monviech (Cedrik) - February 21, 2026, 10:34:52 PMJust fyi:
https://docs.opnsense.org/vendor/deciso/opnwaf.html
It's almost the same apache configuration and web application features as in UTM, and we support it fully in business support (if you ever need it).
If you want to stay mostly in community scope HA proxy is also fine.
https://docs.opnsense.org/vendor/deciso/opnwaf.html
It's almost the same apache configuration and web application features as in UTM, and we support it fully in business support (if you ever need it).
If you want to stay mostly in community scope HA proxy is also fine.
#10
Development and Code Review / Re: fatal uncaught error 26.1....
Last post by Diggy - February 21, 2026, 10:07:05 PMQuick side question regarding MTU:
When configuring an interface, the help says "If you leave this field blank, the adapter's default MTU will be used."
If the adapter is a LAGG and I specified an MTU in the LAGG's config, is that MTU used? In other words, what takes presidence with respect to an interface's blank MTU setting, the physical adapters' MTU, or the LAGG's MTU?
When configuring an interface, the help says "If you leave this field blank, the adapter's default MTU will be used."
If the adapter is a LAGG and I specified an MTU in the LAGG's config, is that MTU used? In other words, what takes presidence with respect to an interface's blank MTU setting, the physical adapters' MTU, or the LAGG's MTU?
