Recent posts

#1
General Discussion / Re: Periodic NIC issues (?) wi...
Last post by meyergru - Today at 09:12:18 AM
That really looks like link flapping to me which may indicate a flaky connection to your modem or ONT.
#2
General Discussion / Re: Unbound DNS keeps crashing...
Last post by meyergru - Today at 09:07:45 AM
Queries for what names? Also, there are some settings on "Services: Unbound DNS: Advanced" that should NOT be applied, like "Strict QNAME Minimization" - there are warnings in their help texts.

#3
General Discussion / Re: Periodic NIC issues (?) wi...
Last post by OPNenthu - Today at 09:06:13 AM
Quote from: meyergru on July 14, 2026, 09:43:14 AM1. There are chip revisions (e.g., the latest ones have a smaller structure width and consume less power). You can see that via " pciconf -lv | grep -B3 igc", look at the "rev" value (mine is 0x04 on my current china box, I have others with 0x03).

Mine is rev 04.

Already on the latest available coreboot from Protectli (has no in-BIOS ASPM options), but I added the following tunables:

hw.pci.enable_aspm=0
dev.igc.0.eee_control=0
dev.igc.1.eee_control=0
dev.igc.2.eee_control=0
dev.igc.3.eee_control=0

Just a note to anyone adding the EEE tunables, your NICs may lock up when you apply them.  Mine did.  With the serial console I was able to see the following in dmesg:

[5872] igc1: link state changed to DOWN
[5876] igc1: link state changed to UP
[5876] igc1: link state changed to DOWN
[5880] igc1: link state changed to UP
[5996] igc1: link state changed to DOWN
[5999] igc1: link state changed to UP
[6042] igc1: link state changed to DOWN
[6046] igc1: link state changed to UP
[6047] igc1: link state changed to DOWN
[6048] wg1: loop detected
[6048] wg1: loop detected

A reboot command from console brought everything online again.

Will see how it goes with this configuration (mind: still on the original 2.13 NVM) however early indication is that there is no improvement.  Still getting sporadic dpinger losses on the gateways.

The 'igc_aspm' test kernel is still active.
#4
Das ist die richtige Lösung, es verhindert das dnsmasq alle sockets (:53) bindet.
Jetzt binden dnsmasq und dhcrelay nur selective sockets die sich nicht überlappen sollten. (z.b. 192.168.1.1:53 und 192.168.2.1:53...).
#5
German - Deutsch / Re: Dnsmasq + DHCPv4 Relay gle...
Last post by Syosse - Today at 08:57:07 AM
Ich glaube, ich konnte das Problem lösen. Es hat lediglich die Option ,,Strict interface binding" bei Dnsmasq gefehlt.

Seitdem laufen beide Dienste problemlos parallel.

#6
German - Deutsch / Dnsmasq + DHCPv4 Relay gleichz...
Last post by Syosse - Today at 08:25:53 AM
Hallo zusammen,
ich migriere aktuell eine FortiGate auf OPNsense und habe folgendes Setup:

Dnsmasq als DHCP-Server für mehrere VLANs.
Ein AD-Client-VLAN soll per DHCP-Relay an zwei Windows-Domain-Controller weiterleiten (für dynamische DNS-Registrierung).
Sobald der DHCPv4-Relay-Dienst aktiv ist, startet Dnsmasq nicht mehr.
Deaktiviere ich das Relay, läuft Dnsmasq problemlos.

Meine Fragen:
Wie würdet Ihr das lösen, laut recherche habe ich folgendes gefunden:

Dazu sollte ich eine Custom-Config anlegen und folgende Einträge hinzufügen:

mkdir -p /usr/local/etc/dnsmasq.conf.d

Anschließend z. B. eine Datei mit folgendem Inhalt erstellen:

dhcp-relay=10.125.16.1,10.125.4.11
dhcp-relay=10.125.16.1,10.125.4.12


Welche Variante nutzt ihr in der Praxis zuverlässig oder habt Ihr eine andere Idee?

Dnsmasq


Dashboard


DHCRelay



Vielen herzlichen Dank!
#7
26.1, 26,4 Series / Re: Large number of files accu...
Last post by franco - Today at 08:17:33 AM
Hi Larry,

Ad found the bug that leaves the temp file when the command crashed:

# opnsense-patch https://github.com/opnsense/core/commit/9b0767001e
# service configd restart

The "interface gateways list" command for the second question has several arguments and it may end up caching the same content multiple times in two different files for that reason:

src/opnsense/mvc/app/models/OPNsense/Routes/Route.xml:                <ConfigdPopulateAct>interface gateways list</ConfigdPopulateAct>
src/opnsense/mvc/app/models/OPNsense/Routing/GatewayGroups.xml:                <ConfigdPopulateAct>interface gateways list -l</ConfigdPopulateAct>

These two likely produce the same output most of the time but are different parameters so effectively different calls. I also have two files with the same content.


Cheers,
Franco
#8
Hardware and Performance / Re: BIOS and BMC firmware for ...
Last post by vpx - Today at 07:48:30 AM
There is a new BIOS/BMC/SUM bundle containing:

BIOS: 2.3 (04/14/2025) - unchanged
BMC: 04.07 (05/29/2026)
Supermicro Update Manager (SUM): V2.14.0-p10 (09/22/2025)

https://www.supermicro.com/support/resources/getfile.php?SoftwareItemID=31458
#9
General Discussion / Re: Unbound DNS keeps crashing...
Last post by apoorv569 - Today at 07:39:48 AM
Quote from: meyergru on July 12, 2026, 10:16:22 AMThe rules look "O.K." now. I told you to first check if your rules cause the problems in my first answer, for somehow I guessed that you redirected "all" port 53 traffic, creating an endless loop like explained here.

What can you learn of this? Your rule of thumb should be: If you experience problems, show your rules, because often times, they are the cause of it. See also the "READ THIS FIRST" article in the tutorial section.

That being said, your current rules alone will not help you with either DoT or DoH, which are the default in many browsers now.
There is a discussion about this also in the tutorial section.

Basically, you can block port 853 for DoT, but you need a blocklist for known DoH services because you cannot block port 443.

Also, there are a few more kinks in your rules, because they apply to IPv6 as well, see this.

On a side note: I have given up on the "block any other DNS than my own" game, because you cannot win it.

It worked for a while but seems to be happening again.  I'm wondering that there are so many queries being made per second that upstream limits or times out or something..
#10
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by rusli - Today at 07:22:20 AM
Maurice,

Since when I posted on github???
My apologise.
Everyone makes mistakes.