You can specify a whole network as des/src, 192.168.1.0/24 would include all hosts from 192.168.1.1-254. So there is no need for a rule for every VM. You will however need a rule for every exception.
Hey,
you can add a firewall rule to drop/reject traffic in a subnet by setting the source and destination to the subnet. If your router should also be on the same subnet, you can add another rule(in front of the blocking one) that allows all traffic from and to the router.
(Datacenter ->...
Hey,
setting up port forwarding should work[1]. You could also create a new user with no rights on the server and use that instead of root as an SSH "middleman".
[1] https://serverfault.com/a/1017016
Welcher dieser container verbraucht denn immer mehr RAM? Weil wenns so bleibt, ist der RAM ja nur zu 50-60% voll. Ich nehme an ausser Docker läuft sonst nichts mehr im CT was den RAM verauch erklären würde.
Looks like there might be something wrong with your storage or your RAM. With debsums you can check if everything with the installed package is ok, and for checking your RAM you can use MemTest.
Hey,
was für container hast du da denn laufen? Irgendwas verbraucht den Speicher ja, kannst du im CT mal nachschauen welcher Prozess denn den meisten RAM braucht?
Since the only thing that does not change with all the things you tried is the terminal you use, it sounds like the problem might be related to your terminal and the config you use for it. Could you try using a different terminal? xterm(the application) or maybe just the root shell in the Web...
Hey,
siehst du Dateien wenn du diese direkt in /var/lib/minidlna (also nicht in einem Unterordner) anlegst? Wenn du mit dem SMB client eine Datei im Share anlegst, wo landet diese auf dem Server?
Hey,
how much free space do you have on your NVME? I assume the NUC only has one SATA port. So you could either
* move an LXC to the NVME, swap the SSDs then move the LXCs (from the NVME) to the new SSD, this however only works if you have enough free space on your boot drive to hold the...
Hey,
I assume you mean after starting docker containers or is this happening right after the installation of docker? Could you post the output of journalctl -u sshd.service -b and lsof -i -P -n | grep LISTEN after it kicked you out(and you're connected again)?
Hey,
a bit of a wild guess, but could you check if the problem persists if you use a different terminal? Also check what the TERM[1] environment variable is set to, xterm should be fine, having it set to something that is not present on the server might cause the weird behavior you see.
[1]...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.