@genmaicha That's what I'm searching about online right now, but not really getting any meaningful answers as of yet. I feel like it should be possible, right? My networking experience is also virtually non-existent, so……
Conversation
Notices
-
👺防空識別區👹 (adiz@mtl.jinxian.casa)'s status on Monday, 10-Feb-2025 05:02:46 JST 👺防空識別區👹
-
silverpill (silverpill@mitra.social)'s status on Monday, 10-Feb-2025 05:02:45 JST silverpill
You need to figure out server's IP address, then you can block incoming connections via iptables, for example
iptables -A INPUT -d 10.2.3.4 -j REJECT -
silverpill (silverpill@mitra.social)'s status on Monday, 10-Feb-2025 05:55:26 JST silverpill
@adiz You also need to block outgoing requests ("deny to" or something like that)
@genmaicha -
👺防空識別區👹 (adiz@mtl.jinxian.casa)'s status on Monday, 10-Feb-2025 05:55:27 JST 👺防空識別區👹
@silverpill Yeah, so, basically, if I understand this correctly, I can delete all my mitractl "reject" rules if I want. Then, I can use ufw to do like sudo ufw deny from <ip_address> to any and the instance for which that IP address is applicable will essentially not be able to connect to my server, thereby won't be able to receive any of my messages nor activities. I think I have that right? Then, I would basically not exist to them, for all intents and purposes. I think? Yes? 😅 @genmaicha
-
👺防空識別區👹 (adiz@mtl.jinxian.casa)'s status on Monday, 10-Feb-2025 05:55:28 JST 👺防空識別區👹
@silverpill I use ufw for managing my firewall on Debian (iIrc it's the recommended interface for handling the firewall "out of the box"). I'm assuming I can do the same via it if I can ascertain the IPs of the instances I'm trying to block access to…… @genmaicha
-