The issue I am facing:
I have pihole running in a docker container. I've locked down most of my ports on my box except the few required for pihole to run (see below). Still able to access the web gui, as I have 80 and 443 open as well.
iptables -A INPUT -p udp --dport 53 -j ACCEPT
iptables -A INPUT -p tcp --dport 53 -j ACCEPT
iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
iptables -A OUTPUT -p tcp --dport 53 -j ACCEPT
iptables -A INPUT -p udp --dport 67 -j ACCEPT
iptables -A INPUT -p tcp --dport 67 -j ACCEPT
iptables -A OUTPUT -p udp --dport 67 -j ACCEPT
iptables -A OUTPUT -p tcp --dport 67 -j ACCEPT
iptables -I INPUT 1 -p udp --dport 67:68 --sport 67:68 -j ACCEPT
iptables -I INPUT 1 -p tcp -m tcp --dport 4711 -i lo -j ACCEPT
iptables -I INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
This works just fine, no issue with pihole. I am able to upload a teleporter file from another pihole just fine using teleporter-->browse (add local file)-->restore. However, if I lock down the remaining ports using these iptables commands below, teleporter will not upload the restore file:
iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP
iptables -t filter -P OUTPUT DROP
The above would drop all traffic not specifically authorized.
Everything else continues to work properly including DN resolution and the webgui. For the teleporter-->browse (add local file)-->restore dialog box, there is a spinning disk in the upper right of the dialog box and it never finishes. Obviously teleporter needs some other ports open to work properly.
Any help much appreciated.
Details about my system:
Pihole running in docker
What I have changed since installing Pi-hole:
The firewall rules