![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
4·
6 months agoWhat is your root filesystem installed on - lvm, zfs, or bare disk partitions? Are you booting with grub (legacy/bios) or systemd-boot (uefi)?
What is your root filesystem installed on - lvm, zfs, or bare disk partitions? Are you booting with grub (legacy/bios) or systemd-boot (uefi)?
In the bridge-vids option, you can replace 2-4094 with a space-separated list of vlans to be allowed tagged ingress/egress on the bridge interface, if you prefer to limit it. Nothing in the GUI for that, as far as I know.
If you aren’t going to fully wipe your drive in horrible events like this, at the very least use shred
instead of rm
. rm
simply removes references to the file in the filesystem, leaving the data behind on the disk until other data happens to be written there.
Do not ever allow data like that to exist on your machines. The law doesn’t care how it got there.
DNS is what you’re looking for. To keep it simple and in one place (your adguard instance), you can add local dns entries under Filters > DNS Rewrites in the format below: