Privacy

41933 readers

1209 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Where Are All My Firewall People? (lemmy.world)

submitted 3 days ago by irmadlad@lemmy.world to c/privacy@lemmy.ml

61 comments fedilink hide all child comments

What do you run; Opnsense, pfsense, Smoothwall, maybe a WAF like wazuh?

Today was update/audit firewall day. I'm running a standalone instance of pFsense on a Protectli Vault FW4B - 4 Port - Intel Quad Core - 8GB RAM - 120GB mSATA SSD with unbound, pfBlockerNG, Suricata, ntopng, and heavily filtered. I did bump the swap to 8 GB as I've previously noticed a few 'out of swap' errors under load.

Before I signed off, I ran it through a couple porn sites to see if my adblocking strategy was working. Not one intrusive ad. Sweet!

Show me what you got.

you are viewing a single comment's thread
view the rest of the comments

[–] irmadlad@lemmy.world 2 points 2 days ago

I have found that a lot of VPN kill switches interfere with other security measures. For instance, I use tailscale on my VPS. I also run a local VPN. If I have the kill switch on the local VPN engaged, it interferes with tailscale and I cannot ssh in to my VPS. So, a not so elegant solution for me is to disengage the local VPN's kill switch for that session, and then re-enable it after I am finished administering my VPS. After which I will do a DNS leak check to make sure everything is as it was. Takes a couple of quick steps, but it seems to work.