Recent posts

#1
26.7, 26.10 Series / /var/log to RAM disk
Last post by waxhead - November 12, 2026, 11:40:37 PM
Hi,

Under system->settings->miscellaneous it is possible to select "use memory file system for /var/log"
the information says that if you use /var/log as a RAM disk the log data will be lost on a reboot.

Why? It sound trivial to rsync the memory based /var/log to physical disk on a scheduled reboot/shutdown and vice versa on boot.
Yes, data will still be lost on a crash / power outage , but for planned restarts I don't see why loosing log data would be necessary.
#2
26.7, 26.10 Series / Re: Safe triangles in UI
Last post by schasj - November 12, 2026, 10:41:34 PM
Quote from: Boxer on November 06, 2026, 10:33:05 PMIf the menu isn't expanded then yes it disappears. Ckick the arrow next to the OPNsense logo at the top left to expand it. Is this what you mean?

Yes, I've only used the collapsed menus so I wasn't aware that the expanded works as expected. So my request stands but it only applies to collapsed menus.
#3
26.7, 26.10 Series / Re: A bug in 26.7.9_1 with ali...
Last post by oc - November 12, 2026, 10:23:33 PM
Thanks for reporting this, @Nullman. I noticed the same today (coincidentally, I have tweaked my aliases over the last few days, and I have updated to 26.7.9 yesterday, and to 26.7.9_1 today - so I observed something feels different).

It would be very practical if this was reverted to what worked previously.

Thanks :)
OC
#4
26.7, 26.10 Series / Re: PPPoE over an unassigned V...
Last post by fanski - November 12, 2026, 10:14:17 PM
Quote from: franco on November 12, 2026, 08:38:54 PMThe order of the patching is wrong though:

> 4. upgraded to 26.7.9

As soon as you upgrade the local patches get lost.  The sequence is:

1. Update to 26.7.9.
2. run patch command once which does everything for you: # opnsense-patch 39cca4ca785

Yes, I didn't run the patch at all, I just did a dry-run to see the output (output was hunk 2 did not work in 26.7.1) and then did the upgrade and it directly worked but as I said, I did the same update yesterday and the result was different so I'm totally confused.

I installed the patch now and it still works.

Regards,

Fanski
#5
26.7, 26.10 Series / Re: issue with legacy firewall...
Last post by Andreas1 - November 12, 2026, 09:09:00 PM
Quote from: nero355 on November 10, 2026, 08:19:37 PM
Quote from: Andreas1 on November 10, 2026, 05:55:04 PMNow I have the current version 26.7.8_2 and no migration assistent anymore.
IIRC you don't even need it : Just Export and Import the Rules again and you are done ??

Deleting the old Rules can also be done via your config.xml I think ?

There was a similar topic a week ago : https://forum.opnsense.org/index.php?topic=53280.0

I tried it but it did not help. They are still marked as legacy rules. And most importantly the automatically generated rules are still in legacy and therefor aren't editable (cannot turn them off).

:(
#6
26.7, 26.10 Series / Re: FreeRADIUS MAC-Based Auth ...
Last post by mimugmail - November 12, 2026, 09:07:27 PM
I'll fix it tomorrow
#7
German - Deutsch / Re: OPNSense 26.7 - AdGuard Ho...
Last post by tangofan - November 12, 2026, 08:57:47 PM
Quote from: Patrick M. Hausen on November 12, 2026, 11:59:02 AMM.E. ist die OPNsense der ideale Ort für AGH. Wenn du gleichzeitig Dinge tun willst wie DOT/DOH blocken, alle Clients über den einen offiziellen Resolver zwingen, etc. dann macht das viel weniger Streß als mit Port-Forward zu einem weiteren System.

I werde mir auch nochmal Adguard anschauen, nachdem ich beim initialen Aufsetzen von OPNsense die genannten Paketkonflikte hatte. Aber das ist ja anscheinend jetzt mit der "Just AdGuard" Installationsoption kein Problem mehr.

Eine Frage zum Setup: Im Prinzip gibt es ja zwei Möglichkeiten, das Ganze Aufzusetzen (in meinem Fall mit Unbound):

1. LAN-Clients -> AdGuard -> Unbound -> Internet
oder
2. LAN-Clients -> Unbound -> AdGuard -> Internet

Ich benutze Unbound übrigens als DNS Forwarder (via DoT) zu quad9, da ich in den USA lebe und meinem hiesigen Internetprovider etwas weniger traue als einer Klapperschlange oder einem Skunk. Da wäre dann natürlich die Frage, ob man Unbound nicht gleich in der Kette weglassen kann und so etwas aufsetzt:

3. LAN-Clients -> AdGuard -> Internet (quad9)

Den Blocklist-Teil von Unbound sollte dann ja mit AdGuard gehen, oder? Gäbe es denn sonst noch einen Grund, Unbound beizubehalten?

Also meine Fragen wären: Zwischen 1. und 2. was wäre die zu präferierende Lösung und warum? Und wenn man 3. dazu nimmt, was wäre die insgesamt beste Lösung?

Vielen Dank schon im voraus für Antworten dazu.
#8
26.7, 26.10 Series / A bug in 26.7.9_1 with alias e...
Last post by Nullman - November 12, 2026, 08:54:32 PM
Clicking on edit alias on a firewall rule doesnt work in both 26.7.9 and 26.7.9_1. When i click on edit alias, it brings Firewall/Aliases page, but it doesnt pop up the edit window. Instead, i have to manually locate the alias and click edit pencil to make changes. Tested on latest version of Firefox and Google Chrome.
#9
26.7, 26.10 Series / Re: PPPoE over an unassigned V...
Last post by franco - November 12, 2026, 08:38:54 PM
Hmm, we didn't change much.  Just a bit of non-functional plumbing for PPP actually.

The order of the patching is wrong though:

> 4. upgraded to 26.7.9

As soon as you upgrade the local patches get lost.  The sequence is:

1. Update to 26.7.9.
2. run patch command once which does everything for you: # opnsense-patch 39cca4ca785

Given you're using igb perhaps you saw a side effect of https://github.com/opnsense/src/issues/329 which was introduced in 26.7.4 and fixed in 26.7.9 in the kernel. It's strange but it could be.

Nevertheless you should try the PPP deferral patch because I think we should go ahead with this.


Cheers,
Franco
#10
Announcements / Re: OPNsense 26.7.9 released
Last post by franco - November 12, 2026, 08:30:05 PM
A hotfix release was issued as 26.7.9_1:

o system: fix automation user scope set since validation was tightened