Conversation

Notices

1. anonymous (anonymous@freespeechextremist.com)'s status on Tuesday, 30-Jan-2024 11:12:02 JST anonymous

   in reply to

   • menherahair
   • this ad CAN be blocked, bitch

   @menherahair @kirby Or you could just use gufw.

   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Tuesday, 30-Jan-2024 11:12:02 JST † top dog :pedomustdie:

     in reply to

     • menherahair
     • this ad CAN be blocked, bitch
     @anonymous @menherahair @kirby Or just ip tables
   • menherahair (menherahair@eientei.org)'s status on Tuesday, 30-Jan-2024 11:12:03 JST menherahair

     • this ad CAN be blocked, bitch
     @kirby ufw allow in 22
     alt: ufw allow in port 22, get error, man ufw and walk the longest option line listed in usage to construct the command
     you can also throw iptables rules in /etc/ufw/*.rules
     or define shit in /etc/ufw/applications.d/ and update that instead of the rules every time application's port changes or there's a new one
     that's pretty much it. do routing/nat in the .rules files or with iptables, cli ufw is too dumb for it