firehol-services - FireHOL services list
AH all amanda any anystateless apcupsd apcupsdnis aptproxy asterisk
darkstat daytime dcc dcpp dhcp dhcprelay dhcpv6 dict distcc dns
h323 heartbeat http httpalt https hylafax
iax iax2 ICMP icmp ICMPV6 icmpv6 icp ident imap imaps ipsecnatt ipv6error ipv6mld ipv6neigh ipv6router irc isakmp
microsoft_ds mms msn msnp ms_ds multicast mysql
netbackup netbios_dgm netbios_ns netbios_ssn nfs nis nntp nntps nrpe ntp nut nxserver
ping pop3 pop3s portmap postgres pptp privoxy
radius radiusold radiusoldproxy radiusproxy rdp rndc rsync rtp
samba sane sip smtp smtps snmp snmptrap socks squid ssh stun submission sunrpc swat syslog
telnet tftp time timestamp tomcat
vmware vmwareauth vmwareweb vnc
Example:
server AH acceptService Type:
Server Ports:
Client Ports:
Links
Notes
For more information see this Archive of the FreeS/WAN documentation and RFC 2402. [WIKI-AH]: http://en.wikipedia.org/wiki/IPsec#Authentication_Header
Example:
server all acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Notes
Matches all traffic (all protocols, ports, etc.). Note that to provide “connections in one direction with replies” semantics, the kernel connection tracker is still used: this will therefore still not match packets if they are not understood as part of a connection (e.g. some ICMPv6 packets, requests and replies taking different routes, complex protocols with no helper loaded).
This service may indirectly setup a set of other services, if they require kernel modules to be loaded. The following complex services are activated:
Service Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server any *myname* accept proto 47Service Type:
Server Ports:
Client Ports:
Notes
Matches all traffic (all protocols, ports, etc), but does not care about kernel modules and does not activate any other service indirectly. In combination with the firehol-params(5) this service can match unusual traffic (e.g. GRE - protocol 47).
Note that you have to supply your own name in addition to “any”.
Example:
server anystateless *myname* accept proto 47Service Type:
Server Ports:
Client Ports:
Notes
Matches all traffic (all protocols, ports, etc), but does not care about kernel modules and does not activate any other service indirectly. In combination with the firehol-params(5) this service can match unusual traffic (e.g. GRE - protocol 47).
This service is identical to “any” but does not care about the state of traffic.
Note that you have to supply your own name in addition to “anystateless”.
Example:
server apcupsd acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service must be defined as “server apcupsd accept” on all machines not directly connected to the UPS (i.e. slaves).
Note that the port defined here is not the default port (6666) used if you download and compile APCUPSD, since the default conflicts with IRC and many distributions (like Debian) have changed this to 6544.
You can define port 6544 in APCUPSD, by changing the value of NETPORT in its configuration file, or overwrite this FireHOL service definition using the procedures described in Adding Services in firehol.conf(5). [HOME-apcupsd]: http://www.apcupsd.com [WIKI-apcupsd]: http://en.wikipedia.org/wiki/Apcupsd
Example:
server apcupsdnis acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service allows the remote WEB interfaces of APCUPSD, to connect and get information from the server directly connected to the UPS device. [HOME-apcupsdnis]: http://www.apcupsd.com [WIKI-apcupsdnis]: http://en.wikipedia.org/wiki/Apcupsd
Example:
server aptproxy acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server asterisk acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service refers only to the manager interface of asterisk. You should normally enable sip, h323, rtp, etc. at the firewall level, if you enable the relative channel drivers of asterisk. [HOME-asterisk]: http://www.asterisk.org [WIKI-asterisk]: http://en.wikipedia.org/wiki/Asterisk_PBX
Example:
server cups acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server custom myimap tcp/143 default acceptService Type:
Server Ports:
Client Ports:
Notes
The full syntax is:
subcommand
customname svr-proto/ports cli-ports action paramsThis service is used by FireHOL to allow you create rules for services which do not have a definition.
subcommand, action and params have their usual meanings.A name must be supplied along with server ports in the form proto/range and client ports which takes only a range.
To define services with the built-in extension mechanism to avoid the need for
customservices, see Adding Services in firehol.conf(5).
Example:
server cvspserver acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server darkstat acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server daytime acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server dcc acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See also this DCC FAQ. [WIKI-dcc]: http://en.wikipedia.org/wiki/Distributed_Checksum_Clearinghouse
Example:
server dcpp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server dhcp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
The dhcp service is implemented as stateless rules.
DHCP clients broadcast to the network (src 0.0.0.0 dst 255.255.255.255) to find a DHCP server. If the DHCP service was stateful the iptables connection tracker would not match the packets and deny to send the reply.
Note that this change does not affect the security of either DHCP servers or clients, since only the specific ports are allowed (there is no random port at either the server or the client side).
Note also that the “server dhcp accept” or “client dhcp accept” commands should placed within interfaces that do not have src and / or dst defined (because of the initial broadcast).
You can overcome this problem by placing the DHCP service on a separate interface, without a src or dst but with a policy return. Place this interface before the one that defines the rest of the services.
For example:
interface eth0 dhcp
policy return
server dhcp accept
interface eth0 lan src "$mylan" dst "$myip"
client all acceptFor example: interface eth0 dhcp policy return server dhcp accept interface eth0 lan src “$mylan" dst "$myip” client all accept
This service implicitly sets its client or server to ipv4 mode. [WIKI-dhcp]: http://en.wikipedia.org/wiki/Dhcp
Example:
server dhcprelay acceptService Type:
Server Ports:
Client Ports:
Links
Notes
From RFC 1812 section 9.1.2:
In many cases, BOOTP clients and their associated BOOTP server(s) do not reside on the same IP (sub)network. In such cases, a third-party agent is required to transfer BOOTP messages between clients and servers. Such an agent was originally referred to as a BOOTP forwarding agent. However, to avoid confusion with the IP forwarding function of a router, the name BOOTP relay agent has been adopted instead.
For more information about DHCP Relay see section 9.1.2 of RFC 1812 and section 4 of RFC 1542 [WIKI-dhcprelay]: http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#DHCP_relaying
Example:
server dhcpv6 accept
client dhcpv6 acceptService Type:
Server Ports:
Client Ports:
Links
Notes
The dhcp service is implemented as stateless rules. It cannot be stateful as the connection tracker will not match a unicast reply to a broadcast request. Further, if you wish to add src/dst rule parameters, you must account for both the broadcast and link-local network prefixes.
Clients broadcast from a link-local address to the multicast address ff02::1:2 on UDP port 547 to find a server. The server sends a unicast reply back to the client which listens on UDP port 546.
For a FireHOL interface, creating a client will allow sending to port 547 and receiving on port 546. Creating a server allows sending to port 546 and receiving on port 547.
Unlike DHCP for IPv4, the source ports to be used are not defined in DHCPv6 - see section 5.2 of RFC3315. Some servers are known to make use of this to send from arbitrary ports, so FireHOL does not assume a source port.
This service implicitly sets its client or server to ipv6 mode. [WIKI-dhcpv6]: https://en.wikipedia.org/wiki/DHCPv6
Example:
server dict acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See RFC2229. [WIKI-dict]: http://en.wikipedia.org/wiki/DICT
Example:
server distcc acceptService Type:
Server Ports:
Client Ports:
Links
Notes
For distcc security, please check the distcc security design. [HOME-distcc]: https://code.google.com/p/distcc/ [WIKI-distcc]: http://en.wikipedia.org/wiki/Distcc
Example:
server dns acceptService Type:
Server Ports:
Client Ports:
Links
Notes
On very busy DNS servers you may see a few dropped DNS packets in your logs. This is normal. The iptables connection tracker will timeout the session and lose unmatched DNS packets that arrive too late to be useful. [WIKI-dns]: http://en.wikipedia.org/wiki/Domain_Name_System
Example:
server echo acceptService Type:
Server Ports:
Client Ports:
Links
Example:
client emule accept src 192.0.2.1Service Type:
Server Ports:
Client Ports:
Links
Notes
According to eMule Port Definitions, FireHOL defines:
- Accept from any client port to the server at tcp/4661
- Accept from any client port to the server at tcp/4662
- Accept from any client port to the server at udp/4665
- Accept from any client port to the server at udp/4672
- Accept from any server port to the client at tcp/4662
- Accept from any server port to the client at udp/4672
Use the FireHOL firehol-client(5) command to match the eMule client.
Please note that the eMule client is an HTTP client also. [HOME-emule]: http://www.emule-project.com
Example:
server eserver acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ESP acceptService Type:
Server Ports:
Client Ports:
Links
Notes
For more information see this Archive of the FreeS/WAN documentation RFC 2406. [WIKI-ESP]: http://en.wikipedia.org/wiki/IPsec#Encapsulating_Security_Payload
Example:
server finger acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ftp acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Notes
The FTP service matches both active and passive FTP connections. [WIKI-ftp]: http://en.wikipedia.org/wiki/Ftp
Example:
server gift acceptService Type:
Server Ports:
Client Ports:
Links
Notes
The gift FireHOL service supports:
- Gnutella listening at tcp/4302
- FastTrack listening at tcp/1214
- OpenFT listening at tcp/2182 and tcp/2472
The above ports are the defaults given for the corresponding giFT modules.
To allow access to the user interface ports of giFT, use the giftui. [HOME-gift]: http://gift.sourceforge.net [WIKI-gift]: http://en.wikipedia.org/wiki/GiFT
Example:
server giftui acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service refers only to the user interface ports offered by giFT. To allow gift accept P2P requests, use the gift. [HOME-giftui]: http://gift.sourceforge.net [WIKI-giftui]: http://en.wikipedia.org/wiki/GiFT
Example:
server gkrellmd acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server GRE acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Notes
Protocol No 47.
For more information see RFC RFC 2784. [WIKI-GRE]: http://en.wikipedia.org/wiki/Generic_Routing_Encapsulation
Example:
server h323 acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server heartbeat acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This FireHOL service has been designed such a way that it will allow multiple heartbeat clusters on the same LAN. [HOME-heartbeat]: http://www.linux-ha.org/
Example:
server http acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server httpalt acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This port is commonly used by web servers, web proxies and caches where the standard http port is not available or can or should not be used. [WIKI-httpalt]: http://en.wikipedia.org/wiki/Http
Example:
server https acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server hylafax acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service allows incoming requests to server port tcp/4559 and outgoing from server port tcp/4558.
The correct operation of this service has not been verified.
USE THIS WITH CARE. A HYLAFAX CLIENT MAY OPEN ALL TCP UNPRIVILEGED PORTS TO ANYONE (from port tcp/4558). [HOME-hylafax]: http://www.hylafax.org/ [WIKI-hylafax]: http://en.wikipedia.org/wiki/Hylafax
Example:
server iax acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service refers to IAX version 1. There is also iax2. [HOME-iax]: http://www.asterisk.org [WIKI-iax]: http://en.wikipedia.org/wiki/Iax
Example:
server iax2 acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This service refers to IAX version 2. There is also iax. [HOME-iax2]: http://www.asterisk.org [WIKI-iax2]: http://en.wikipedia.org/wiki/Iax
Example:
server ICMP acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ICMPV6 acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server icp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ident reject with tcp-resetService Type:
Server Ports:
Client Ports:
Links
Example:
server imap acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server imaps acceptService Type:
Server Ports:
Client Ports:
Links
Service Type:
Server Ports:
Client Ports:
Links
Example:
server ipv6error acceptService Type:
Server Ports:
Client Ports:
Notes
This service is not needed from 3.0.0. It will do nothing but issue a warning from 3.1.0; it will be removed in 4.0.0.
The linux connection tracker ensures that ICMPv6 errors are marked as RELATED. Since 3.0.0, these are automatially accepted by FireHOL, making a separate command redundant.
Example:
client ipv6mld acceptService Type:
Server Ports:
Client Ports:
Links
Notes
IPv6 uses Multicast Listener Discovery to discover multicast listeners and what they are listening for.
In practice all IPv6 nodes are multicast listeners since multicast is used in the neighbour discovery protocol which replaces ARP in IPv4.
These rules are stateless since reports can happen automatically as well as on query.
Unless muticast snooping is disabled across the network, MLD should be enabled for any clients:
client ipv6mld acceptMLD should also be enabled as a server on any hosts acting as a router:
server ipv6mld acceptThe rules should generally not be used to pass packets across a firewall (e.g. in a router definition) unless the firewall is for a bridge.
This service implicitly sets its client or server to ipv6 mode. [WIKI-ipv6mld]: https://en.wikipedia.org/wiki/Multicast_Listener_Discovery
Example:
client ipv6neigh accept
server ipv6neigh acceptService Type:
Server Ports:
Client Ports:
Links
Notes
IPv6 uses the Neighbour Discovery Protocol to do automatic configuration of routes and to replace ARP. To allow this functionality the network neighbour and router solicitation/advertisement messages should be enabled on each interface.
These rules are stateless since advertisement can happen automatically as well as on solicitation.
Neighbour discovery (incoming) should always be enabled:
server ipv6neigh acceptNeighbour advertisement (outgoing) should always be enabled:
client ipv6neigh acceptThe rules should not be used to pass packets across a firewall (e.g. in a router definition) unless the firewall is for a bridge.
This service implicitly sets its client or server to ipv6 mode. [WIKI-ipv6neigh]: https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol
Example:
client ipv6router acceptService Type:
Server Ports:
Client Ports:
Links
Notes
IPv6 uses the Neighbour Discovery Protocol to do automatic configuration of routes and to replace ARP. To allow this functionality the network neighbour and router solicitation/advertisement messages should be enabled on each interface.
These rules are stateless since advertisement can happen automatically as well as on solicitation.
Router discovery (incoming) should always be enabled:
client ipv6router acceptRouter advertisement (outgoing) should be enabled on a host that routes:
server ipv6router acceptThe rules should not be used to pass packets across a firewall (e.g. in a router definition) unless the firewall is for a bridge.
This service implicitly sets its client or server to ipv6 mode. [WIKI-ipv6router]: https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol
Example:
server irc acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server isakmp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
For more information see the Archive of the FreeS/WAN documentation [WIKI-isakmp]: http://en.wikipedia.org/wiki/ISAKMP
Example:
server jabber acceptService Type:
Server Ports:
Client Ports:
Links
Notes
Allows clear and SSL client-to-server connections. [WIKI-jabber]: http://en.wikipedia.org/wiki/Jabber
Example:
server jabberd acceptService Type:
Server Ports:
Client Ports:
Links
Notes
Allows clear and SSL client-to-server and server-to-server connections.
Use this service for a jabberd server. In all other cases, use the jabber. [WIKI-jabberd]: http://en.wikipedia.org/wiki/Jabber
Service Type:
Server Ports:
Client Ports:
Links
Example:
server ldap acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ldaps acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server lpd acceptService Type:
Server Ports:
Client Ports:
Links
Notes
LPD is documented in RFC 1179.
Since many operating systems incorrectly use the non-default client ports for LPD access, this definition allows any client port to access the service (in addition to the RFC defined 721 to 731 inclusive). [WIKI-lpd]: http://en.wikipedia.org/wiki/Line_Printer_Daemon_protocol
Example:
server microsoft_ds acceptService Type:
Server Ports:
Client Ports:
Notes
Direct Hosted (i.e. NETBIOS-less SMB)
This is another NETBIOS Session Service with minor differences with netbios_ssn. It is supported only by Windows 2000 and Windows XP and it offers the advantage of being independent of WINS for name resolution.
It seems that samba supports transparently this protocol on the netbios_ssn ports, so that either direct hosted or traditional SMB can be served simultaneously.
Please refer to the netbios_ssn for more information.
Example:
server mms acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Notes
Microsoft’s proprietary network streaming protocol used to transfer unicast data in Windows Media Services (previously called NetShow Services). [WIKI-mms]: http://en.wikipedia.org/wiki/Microsoft_Media_Server
Example:
server msn acceptService Type:
Server Ports:
Client Ports:
Example:
server msnp acceptService Type:
Server Ports:
Client Ports:
Example:
server multicast reject with proto-unreachService Type:
Server Ports:
Client Ports:
Links
Notes
The multicast service matches all packets sent to the $MULTICAST_IPS addresses using IGMP or UDP. For IPv4 that means 224.0.0.0/4 and for IPv6 FF00::/16. [WIKI-multicast]: http://en.wikipedia.org/wiki/Multicast
Example:
server mysql acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server netbackup accept
client netbackup acceptService Type:
Server Ports:
Client Ports:
Links
Notes
To use this service you must define it as both client and server in NetBackup clients and NetBackup servers. [WIKI-netbackup]: http://en.wikipedia.org/wiki/Netbackup
Example:
server netbios_dgm acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See also the samba.
Keep in mind that this service broadcasts (to the broadcast address of your LAN) UDP packets. If you place this service within an interface that has a dst parameter, remember to include (in the dst parameter) the broadcast address of your LAN too. [WIKI-netbios_dgm]: http://en.wikipedia.org/wiki/Netbios#Datagram_distribution_service
Example:
server netbios_ns acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See also the samba. [WIKI-netbios_ns]: http://en.wikipedia.org/wiki/Netbios#Name_service
Example:
server netbios_ssn acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See also the samba.
Please keep in mind that newer NETBIOS clients prefer to use port 445 (microsoft_ds) for the NETBIOS session service, and when this is not available they fall back to port 139 (netbios_ssn). Versions of samba above 3.x bind automatically to ports 139 and 445.
If you have an older samba version and your policy on an interface or router is DROP, clients trying to access port 445 will have to timeout before falling back to port 139. This timeout can be up to several minutes.
To overcome this problem you can explicitly REJECT the microsoft_ds with a tcp-reset message:
server microsoft_ds reject with tcp-reset [WIKI-netbios_ssn]: http://en.wikipedia.org/wiki/Netbios#Session_service
Example:
client nfs accept dst 192.0.2.1Service Type:
Server Ports:
Client Ports:
Links
Notes
The NFS service queries the RPC service on the NFS server host to find out the ports nfsd, mountd, lockd and rquotad are listening. Then, according to these ports it sets up rules on all the supported protocols (as reported by RPC) in order the clients to be able to reach the server.
For this reason, the NFS service requires that:
- the firewall is restarted if the NFS server is restarted
- the NFS server must be specified on all nfs statements (only if it is not the localhost)
Since NFS queries the remote RPC server, it is required to also be allowed to do so, by allowing the portmap too. Take care that this is allowed by the running firewall when FireHOL tries to query the RPC server. So you might have to setup NFS in two steps: First add the portmap service and activate the firewall, then add the NFS service and restart the firewall.
To avoid this you can setup your NFS server to listen on pre-defined ports, as documented in NFS Howto. If you do this then you will have to define the the ports using the procedure described in Adding Services in firehol.conf(5).
Example:
client nis accept dst 192.0.2.1Service Type:
Server Ports:
Client Ports:
Links
Notes
The nis service queries the RPC service on the nis server host to find out the ports ypserv and yppasswdd are listening. Then, according to these ports it sets up rules on all the supported protocols (as reported by RPC) in order the clients to be able to reach the server.
For this reason, the nis service requires that:
- the firewall is restarted if the nis server is restarted
- the nis server must be specified on all nis statements (only if it is not the localhost)
Since nis queries the remote RPC server, it is required to also be allowed to do so, by allowing the portmap too. Take care that this is allowed by the running firewall when FireHOL tries to query the RPC server. So you might have to setup nis in two steps: First add the portmap service and activate the firewall, then add the nis service and restart the firewall.
This service was added to FireHOL by Carlos Rodrigues. His comments regarding this implementation, are:
These rules work for client access only!
Pushing changes to slave servers won’t work if these rules are active somewhere between the master and its slaves, because it is impossible to predict the ports where yppush will be listening on each push.
Pulling changes directly on the slaves will work, and could be improved performance-wise if these rules are modified to open fypxfrd. This wasn’t done because it doesn’t make that much sense since pushing changes on the master server is the most common, and recommended, way to replicate maps. [WIKI-nis]: http://en.wikipedia.org/wiki/Network_Information_Service
Example:
server nntp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server nntps acceptService Type:
Server Ports:
Client Ports:
Links
Service Type:
Server Ports:
Client Ports:
Links
Example:
server ntp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server nut acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server nxserver acceptService Type:
Server Ports:
Client Ports:
Links
Notes
Default ports used by NX server for connections without encryption.
Note that nxserver also needs the ssh to be enabled.
This information has been extracted from this The TCP ports used by nxserver are 4000 + DISPLAY_BASE to 4000 + DISPLAY_BASE + DISPLAY_LIMIT. DISPLAY_BASE and DISPLAY_LIMIT are set in /usr/NX/etc/node.conf and the defaults are DISPLAY_BASE=1000 and DISPLAY_LIMIT=200.
For encrypted nxserver sessions, only ssh is needed. [WIKI-nxserver]: http://en.wikipedia.org/wiki/NX_Server
Service Type:
Server Ports:
Client Ports:
Links
Example:
server oracle acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server OSPF acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ping acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This services matches requests of protocol ICMP and type echo-request (TYPE=8) and their replies of type echo-reply (TYPE=0).
The ping service is stateful. [WIKI-ping]: http://en.wikipedia.org/wiki/Ping
Example:
server pop3 acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server pop3s acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server portmap acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server postgres acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server pptp acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server privoxy acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server radius acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server radiusold acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server radiusoldproxy acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server radiusproxy acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server rdp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
Remote Desktop Protocol is also known also as Terminal Services. [WIKI-rdp]: http://en.wikipedia.org/wiki/Remote_Desktop_Protocol
Example:
server rndc acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server rsync acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server rtp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
RTP ports are generally all the UDP ports. This definition narrows down RTP ports to UDP 10000 to 20000. [WIKI-rtp]: http://en.wikipedia.org/wiki/Real-time_Transport_Protocol
Example:
server samba acceptService Type:
Server Ports:
Client Ports:
Links
Notes
The samba service automatically sets all the rules for netbios_ns, netbios_dgm, netbios_ssn and microsoft_ds.
Please refer to the notes of the above services for more information.
NETBIOS initiates based on the broadcast address of an interface (request goes to broadcast address) but the server responds from its own IP address. This makes the “server samba accept” statement drop the server reply, because of the way the iptables connection tracker works.
This service definition includes a hack, that allows a Linux samba server to respond correctly in such situations, by allowing new outgoing connections from the well known netbios_ns port to the clients high ports.
However, for clients and routers this hack is not applied because it would open all unprivileged ports to the samba server. The only solution to overcome the problem in such cases (routers or clients) is to build a trust relationship between the samba servers and clients. [HOME-samba]: http://www.samba.org/ [WIKI-samba]: http://en.wikipedia.org/wiki/Samba_(software)
Service Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server sip acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Notes
SIP is an IETF standard protocol (RFC 2543) for initiating interactive user sessions involving multimedia elements such as video, voice, chat, gaming, etc. SIP works in the application layer of the OSI communications model. [WIKI-sip]: http://en.wikipedia.org/wiki/Session_Initiation_Protocol
Example:
server smtp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server smtps acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server snmp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server snmptrap acceptService Type:
Server Ports:
Client Ports:
Links
Notes
An SNMP trap is a notification from an agent to a manager. [WIKI-snmptrap]: http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#Trap
Example:
server socks acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See also RFC 1928. [WIKI-socks]: http://en.wikipedia.org/wiki/SOCKS
Example:
server squid acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server ssh acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server stun acceptService Type:
Server Ports:
Client Ports:
Links
Notes
STUN is a protocol for assisting devices behind a NAT firewall or router with their packet routing. [WIKI-stun]: http://en.wikipedia.org/wiki/STUN
Example:
server submission acceptService Type:
Server Ports:
Client Ports:
Links
Notes
Submission is essentially normal SMTP with an SSL/TLS negotiation. [WIKI-submission]: http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol
Example:
server swat acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server syslog acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server telnet acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server tftp acceptService Type:
Server Ports:
Client Ports:
Netfilter Modules
Netfilter NAT Modules
Links
Example:
server time acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server timestamp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
This services matches requests of protocol ICMP and type timestamp-request (TYPE=13) and their replies of type timestamp-reply (TYPE=14).
The timestamp service is stateful. [WIKI-timestamp]: http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Timestamp
Example:
server upnp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
For a Linux implementation see: Linux IGD. [HOME-upnp]: http://upnp.sourceforge.net/ [WIKI-upnp]: http://en.wikipedia.org/wiki/Universal_Plug_and_Play
Example:
server uucp acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server vmware acceptService Type:
Server Ports:
Client Ports:
Notes
Used from VMWare 1 and up. See the VMWare KnowledgeBase.
Example:
server vmwareauth acceptService Type:
Server Ports:
Client Ports:
Notes
Used from VMWare 1 and up. See the VMWare KnowledgeBase.
Example:
server vmwareweb acceptService Type:
Server Ports:
Client Ports:
Notes
Used from VMWare 2 and up. See VMWare Server 2.0 release notes and the VMWare KnowledgeBase.
Example:
server vnc acceptService Type:
Server Ports:
Client Ports:
Links
Notes
VNC is a graphical desktop sharing protocol. [WIKI-vnc]: http://en.wikipedia.org/wiki/Virtual_Network_Computing
Example:
server webmin acceptService Type:
Server Ports:
Client Ports:
Links
Example:
server whois acceptService Type:
Server Ports:
Client Ports:
Links
Example:
client xbox acceptService Type:
Server Ports:
Client Ports:
Notes
Definition for the Xbox live service.
See program source for contributor details.
Example:
server xdmcp acceptService Type:
Server Ports:
Client Ports:
Links
Notes
See Gnome Display Manager for a discussion about XDMCP and firewalls (Gnome Display Manager is a replacement for XDM). [WIKI-xdmcp]: http://en.wikipedia.org/wiki/X_display_manager_(program_type)#X_Display_Manager_Control_Protocol