Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I prepare an xml:
<service>
<short>Xelerance l2tpd</short>
<description>A Layer 2 Tunneling Protocol VPN client/daemon for Linux and other POSIX-based OSs. Based off of L2TPd 0.61.</description>
<port protocol="udp" port="1701"/>
</service>
I execute:
$ firewall-cmd --permanent --new-service=xl2tpd
I see file got copied into /etc/firewalld/services/ but
$ firewall-cmd --get-services
show no such service, so I do: systemctl restart firewalld - now --get-services list it but I end up with:
<?xml version="1.0" encoding="utf-8"?>
<service>
</service>
effectively having no results on iptables after adding the service to a zone
Version-Release number of selected component (if applicable):
firewalld-0.3.9-11.el7.noarch
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
I've just come across something, I've tried man pages but could not find any info on '&' char.
And it seems that if it is in .xml file (I had in <description>) then firewalld omits silently.
yes, but this - if one makes one mistake in one .xml then the rest, if there are other custom services xmls, get silently skipped! Services are there listed as attached to zones but ports are not opened!
test it - make a mistake in <port> eg. put 443,444 instead of 443-444 (and I imagine many of us will be makeing it, old iptables style habit) and all custom services are affected.
I'd be nice to have firewalld resilient to this.
(In reply to lejeczek from comment #9)
> yes, but this - if one makes one mistake in one .xml then the rest, if there
> are other custom services xmls, get silently skipped! Services are there
> listed as attached to zones but ports are not opened!
>
Please open an extra bug for this - it is a different issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2597.html