<dhcpd>
<lan>
<range>
<from>192.168.97.10</from>
<to>192.168.97.245</to>
</range>
</lan>
</wan>
<enable>1</enable>
<ddnsdomainalgorithm>hmac-md5</ddnsdomainalgorithm>
<numberoptions>
<item/>
</numberoptions>
<range>
<from>192.168.2.100</from>
<to>192.168.2.110</to>
</range>
<winsserver/>
<dnsserver/>
<ntpserver/>
</wan>
</dhcpd>The following input errors were detected:
The DHCP Server is active on this interface and it can be used only with a static IP configuration. Please disable the DHCP Server service on this interface first, then change the interface configuration.Quote from: trixter on Today at 11:06:51 AMAufs Manangement-Interface würde der Traffic auch nicht kommen, davon war nicht die Rede.QuoteClients am LAN könnten eben so gut ihre DNS-Anfragen an die Management-IP richten. Wenn da ein DNS läuft und die Firewall-Regen den Zugriff erlauben, werden sie eine Antwort erhalten.
Sowas würde ich schon aus Prinzip nicht machen - Lan-Traffic hat am Management-Interface per se nichts zu suchen!
Quote from: ziegler on Today at 07:21:42 PMDanke für Deine Antwort.
Ich habe noch ein Riegel 16GB 1Rr8 PC-5600B-SA0-1010-XT DDR5 SODIMM aus einem HP Mini Elite PC, diesen würde ich dann nutzen wollen.
Der RAM ist quasi neu, wurde nie benutzt.
Die Preise für RAM sind ja heute recht hoch, deshalb nicht extra neu kaufen.
Auch habe ich eien Samsung EVO 960 Plu mit 1 TB noch über.
Das sollte doch mit CoreBoot kompatibel sein, oder?
Hat CoreBoot eigentlich einen Vorteil gegenüber dem "klassischen" bis auf das es opensource ist?
Ich würde nämlich lieber coreBoot nehmen aus dem "Bauch" heraus.

root@opnsense1:~ # netstat -rn6 | grep -c fdXX:XXXX:XXXX:XXXX::XXXX
0
root@opnsense1:~ # vtysh -c "show ipv6 route fdXX:XXXX:XXXX:XXXX::XXXX"
Routing entry for fdXX:XXXX:XXXX:XXXX::XXXX/128
Known via "kernel", distance 0, metric 0
Last update 00:01:03 ago
Flags: None
Status: Installed
* directly connected, vmx0_vlan788
Routing entry for fdXX:XXXX:XXXX:XXXX::XXXX/128
Known via "kernel", distance 0, metric 0
Last update 00:01:58 ago
Flags: None
Status: Installed
* directly connected, vmx0_vlan788
Routing entry for fdXX:XXXX:XXXX:XXXX::XXXX/128
Known via "kernel", distance 0, metric 0
Last update 00:02:34 ago
Flags: None
Status: Installed
* directly connected, vmx0_vlan788
...
(222 similar entries in total)(Yes, I know it's pointless to obfuscate ULAs)Quote from: meikel on Today at 08:10:22 PMSadly both ram sticks had no issues after 30min.30 minutes is not enough.
Quote from: meikel on Today at 08:10:22 PMI tried running a live debian13 and the device hung after some seconds on the desktop.That rules out SSD issue.
Quote from: meikel on Today at 08:10:22 PMI improved cooling (airflow) even though I don't think this is the issue (the issue persists even after the cooling body feels way cooler now).Improving the airflow wont fix bad thermal contact between heat sink and the cpu. Also, bad thermal contact can cause overheating even if your case is cold to the touch.
Quote from: meikel on Today at 08:10:22 PMI also replaced the CMOS battery as a friend suggested this can be the root cause of such issues but no luck here either.CMOS is active only when you turn on your system. Once POST is completed, it does nothing.
Quote from: meikel on Today at 08:10:22 PMI will wait for the serial cable and try to debug that way. In the meantime I might try to update the bios of the mainboard.You should not update anything until you find what the problem is.
Quote from: meikel on Today at 08:10:22 PMI also have to correct myself: the SSD is not running in raid1. It's a single SSD but as a live OS is also crashing I assume it's not the SSD. I also doubt that a faulty SSD crashes the whole machine.
Quote from: Patrick M. Hausen on Today at 04:36:36 PMDoes your device have a serial console? If yes, connect a PC with a terminal program and let that run until the next crash. The serial console output will not be cleared on reboot unlike VGA/HDMI.