kill landlords - why are you on my profile?

  • 1 Post
  • 65 Comments
Joined 10 months ago
cake
Cake day: January 23rd, 2024

help-circle







  • drkt@lemmy.dbzer0.comtoLinux@lemmy.mlFirewalls: what SHOULD I block?
    link
    fedilink
    arrow-up
    7
    arrow-down
    10
    ·
    edit-2
    1 month ago

    You shouldn’t be touching it, honestly. There’s a firewall at your router. It should be responsible for blocking incoming traffic. Firewalls on individual machines are for servers where you know exactly what’s going in and out. I don’t have a firewall on my desktop or laptop.

    You will spend the best years of your life chasing random network connections if you block everything by default.










  • Hosting videogames on a dedicated box for me and the boys when I was 16 got me more interested in networking and when I had finished my mostly unrelated education, I pivoted hard to IT. I don’t currently work in IT and I don’t know if I ever will again because my handicap and location make it hard to find jobs but essentially:

    Self-hosting came first, then came the tech ‘background’.



  • All of my services run on LXC containers. Some files and configs are backed up to NAS and offsite. The containers are snapshotted in their entirety before I do any work on them. A snapshot takes 5 seconds to make and causes no downtime. If I regret a change or mess it up, I can restore the snapshot in under a minute at the cost of some seconds of downtime.

    My only non-container machines are my desktop (doesn’t count), my NAS and the Hypervisor. The Hypervisor is very clean and wouldn’t be much fuss to reinstall and the NAS is literally just Debian with NFS. All of these have a regular rsync which runs to backup the important files.