"Recent posts
#1
General Discussion / Re: netgate freebsd performanc...
Last post by Seimus - Today at 04:18:10 PMQuote from: Patrick M. Hausen on Today at 11:29:24 AMThat discussion even carried over to the TrueNAS forum.
What, why, how...
#2
General Discussion / Re: opnsense wont boot on APU2...
Last post by Patrick M. Hausen - Today at 03:54:47 PMReplace the SSD.
#3
26.7 Series / Re: PPPoE over an unassigned V...
Last post by franco - Today at 03:31:54 PMDid you install the patch and then upgrade to _3? It looks like the patch is not active which would explain it not working.
After doing a firmware upgrade patches are undone.
Cheers,
Franco
After doing a firmware upgrade patches are undone.
Cheers,
Franco
#4
General Discussion / opnsense wont boot on APU2 boa...
Last post by robertkwild - Today at 03:00:15 PMHi all,
Running opnsense on a pcengine APU2 board and been rock solid for years and years but all of a sudden it wont boot and i got the below of serial
```
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
, 41032026, 4103(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fa ed 8b 40 02 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
2027, 41032028, (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fb ed 8b 40 02 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
41032029, 410320(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fc ed 8b 40 02 00 00 00 00 00
```
let me know
Thanks,
Rob
Running opnsense on a pcengine APU2 board and been rock solid for years and years but all of a sudden it wont boot and i got the below of serial
```
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
, 41032026, 4103(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fa ed 8b 40 02 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
2027, 41032028, (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fb ed 8b 40 02 00 00 00 00 00
(ada0:ahcich0:0:0:0): CAM status: Auto-Sense Retrieval Failed
(ada0:ahcich0:0:0:0): Error 5, Unretryable error
41032029, 410320(ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 01 fc ed 8b 40 02 00 00 00 00 00
```
let me know
Thanks,
Rob
#5
26.7 Series / Re: PPPOE Connection Keep drop...
Last post by nicholaswkc - Today at 01:59:32 PMAnyone please help me on this. I can post the config here as request.
#6
Portuguese - Português / Re: Failover dual-WAN automáti...
Last post by lowalex - Today at 01:25:25 PMUma coisa que vale verificar é se o gateway da fibra volta efetivamente ao estado online depois da recuperação do link. No OPNsense, o grupo de gateways com a fibra no Tier 1 deve voltar a preferi-la quando ela estiver saudável, mas as sessões existentes podem continuar presas ao caminho anterior até serem restabelecidas. Também convém conferir os tempos de monitorização, os logs dos gateways e se o monitor IP da fibra responde de forma consistente. Se o gateway já aparece online, mas o tráfego continua a sair pelo 5G, vale investigar as rotas e as regras de policy-based routing. Consegues confirmar se, após reconectar a fibra, o gateway fica online imediatamente ou se demora a recuperar?
#7
26.7 Series / Re: 26.7.6: unbound (and syslo...
Last post by drobins1976 - Today at 12:52:56 PMI can confirm a similar problem with OPNsense 26.7.6 on Hyper-V.
My setup is a Windows 11 Hyper-V host with an AMD Ryzen 7 8745HS, and an OPNsense VM with 2 vCPUs and 4 GB RAM. Unbound has DNSSEC and the Python DNS blocklist module enabled.
After updating on 9 October, Unbound repeatedly exited with signal 11. The WAN connection remained up, but DNS requests to the router timed out. Direct internet access by IP still worked.
These are the crash timestamps recorded in the kernel log (BST):
- 09:01:57
- 09:02:03
- 09:39:15
- 09:49:58
- 09:50:15
- 10:40:20
- 10:44:44
The kernel messages were of this form:
pid 52844 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)
Restarting Unbound only restored DNS temporarily. Restarting the Windows host also did not stop the crashes; Unbound crashed again after the VM came back up.
I rolled back ONLY the kernel using:
opnsense-update -kr 26.7.4
The kernel installed successfully, then I rebooted OPNsense. The application and packages remained on 26.7.6. No resolver, blocklist, firewall or VM settings were changed as part of this recovery.
Before rollback:
FreeBSD 15.1-RELEASE-p4 stable/26.7-n284150-0a7d52ef8757
After rollback:
FreeBSD 15.1-RELEASE-p3 stable/26.7-n283949-083dc7025377
As of 10 October at 11:27 BST, the VM has been up for approximately 24 hours 34 minutes. Unbound is running, DNS lookups through the router succeed, and HTTPS through the router works. No Unbound signal-11 entries appear in the current system log, although it has rotated, so I cannot claim complete log coverage for the whole period.
One additional point: the normal update offer now includes both opnsense 26.7.6_3 and kernel 26.7.6, which would undo this workaround. I have not installed it.
This seems consistent with the Hyper-V kernel regression discussed here. I have not tested the 26.7.6-hyperv test kernel, and I have no crash backtrace because core dumps were disabled.
My setup is a Windows 11 Hyper-V host with an AMD Ryzen 7 8745HS, and an OPNsense VM with 2 vCPUs and 4 GB RAM. Unbound has DNSSEC and the Python DNS blocklist module enabled.
After updating on 9 October, Unbound repeatedly exited with signal 11. The WAN connection remained up, but DNS requests to the router timed out. Direct internet access by IP still worked.
These are the crash timestamps recorded in the kernel log (BST):
- 09:01:57
- 09:02:03
- 09:39:15
- 09:49:58
- 09:50:15
- 10:40:20
- 10:44:44
The kernel messages were of this form:
pid 52844 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)
Restarting Unbound only restored DNS temporarily. Restarting the Windows host also did not stop the crashes; Unbound crashed again after the VM came back up.
I rolled back ONLY the kernel using:
opnsense-update -kr 26.7.4
The kernel installed successfully, then I rebooted OPNsense. The application and packages remained on 26.7.6. No resolver, blocklist, firewall or VM settings were changed as part of this recovery.
Before rollback:
FreeBSD 15.1-RELEASE-p4 stable/26.7-n284150-0a7d52ef8757
After rollback:
FreeBSD 15.1-RELEASE-p3 stable/26.7-n283949-083dc7025377
As of 10 October at 11:27 BST, the VM has been up for approximately 24 hours 34 minutes. Unbound is running, DNS lookups through the router succeed, and HTTPS through the router works. No Unbound signal-11 entries appear in the current system log, although it has rotated, so I cannot claim complete log coverage for the whole period.
One additional point: the normal update offer now includes both opnsense 26.7.6_3 and kernel 26.7.6, which would undo this workaround. I have not installed it.
This seems consistent with the Hyper-V kernel regression discussed here. I have not tested the 26.7.6-hyperv test kernel, and I have no crash backtrace because core dumps were disabled.
#8
26.7 Series / Re: PPPoE over an unassigned V...
Last post by fanski - Today at 12:12:21 PMHi Franco,
unfortunately it seems the hammer was not big enough?!
The problem still exists after upgrading to 26.7.6_3 and with the patch installed.
Or should I have only upgraded to 26.7.5?
Regards,
Fanski
unfortunately it seems the hammer was not big enough?!
The problem still exists after upgrading to 26.7.6_3 and with the patch installed.
Or should I have only upgraded to 26.7.5?
Regards,
Fanski
#9
26.7 Series / missing wireguard automatic ro...
Last post by freejack - Today at 11:55:12 AMSetting up a new instance and following the Road Warrior tutorial I noticed routing issues for my wg peers (peers get a handshake, but cannot access). And System - Routes - Status did not show a route for the wg interface.
Ignoring the "There is no need to configure IPs on the interface. The tunnel address(es) specified in the Instance configuration for your server will be automatically assigned to the interface once WireGuard is restarted" note from the tutorial and adding the tunnel static ip config for the wg interface as well resolves the issue (route shows up in status, peer can access). While the interface edit dialog rejects an ip config for a tunnel, the assignment dialog allows it, so I entered it there.
Ignoring the "There is no need to configure IPs on the interface. The tunnel address(es) specified in the Instance configuration for your server will be automatically assigned to the interface once WireGuard is restarted" note from the tutorial and adding the tunnel static ip config for the wg interface as well resolves the issue (route shows up in status, peer can access). While the interface edit dialog rejects an ip config for a tunnel, the assignment dialog allows it, so I entered it there.
#10
General Discussion / Re: netgate freebsd performanc...
Last post by Patrick M. Hausen - Today at 11:29:24 AMThat discussion even carried over to the TrueNAS forum.
