Manage fail2ban jails, bans, and filters inside a SWAG container.
npx skills add https://github.com/jmagar/claude-homelab --skill fail2ban-swag
Please help me install this Agent Skill. Skill: fail2ban-swag Source: https://github.com/jmagar/claude-homelab/tree/main/skills/fail2ban-swag Command: npx skills add https://github.com/jmagar/claude-homelab --skill fail2ban-swag
Protect SWAG-protected services by centralized fail2ban management inside the SWAG container, enabling quick status checks, bans, unbans, jail configuration, and regex testing to deter abusive access patterns.
Install the skill and run the wrapper to manage fail2ban inside the SWAG container.
High-intent search queries and answers about installing and using this skill.
The wrapper automates fail2ban management inside the SWAG container, allowing you to check jail status, ban or unban IPs, create custom jails, and test regex filters against logs mounted under the /config directory.
Configuring fail2ban for SWAG requires SSH access to the host, a running SWAG container named swag, and appdata mounted at the configured path. You must also set the SWAG_HOST, SWAG_CONTAINER_NAME, and SWAG_APPDATA_PATH environment variables and have jq installed.
Yes, you can test fail2ban filters against SWAG logs before applying them. The wrapper supports filter testing against logs mounted under the /config directory, enabling real-time troubleshooting workflows for regex validation.
Centralized fail2ban management protects SWAG-protected services by deterring abusive access patterns. It enables quick status checks, IP bans, unbans, jail creation, and filter testing inside the SWAG container to block malicious traffic.
The best way to troubleshoot fail2ban jails in a SWAG Docker deployment is using structured commands that provide a readable status overview of all jails, review banned IPs, reload configurations, and test filters against logs mounted under /config.
Fail2ban may not work with your SWAG container if the logs are not mounted under /config, the container is not named swag, or the environment variables SWAG_HOST, SWAG_CONTAINER_NAME, and SWAG_APPDATA_PATH are not configured correctly for your deployment.
BBufSSH into h100_sglang to attach to the sglang_bbuf container for GPU-enabled SGLang development.
L3DigitalNetManage Fail2ban jails, filters, and IP bans for intrusion prevention.
SSujitXManage Docker container networking, Nginx reverse proxy configurations, and Let's Encrypt SSL certificates.
L3DigitalNetInstalls, configures CrowdSec intrusion prevention system and manages it via cscli and config files.
