Tcp And Udp Based Services; Viewing A Specific Service - D-Link NetDefend DFL-210 User Manual

Network security firewall ver 2.26.01
Hide thumbs Also See for NetDefend DFL-210:
Table of Contents

Advertisement

3.2.2. TCP and UDP Based Services

Example 3.7. Viewing a Specific Service
To view a specific service in the system:
Command-Line Interface
gw-world:/> show Service ServiceTCPUDP echo
The output will look similar to the following listing:
Property
-----------------
DestinationPorts:
SourcePorts:
PassICMPReturn:
MaxSessions:
Comments:
Web Interface
1.
Go to Objects > Services
2.
Select the specific service object in the table
3.
A listing all services will be presented
3.2.2. TCP and UDP Based Services
Most applications are using TCP and/or UDP as transport protocol for transferring application data
over IP networks.
TCP (Transmission Control Protocol) is a connection-oriented protocol that, among other things,
includes mechanisms for reliable transmission of data. TCP is used by many common applications
where error-free transfers are mandatory, such as HTTP, FTP and SMTP.
Streaming Applications
For other types of applications where data delivery speed is of greater importance, for example with
streaming audio and video, User Datagram Protocol (UDP) is the preferred protocol. UDP is
connectionless, provides minimal transmission error recovery, and has a much lower overhead when
compared with TCP. Due to the lower overhead, UDP is also used for some non-streaming services
and in those cases the applications themselves must provide any error recovery mechanisms.
TCP and UDP Service Definition
To define a TCP or UDP based protocol to NetDefendOS, a TCP/UDP service object is used. Apart
from a unique name describing the service, the object contains information about what protocol
(TCP, UDP or both) and what source and destination ports are applicable for the service.
Specifying Port Numbers
Port numbers can be specified in a number of ways. These are:
Single Port
Value
----------------
Name:
echo
7
Type:
TCPUDP (TCP/UDP)
0-65535
No
ALG:
(none)
1000
Echo service
For many services, a single destination port is sufficient. For
example, HTTP uses destination port 80 in most cases. SMTP
81
Chapter 3. Fundamentals

Advertisement

Table of Contents
loading

Table of Contents