FIREWALLD.ICMPTYPE(5)

NAME
firewalld.icmptype - firewalld icmptype configuration files

SYNOPSIS

/usr/etc/firewalld/icmptypes/icmptype.xml
/usr/lib/firewalld/icmptypes/icmptype.xml

DESCRIPTION

A firewalld icmptype configuration file provides the information for an Internet Control Message Protocol (ICMP) type for firewalld.

This example configuration file shows the structure of an icmptype configuration file:

    <?xml version="1.0" encoding="utf-8"?>
    <icmptype>
      <short>My Icmptype</short>
      <description>description</description>
      <destination ipv4="yes" ipv6="yes"/>
    </icmptype>

OPTIONS

The config can contain these tags and attributes. Some of them are mandatory, others optional.

  icmptype

The mandatory icmptype start and end tag defines the icmptype. This tag can only be used once in an icmptype configuration file. This tag has optional attributes:

version="string"
    To give the icmptype a version.

  short

Is an optional start and end tag and is used to give an icmptype a more readable name.

  description

Is an optional start and end tag to have a description for a icmptype.

  destination

Is an optional empty-element tag and can be used only once. The destination tag specifies if an icmptype entry is available for IPv4 and/or IPv6. The default is IPv4 and IPv6, where this tag can be missing.

ipv4="bool"
    Describes if the icmptype is available for IPv4.

ipv6="bool"
    Describes if the icmptype is available for IPv6.

SEE ALSO
firewall-applet(1), firewalld(1), firewall-cmd(1), firewall-config(1), firewalld.conf(5), firewalld.direct(5), firewalld.dbus(5), firewalld.icmptype(5), firewalld.lockdown-whitelist(5), firewall-offline-cmd(1), firewalld.richlanguage(5), firewalld.service(5), firewalld.zone(5), firewalld.zones(5), firewalld.policy(5), firewalld.policies(5), firewalld.ipset(5), firewalld.helper(5)

NOTES

firewalld home page:
    http://firewalld.org

AUTHORS

Thomas Woerner <twoerner@redhat.com>
    Developer

Jiri Popelka <jpopelka@redhat.com>
    Developer

Eric Garver <eric@garver.life>
    Developer