Score:0

How to close podman exposed port on public interface

se flag

I have running AdGuardHome instance on podman with WebUI port -p 8053:80.

# podman port -a
1aeb8e800717    53/tcp -> 0.0.0.0:53
1aeb8e800717    853/tcp -> 0.0.0.0:853
1aeb8e800717    5443/tcp -> 0.0.0.0:5443
1aeb8e800717    80/tcp -> 0.0.0.0:8053
1aeb8e800717    53/udp -> 0.0.0.0:53
1aeb8e800717    784/udp -> 0.0.0.0:784
1aeb8e800717    853/udp -> 0.0.0.0:853
1aeb8e800717    5443/udp -> 0.0.0.0:5443

# firewall-cmd --get-active-zones
public
  interfaces: ens3
trusted
  sources: 10.88.0.9/32 10.88.0.10/32 10.88.0.11/32
tunnel
  interfaces: wg0

# firewall-cmd --list-all --zone=trusted
trusted (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: 
  sources: 10.88.0.9/32 10.88.0.10/32 10.88.0.11/32
  services: 
  ports: 
  protocols: 
  forward: no
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

# firewall-cmd --list-all --zone=public
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: ens3
  sources: 
  services: dhcpv6-client ssh wireguard--50176
  ports: 63035/udp
  protocols: 
  forward: no
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
    rule family="ipv6" source address="fd42:42:42::0/24" masquerade
    rule family="ipv4" source address="10.66.66.0/24" masquerade

tunnel zone is wireguard tunnel.

How I can close exposed 8053 port on public zone?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.