Description of problem: internet ip addresses are showing up in my arp tables [robertwfairbrother@localhost ~]$ systemctl status firewalld ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-05-31 10:20:33 MDT; 1 day 2h ago Docs: man:firewalld(1) Main PID: 1063 (firewalld) Tasks: 2 (limit: 4611) Memory: 20.6M CGroup: /system.slice/firewalld.service └─1063 /usr/bin/python3 /usr/sbin/firewalld --nofork --nopid May 31 10:20:29 localhost.localdomain systemd[1]: Starting firewalld - dynamic firewall daemon... May 31 10:20:33 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall daemon. May 31 10:20:35 localhost.localdomain firewalld[1063]: ERROR: Failed to load service file '/usr/lib/firewalld/services/tcpcryptd.xml': PARSE_ERROR: Unexpected element direct Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Also in clean installs of Fedora 30, and Rawhide. $ rpm -q firewalld firewalld-0.6.3-2.fc30.noarch
This service definition is provided by the tcpcrypt package. # dnf repoquery -l tcpcrypt |grep tcpcryptd.xml /usr/lib/firewalld/services/tcpcryptd.xml firewalld direct rules are not valid inside service definitions, hence the error. See man firewalld.service. Reassigning to tcpcrypt.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Is this a duplicate of bug 1502646? created on 2017-10-16 and still open? Still present FC32.
Looks like /usr/lib/firewalld/services/tcpcryptd.xml should not be placed there, but copied to (or merged with if it already exists) /etc/firewalld/direct.xml. Doing a firewall-cmd --reload after that produces no more errors with journalctl status. However, my network goes a bit bonkers. The RDP connection to my laptop drops and can't reconnect. Google searches become quite slow, if they complete. Running tcnetstat errors out with "tcpcrypt_getsockopt(): No such file or directory" Going to github, this hasn't been worked on for a few years, the main developer out since 2016. dnf erase tcpcrypt solved the problem, not sure why this was on this system (not on my other boxes)
This is definitely a dup of bug 1502646. (Also, while no work has been done on the implementation since a long time, the IETF published RFC 8547 and RFC 8548 in May 2019.)
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This issue or some very similar one still exists as of Fedora 37. On bot an upgrade from Fedora 35 and a fresh installation I had to remove tcpcrypt to allow firewalld to start.
Confirming this issue on Fedora 36 after an upgrade of firewalld from version 1.0.5 to 1.2.3. Removing the file /usr/lib/firewalld/services/tcpcryptd.xml "solved" this issue.
Don't think this should be in EOL status. This just occurred with a Fedora 37 (new install within the past 1 month) --> Fedora 38 upgrade.
(In reply to Mike from comment #13) > Don't think this should be in EOL status. > > This just occurred with a Fedora 37 (new install within the past 1 month) > --> Fedora 38 upgrade. I submitted updates to the tcpcrypt package, but they did not get merged. https://src.fedoraproject.org/rpms/tcpcrypt/pull-requests
*** This bug has been marked as a duplicate of bug 1502646 ***