You are not logged in.
Hi !
The documentation for Firewalld says that "Only selected incoming connections are accepted" in the "Public" and "Home" zones.
On my setup though, it doesn't appear to be the case. On my wlo1 connection set to zone "Home", with only the default services activated, I can see with ngrep that :
* a BitTorrent client receives TCP traffic through port 44771
* DNS over TLS works through port 853
$ firewall-cmd --list-all --zone=home
home (active)
target: default
icmp-block-inversion: no
interfaces: wlo1
sources:
services: dhcpv6-client mdns samba-client ssh
ports:
protocols:
forward: yes
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
The same happens when I activate my wireguard connection which I set to the "public" zone.
Am I understanding something wrong or is there a problem in my settings ?
Thanks !
Last edited by Cvlc (2021-08-28 15:00:07)
Offline
I know nothing about firewalld, but https://serverfault.com/questions/10547 … stablished suggests that it adds reasonabl-ish conntrack rules by default.
You can look at your situation w/ "iptables -nvL"
The incoming traffic is probably not strictly incoming, but part of an ongoing communication that you triggered (DNS requests, bittorrent participation)?
Offline
Thanks for your answer !
So opening up is TCP 853 would only be necessary in order to run a dns server I guess.
I'll check if bitttorrent is able to send files with the firewall activated and without the proper rules and report back
Offline
systemd-resolved might be using 853 as local port for DNS/TLS
You'll not be able to *receive* files via bittorrent, for leeching you'd have to limit outbound traffic (and likely get kicked from the network, because nobody likes leechers. At least when I was young…er)
Offline
You're right it's just already established connections. Inbound connections are properly blocked
thanks !
Offline