"Recent posts
#1
Development and Code Review / Re: netflector available as pl...
Last post by UnicronHD - Today at 09:45:35 PMThanks for running the baseline. If it's just as flaky on plain Wi-Fi with no tunnel and no netflector, then it's Roon itself after a force-close, and there's nothing left to fix on the network side.
Good to know where things stand though. Peers fix discovery over WireGuard, but the phone needs a /24 on its tunnel address, otherwise it sends its endpoint announcement to itself. And the router has to drop 10.10.10.255 on the WireGuard interface, or it forwards the packet back into the tunnel and replies to the phone with ICMP. I'll put both into the docs, we'd never have found them without your captures.
Thanks again for all the testing. I'll prepare a new official release soon.
Good to know where things stand though. Peers fix discovery over WireGuard, but the phone needs a /24 on its tunnel address, otherwise it sends its endpoint announcement to itself. And the router has to drop 10.10.10.255 on the WireGuard interface, or it forwards the packet back into the tunnel and replies to the phone with ICMP. I'll put both into the docs, we'd never have found them without your captures.
Thanks again for all the testing. I'll prepare a new official release soon.
#2
26.1, 26,4 Series / Re: File truncated, kernel/bas...
Last post by Tearlach - Today at 07:30:55 PMFranco, I changed the system DNS queries from being forced down the VPN tunnels to using the WAN interface (Quad9 DNS over TLS). Lookups tested from clients and Interfaces -> Diagnostics -> DNS Lookup appear to function fine. Attempted updates again:
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 12:31:30 EDT 2026
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/232496 bytes
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 933 packages processed.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
After a LONG pause, with "Updates" tab showing rotating circle, I am presented with the option to install base 26.1.11 and kernel 26.1.11; current version of both packages is listed as 26.1.7, which "seems" incorrect, as I am running 26.1.11_10 already. The changelog being truncated is also concerning. So then I ran System -> Status -> Run an audit -> Health
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 12:50:25 EDT 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.7 is incorrect, expected: 26.1.11
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.7 is incorrect, expected: 26.1.11
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-isc-dhcp 1.0_6
os-nut 1.9_1
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.11_10 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***
OK, so the audit also indicates I'm running base and kernal 26.1.7 vice 26.1.11. I go back to the "Updates" tab and click on the Update box to install base 26.1.11 and kernel 26.1.11. Note says "There are 2 updates available, total download size is 168.5MiB. This update requires a reboot." Result:
***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 13:04:33 EDT 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.1.11-amd64.txz: ...............................[fetch: transfer timed out
fetch: /var/cache/opnsense-update/5484/base-26.1.11-amd64.txz.sig appears to be truncated: 0/1332 bytes] failed, no signature found
***DONE***
I'm stuck. No option to upgrade to 26.7, and my 26.1 software appears to have a problem. As best I can tell, DNS is functioning as expected. Franco, you mentioned IPv6 also. Is there anything specific I can check or diagnostic to run to try to narrow the problem down?
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 12:31:30 EDT 2026
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/232496 bytes
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 933 packages processed.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
After a LONG pause, with "Updates" tab showing rotating circle, I am presented with the option to install base 26.1.11 and kernel 26.1.11; current version of both packages is listed as 26.1.7, which "seems" incorrect, as I am running 26.1.11_10 already. The changelog being truncated is also concerning. So then I ran System -> Status -> Run an audit -> Health
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 12:50:25 EDT 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.7 is incorrect, expected: 26.1.11
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.7 is incorrect, expected: 26.1.11
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-isc-dhcp 1.0_6
os-nut 1.9_1
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.11_10 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***
OK, so the audit also indicates I'm running base and kernal 26.1.7 vice 26.1.11. I go back to the "Updates" tab and click on the Update box to install base 26.1.11 and kernel 26.1.11. Note says "There are 2 updates available, total download size is 168.5MiB. This update requires a reboot." Result:
***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.11_10 (amd64) at Sat Sep 19 13:04:33 EDT 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Flushing temporary package files... done
Starting web GUI...done.
Fetching base-26.1.11-amd64.txz: ...............................[fetch: transfer timed out
fetch: /var/cache/opnsense-update/5484/base-26.1.11-amd64.txz.sig appears to be truncated: 0/1332 bytes] failed, no signature found
***DONE***
I'm stuck. No option to upgrade to 26.7, and my 26.1 software appears to have a problem. As best I can tell, DNS is functioning as expected. Franco, you mentioned IPv6 also. Is there anything specific I can check or diagnostic to run to try to narrow the problem down?
#3
German - Deutsch / Re: Kein SMTP outbound
Last post by meyergru - Today at 07:04:47 PMNur kurz gelesen, klingt nach Standardproblemen:
1. Ist das Kabel-Modem wirklich ein Modem oder ein Router mit 192.168.0.x als Transfernetz dahinter? Hint: Reply-To und "Wann ist ein WAN ein WAN"?
2. Erfolgt der Zugriff auf den Port von hinter der OpnSense aus und auf die externe IP via DNS? Ist das die vermeintliche oder die richtige WAN-IP? Ist NAT Reflection an?
Je nach Antwort auf diese Fragen ist Bobs Frage eventuell sehr naheliegend. Ich empfehle ggf: https://forum.opnsense.org/index.php?topic=42985.0
1. Ist das Kabel-Modem wirklich ein Modem oder ein Router mit 192.168.0.x als Transfernetz dahinter? Hint: Reply-To und "Wann ist ein WAN ein WAN"?
2. Erfolgt der Zugriff auf den Port von hinter der OpnSense aus und auf die externe IP via DNS? Ist das die vermeintliche oder die richtige WAN-IP? Ist NAT Reflection an?
Je nach Antwort auf diese Fragen ist Bobs Frage eventuell sehr naheliegend. Ich empfehle ggf: https://forum.opnsense.org/index.php?topic=42985.0
#4
26.7 Series / Re: 26.7.4_1 very frequent net...
Last post by gaben22 - Today at 04:59:27 PMThank you for the answer, apologies for not mentioning above but I upgraded from 26.7.3_11 to this version and previously not seen this happening. I have that backuped, will restore that later, try out and see.
#5
German - Deutsch / Re: Kein SMTP outbound
Last post by Patrick M. Hausen - Today at 04:25:51 PMQuote from: RR on Today at 03:50:37 PMwenn ich das richtig verstehe, müsste das doch über die "Default allow LAN to any rule" abgedeckt sein. Grübel ...
Ja, ist es. Wenn kein Port-Forward/Destination-NAT auf LAN aktiv ist, weil das Port-Forward Priorität vor Firewall-Regeln hat.
#6
German - Deutsch / Re: Kein SMTP outbound
Last post by Bob.Dig - Today at 04:06:16 PMWillst Du mit deinem Wissensstand wirklich einen Web- und einen Mail-Server ins Internet stellen?
#7
German - Deutsch / Re: Kein SMTP outbound
Last post by RR - Today at 03:50:37 PMHallo Patrick,
wenn ich das richtig verstehe, müsste das doch über die "Default allow LAN to any rule" abgedeckt sein. Grübel ...
wenn ich das richtig verstehe, müsste das doch über die "Default allow LAN to any rule" abgedeckt sein. Grübel ...
#8
German - Deutsch / Re: Kein SMTP outbound
Last post by Patrick M. Hausen - Today at 03:21:53 PMWarum willst du für ausgehende Mails eine Portweiterleitung? Einfach "allow" auf LAN und fertig.
#9
26.7 Series / Re: Bug using Maximize Grid in...
Last post by nero355 - Today at 03:01:37 PMI have noticed this when looking at the Firewall Rules too, but considering the fact that there were changes applied between 26.7.3 and 26.7.4 it's pretty safe to assume the whole thing is still a bit under construction and will probably get more improvements in the future :)
So far I am just really happy with the fact that the Pop out/Maximize feature has been applied OPNsense wide in as many parts as possible and seems to be the way forward as a solution to offer us as much as screenspace as possible when looking at various data/settings/logs/etc...
Both my 1366x768 and 1920x1200 screens are now a lot happier than they use to be @ https://forum.opnsense.org/index.php?topic=51182.msg269919#msg269919 LOL! :P
So far I am just really happy with the fact that the Pop out/Maximize feature has been applied OPNsense wide in as many parts as possible and seems to be the way forward as a solution to offer us as much as screenspace as possible when looking at various data/settings/logs/etc...
Both my 1366x768 and 1920x1200 screens are now a lot happier than they use to be @ https://forum.opnsense.org/index.php?topic=51182.msg269919#msg269919 LOL! :P
#10
German - Deutsch / Kein SMTP outbound
Last post by RR - Today at 02:58:55 PMHallo Forengemeinde,
ich bin im Mai von Sophos zu OPNsense umgestiegen. Ich habe ein kleines Netzwerk.
siehe Anhang
Ich bekomme keine vernüftige Portweiterleitung auf den internen Mailserver mehr hin. Mails können empfangen werden, aber der Mailserver kann auf port 25 keine Verbindung mehr zur OPNsense herstellen.
siehe Anhang
Die Port-Weiterleitung sieht so aus:
siehe Anhang
Im Live-Log erscheint folgendes:
siehe Anhang
Was übersehe ich? Ich würde mich sehr über fachkundige Hilfe freuen.
Vielen Dank im Vorraus
RR
ich bin im Mai von Sophos zu OPNsense umgestiegen. Ich habe ein kleines Netzwerk.
siehe Anhang
Ich bekomme keine vernüftige Portweiterleitung auf den internen Mailserver mehr hin. Mails können empfangen werden, aber der Mailserver kann auf port 25 keine Verbindung mehr zur OPNsense herstellen.
siehe Anhang
Die Port-Weiterleitung sieht so aus:
siehe Anhang
Im Live-Log erscheint folgendes:
siehe Anhang
Was übersehe ich? Ich würde mich sehr über fachkundige Hilfe freuen.
Vielen Dank im Vorraus
RR
