[CT] - migrate to nftables and re-deploy fail2ban #1124
Labels
No labels
🔥
🦾 1
🦾 2
🦾 3
🦾 4
🦾 5
🦾 6
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
🙌 Decission needed
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
Goal 2025
help wanted
high impact
housekeeping
Howto
infra
In progress
🤔️ Investigate
Invoice Ninja
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low impact
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
PR ready
question
Ready
refined
Roundcube
searX
SPAM Issues
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Website
windows
wontfix
xmpp
Yearly Report
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#1124
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current default on containers is iptables. We should migrate to nftables and automate it unlike current iptables setup on containers.
Development:
Implementation:
I added a comment in the Documentation that you already provided to ask also for documentation on how you mount needed stuff for logfile parsing
[CT] - migrate to nftablesto [CT] - migrate to nftables and re-deploy fail2banPretty much done but need to do logdir mount and remounts and that will disturb services and since its middle of the day I will not do it now. I will either do it during morning session or perhaps sunday as it's usually quiet. I will see what I will be more comfortable with.