zoukankan      html  css  js  c++  java
  • 通过文件配置:firewalld.service(5)

    firewalld.service

    Name

    firewalld.service — firewalld service configuration files

    Synopsis

    /etc/firewalld/services/service.xml
    /usr/lib/firewalld/services/service.xml

    Description

    A firewalld service configuration file provides the information of a service entry for firewalld. The most important configuration options are ports, modules and destination addresses.
    This example configuration file shows the structure of a service configuration file:
    <?xml version="1.0" encoding="utf-8"?>
    <service>
      <short>My Service</short>
      <description>description</description>
      <port port="137" protocol="tcp"/>
      <protocol value="igmp"/>
      <module name="nf_conntrack_netbios_ns"/>
      <destination ipv4="224.0.0.251" ipv6="ff02::fb"/>
    </service>

    Options

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

    service

    The mandatory service start and end tag defines the service. This tag can only be used once in a service configuration file. There are optional attributes for services:
    version="string"

    To give the service 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.

    port

    Is an optional empty-element tag and can be used several times to have more than one port entry. All attributes of a port entry are mandatory:
    port="string"

    The port string can be a single port number or a port range portid-portid or also empty to match a protocol only.

    protocol="string"

    The protocol value can either be tcpudpsctp or dccp.

    For compatibility with older firewalld versions, it is possible to add protocols with the port option where the port is empty. With the addition of native protocol support in the service, this it not needed anymore. These entries will automatically be converted to protocols. With the next modification of the service file, the enries will be listed as protocols.

    protocol

    Is an optional empty-element tag and can be used several times to have more than one protocol entry. A protocol entry has exactly one attribute:
    value="string"

    The protocol can be any protocol supported by the system. Please have a look at /etc/protocols for supported protocols.

    source-port

    Is an optional empty-element tag and can be used several times to have more than one source port entry. All attributes of a source port entry are mandatory:
    port="string"

    The port string can be a single port number or a port range portid-portid.

    protocol="string"

    The protocol value can either be tcpudpsctp or dccp.

    module

    Is an optional empty-element tag and can be used several times to enable more than one netfilter kernel helper for the service. A module entry has exactly one attribute:
    name="string"

    Defines the name of the kernel netfilter helper as a string.

    destination

    Is an optional empty-element tag and can be used only once. The destination specifies the destination network as a network IP address (optional with /mask), or a plain IP address. The use of hostnames is not recommended, because these will only be resolved at service activation and transmitted to the kernel. For more information in this element, please have a look at --destination in iptables(8) and ip6tables(8).
    ipv4="address[/mask]"

    The IPv4 destination address with optional mask.

    ipv6="address[/mask]"

    The IPv6 destination address with optional mask.

  • 相关阅读:
    Visualvm 远程测试 问题
    jsp中文件下载的实现
    MYOB 的一些开发资料
    连接MYOB ODBC,在MyEclipse 下Commit成功,在Tomcat下单独运行,Commit显示Connection 已经关闭
    也说说学习
    objectivec static变量的使用总结
    objective里面的单例模式
    对函数式编程简单理解
    个人技术生涯的感悟(2)
    苹果键盘快捷键图标
  • 原文地址:https://www.cnblogs.com/jimboi/p/8543904.html
Copyright © 2011-2022 走看看