firewalld not working after reboot
by Rob Marshall
Hi,
I have an issue where, after a system reboot (Oracle Linux 7), communications to the node are not working correctly. If i stop and start (often a restart doesn't work) the firewalld service the network will work correctly. While things were broken I did a: 'firewall-cmd --list-all' and noticed that two of the interfaces were missing. Where can I look to determine what may be going wrong when firewalld starts after a reboot?
Thanks,
Rob
2 years, 1 month
firewalld.org not updated?
by Andrei Borzenkov
Website lists 1.0.1 as the latest release while we have 1.0.2, 1.0.3 and
in the meantime 1.1.0.
Also some summary of changes in 1.1.0 (if there are significant changes)
is certainly helpful.
2 years, 1 month
Allowed source-port is being blocked (AdGuard Home)
by Koen Drai
Hi,
I am running an AdGuard Home DNS server in my home network (on Debian 11, which is v0.9.3).
Works fine so far, but I am getting the following error messages in syslog:
Mar 6 20:48:33 fook kernel: [160941.334608] "filter_IN_knet_REJECT: "IN=enp2s0 OUT= MAC=<MAC> SRC=5.9.164.112 DST=192.168.1.1 LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=0 DF PROTO=TCP SPT=853 DPT=46170 WINDOW=0 RES=0x00 RST URGP=0
However, this request should not be rejected according to the configuration:
/etc/firewalld/zones/knet.xml
(...)
<rule family="ipv4">
<!-- 853 TCP AdGuard Home-->
<source-port port="853" protocol="tcp"/>
<accept/>
</rule>
(...)
--list-all:
(...)
rich rules:
(...)
rule family="ipv4" source-port port="853" protocol="tcp" accept
(...)
Similar behavior for source-port 443 TCP.
Am I missing something?
Is this a known error (and fixed in a later version?)?
Thanks for any hints,
Koen
2 years, 1 month