Related changes

Jump to navigation Jump to search

Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on your Watchlist are in bold.

Recent changes options Show last 50 | 100 | 250 | 500 changes in last 1 | 3 | 7 | 14 | 30 days
Hide registered users | Hide anonymous users | Hide my edits | Show bots | Hide minor edits
Show new changes starting from 19:22, 3 July 2026
 
Page name:
List of abbreviations:
N
This edit created a new page (also see list of new pages)
m
This is a minor edit
b
This edit was performed by a bot
(±123)
The page size changed by this number of bytes

2 July 2026

N    22:56  Nftables 2 changes history +3,949 [Scott (2×)]
     
22:56 (cur | prev) −19 Scott talk contribs (TRAVEL SCENARIO: my current IP can't SSH in)
N    
22:49 (cur | prev) +3,968 Scott talk contribs (Created page with "= nftables Cheat Sheet = Config: <code>/etc/nftables.conf</code> · table <code>inet filter</code> · chains <code>input</code> / <code>forward</code> / <code>output</code> Input policy is '''drop'''; SSH allowed only from <code>$ssh_nets_v4</code>. Out-of-band rescue: IPMI/BMC console (H5Viewer or Serial-over-LAN). == Everyday commands == <syntaxhighlight lang="bash"> # Syntax-check the config WITHOUT applying (always do this first) sudo nft -c -f /etc/nftables.con...")
N    22:55  Fail2ban 2 changes history +3,963 [Scott (2×)]
     
22:55 (cur | prev) −4 Scott talk contribs (TRAVEL SCENARIO: I banned myself)
N    
22:48 (cur | prev) +3,967 Scott talk contribs (Created page with "= fail2ban Cheat Sheet = Config: <code>/etc/fail2ban/jail.local</code> (jails) · <code>/etc/fail2ban/fail2ban.local</code> (daemon) Backend: '''systemd journal''' (not log files) · Ban action: '''nftables''' Jail: <code>sshd</code> · maxretry 4 · findtime 10m · bantime 1h Bans trigger on '''auth failures''', not connection counts. == Status & inspection == <syntaxhighlight lang="bash"> # Daemon alive? sudo systemctl status fail2ban sudo fail2ban-client ping...")