Mainfrezzer

Life lemons, lemonade something positive from it at least. Strolling through the files, i do notice youre running 6.13.3 but run an incompatible go file script. The 1.4 version of the Ram-log script does not work in 6.12.3 Version 1.6 for 6.12.3 If you decide to upgrade to 6.12.4, the code can be found a bit further down.

You would need to post the diagnostics because we can only ask the magic crystal ball for this "execution error". the zfs plugin/ the snapshots in general are not the way. Snapshots are, well, snapshots not the actual data^^

Docker container are removed over the Docker page, not the zfs master plugin. Those snapshots are all created by the dockerservice.

Do you use powertop with the "--auto-tune" by any chance?

Just as a one off random chance shot in the dark.... You're not trying to boot in uefi mode are you? The 730 only works in legacy/bios mode.

I wouldn't bet on that since I'm certain it's due to the switch time, especially since the Synology worked fine. Either the ups specsheet is lying or the evga psu is not up to spec

mhmm spontaneously i would say "dd if=/dev/zero of=data.null bs=10G count=100" which would be a 1TB file with lots and lots of null. "dd if=/dev/zero of=data.null bs=10G count=1000" would be 10TB Be careful, it creates the file where you currently are in the console. Edit: You could also download a zipbomb for quick and easy data to fill the empty space with

Thats even too much efford put in^^ all you need to do is literally this This.mp4

Docker Container nur ne ipv4 zuweisen. wenn MACVLAN benutzt wird, was ich mal stark vermute bei ner Fritzbox, --mac-address 01:23:A0:B1:C3:D4 eintragen bei den Extra Parametern (sichtbar nur bei Aktivierung der erweiterten Ansicht oben rechts) Starten Wenn man lust hat kann man jetzt in der Fritzbox die ULA immer zuweisen lassen, oder auch nicht, egal. Der Container bekommt dann folgende Adressen zugewiesen. fe80::0323:a0ff:feb1:c3d4 fd00::0323:a0ff:feb1:c3d4 (wenn man die standard ULA bei der Fritzbox nimmt) ÖffentlicherPRÄFIX:0323:a0ff:feb1:c3d4 Und was man nun letztendlich für den DHCP Server nimmt ist entweder die fe80 Adresse, nur lokal in einem Netz benutzbar oder die fd00 Adresse, die man für andere Subnetze benutzen könnte (ermöglicht halt auch rDNS für DNS Server, aka statt Adressen stehen dann die clientnamen)

Still not on it. The client that connects to the unraid wireguard server shall have access to the whole of the internet, wherever they are in the world. Everything, except for the network the wireguard server is running on, i.e bogus networks. Pratically be a tor exit node without the ability to reach the local network of the node. theres a guide for that but im not sure how well that translate to the unraid wireguard variant https://gist.github.com/qdm12/4e0e4f9d1a34db9cf63ebb0997827d0d

Na not me, the OP. OP wants to provide a VPN connection for someone outside their lan to use their server as exitnode but does not want the clients to be able to access the lan network the wireguard server is running on.

You cant start that docker container Use the tag for the specific version of the container (i.e Author/Dockerimage:V1.23) If that docker image does not exist on the repository anymore, you still have it locally, which will be used unless you delete it OR if you wanna be super save, push it to your own repository as backup. All you ultimately need to do is a dummy change in the edit fuction, like add a 1 to a random line and delete it, then hit apply and youre done.

It depends on the power supply, how sensitive they are to losing power. You probably dont have a spare PSU around to test your server/ups with i assume? You could look up the hold-up time for your psu and check how fast the switch time is of the ups. Edit: All i can find for the ups is a "respond time of 4ms" which i doubt because i dont think that a psu from evga is that horrible in terms of hold-up time

If the PC turns of the second you unplug the cable from the UPS to the Wall, theres something going on with your UPS. Probably not fast enough with switching or something else.

Thats the total opposite^^ Whats sought is Internet only - No Lan access.

You can indeed do that with wireguard. Needs manual configuration of the wireguard server with iptables to drop packets with your local network as destination.

Das ist doch ein sehr komischer Vergleich für etwas banales wie Raider und Twix

Eben dass man LLA-ULA-GUA nicht wirklich beeinflussen kann^^ (vor allem mit Docker, was SCHMERZ ist) Das muss alles von einem IPv6 Router kommen. Das ipv4 "Gedankenkonstrukt" ist fatal bei der Sache^^ Für zuhause ist das Jacke wie Hose. Da könnt auch nen pinkes Schweinchen drauf sitzen und es macht kein Unterschied. Das einzige was mir im Heimbereich eventuell einfällt wozu man doch gerne die ULA nutzen würde ist rDNS. Das Ende vom Lied war ja, wechselndes Präfixe trifft nur bei GUA auf und das ist absolut unerheblich für Heimanwendungen. Die "statischen" Präfixe gibts ja bereits.

Das ist unmöglich. Das ganze Konstrukt von IPv6 baut auf die Link-Local-Adressen auf. Ohne die, keine weiteren Adressen. Wobei ULA deaktivierbar ist und nicht benötigt(router seitig). Ohne statische Präfixzuweisung bleibt intern nur die LLA und das ist so simpel wie 192.168.2.254 als DNS einzutragen, nur halt mit der fe80::ab12:de17:blub. Extern, wozu man ja eigentlich nur die GUA benötigt, tja. Das kann man vergessen. Da würde nur sowas wie DoH funktionieren. Mit Macvlan kann man selbst sich die Adresse etwas zusammenbasteln, mit ipvlan bekommt man halt das was man bekommt. Wenn man dringend nen GUA erreichbaren DNS Server benötigt und man nur nen dynamischen Anschluss hat da würd ich raten den DNS Server auf irgend nen popeligen vserver zu packen. (Wobei ich den auch nicht öffentlich zugänglich machen würde)

I would give it another reboot since i reckon there wasnt the modprobe at the initial bootup. The plugin does state that for upgrade you do need to reboot twice, you kind of done that here by manually installing the plugin. If that doesnt fix it, i would try a bios update for the pc. But thats from google search for the kernel panic. If that doesnt fix it at all i would head to the support thread of the plugin.

Indeed. 6.1.49 is the new Kernel in 6.12.4

/config on the usb drive is /boot/config in unraid. /config/plugins is already correct Edit: i do see the issue, gimme a second. https://magnon-box.tk/api/public/dl/3_QCBWZP/r8168-driver.zip Edit: Ive noticed a lot of people still try to download this. Its still the specific 6.12.4 version. The Toplink is dead. This one is permanent, but as i said, for 6.12.4 https://magnon.ovh/api/public/dl/3OppGPir/r8168-driver.zip Edit 2: Alternatively, i also attached the file to this post. Just in case. Drop the unraid-r8168.plg and the r8168-driver folder in /config/plugins. Ive downloaded the plugin on my server and copied the folder. The plugin does require internet access to download the files first. This is for 6.12.4 tho, if you need it for any other Unraid version, let me know r8168-driver.zip

Server has been up for a couple hours now and i have not placed the modprob change (options i915 enable_dc=0) back into it. So far, nothing in the logs. Anyone with an affected CPU able to say the same?

You could download the package and place the .plg on the usb to install the driver for the RTL8168H https://github.com/jinlife/unraid-r8125-r8152-driver

Is that already implemented? Only working for openvpn or still an upcoming feature? Im currently using the container to connect to a wireguard server thats behind a dynamic ip and its been a bit of a hassle to restart the container each time the endpoint has a new ip assigned (which happends either once every 24h or, if the telekom decides to be muppets again, 20 times a day)