SonicWALL TZ 190 Benutzerhandbuch

Seite von 843
Firewall > Services
449
SonicOS Enhanced 4.0 Administrator Guide
Supported Protocols
The following IP protocols are available for custom services:
  •
ICMP (1)—(Internet Control Message Protocol) A TCP/IP protocol used to send error and 
control messages. 
  •
IGMP (2)—(Internet Group Management Protocol) The protocol that governs the 
management of multicast groups in a TCP/IP network.
  •
TCP (6)—(Transmission Control Protocol) The TCP part of TCP/IP. TCP is a transport 
protocol in TCP/IP. TCP ensures that a message is sent accurately and in its entirety.
  •
UDP (17)—(User Datagram Protocol) A protocol within the TCP/IP protocol suite that is 
used in place of TCP when a reliable delivery is not required.
  •
GRE (47)—(Generic Routing Encapsulation) A tunneling protocol used to encapsulate a 
wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link 
to firewalls or routing devices over an IP internetwork.
  •
ESP (50)—(Encapsulated Security Payload) A method of encapsulating an IP datagram 
inside of another datagram employed as a flexible method of data transportation by IPsec.
  •
AH (51)—(Authentication Header) A security protocol that provides data authentication and 
optional anti-relay services. AH is embedded in the data to be protected (a full IP 
datagram).
  •
EIGRP (88)—(Enhanced Interior Gateway Routing Protocol) Advanced version of IGRP. 
Provides superior convergence properties and operating efficiency, and combines the 
advantages of link state protocols with those of distance vector protocols.
  •
OSPF (89)—(Open Shortest Path First) A routing protocol that determines the best path for 
routing IP traffic over a TCP/IP network based on distance between nodes and several 
quality parameters. OSPF is an interior gateway protocol (IGP), which is designed to work 
within an autonomous system. It is also a link state protocol that provides less router to 
router update traffic than the RIP protocol (distance vector protocol) that it was designed to 
replace.
  •
PIMSM (103)—(Protocol Independent Multicast Sparse Mode) One of two PIM operational 
modes (dense and sparse). PIM sparse mode tries to constrain data distribution so that a 
minimal number of routers in the network receive it. Packets are sent only if they are 
explicitly requested at the RP (rendezvous point). In sparse mode, receivers are widely 
distributed, and the assumption is that downstream networks will not necessarily use the 
datagrams that are sent to them. The cost of using sparse mode is its reliance on the 
periodic refreshing of explicit join messages and its need for RPs. 
  •
L2TP (115)—(Layer 2 Tunneling Protocol) A protocol that allows a PPP session to run over 
the Internet. L2TP does not include encryption, but defaults to using IPsec in order to 
provide virtual private network (VPN) connections from remote users to the corporate LAN.
Adding Custom Services for Predefined Service Types
You can add a custom service for any of the predefined service types:
Protocol
IP Number
ICMP
1
TCP
6
UDP
17