2024-06-19, 04:01 PM
(This post was last modified: 2024-06-19, 04:02 PM by crashx. Edited 1 time in total.)
Thanks for the reply! If you run sudo iptables -xvnL, the leftmost column of output is packets (pkts). In the output I shared:
345 563268 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0
345 packets skipped the ban rules and hit the return with source 0.0.0.0 which feels like it could be related to a container's address being forwarded instead of the right address.
here's jellyfin.local. Note that I updated the action to use the newer iptables call where all ports is specified as a argument.
[jellyfin]
backend = auto
enabled = true
port = 8096,80
protocol = all
filter = jellyfin
maxretry = 3
bantime = 86400
findtime = 43200
logpath = /jellyfin-logs/log*
action = iptables[type=allports, name=jellyfin, chain=DOCKER-USER]
345 563268 RETURN 0 -- * * 0.0.0.0/0 0.0.0.0/0
345 packets skipped the ban rules and hit the return with source 0.0.0.0 which feels like it could be related to a container's address being forwarded instead of the right address.
here's jellyfin.local. Note that I updated the action to use the newer iptables call where all ports is specified as a argument.
[jellyfin]
backend = auto
enabled = true
port = 8096,80
protocol = all
filter = jellyfin
maxretry = 3
bantime = 86400
findtime = 43200
logpath = /jellyfin-logs/log*
action = iptables[type=allports, name=jellyfin, chain=DOCKER-USER]