D-Link DFL-700 Product Manual - Page 29

Service Filter, Schedule, Custom TCP+UDP

Get D-Link DFL-700 - Security Appliance PDF manuals and user guides
UPC - 790069264535
View all D-Link DFL-700 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Source Users/Groups - Specifies if an authenticated username is needed for this policy to match. Simply make a list of usernames separated by commas (,), specify an entire user group, or write Any to indicate all authenticated users to enable authentication on this policy. If it is left blank there is no need for authentication for the policy. Destination Nets - Specifies the span of IP addresses to be compared to the destination IP of the received packet. Leave this blank to match everything. Destination Users/Groups - Specifies if an authenticated username is needed for this policy to match. Either make a list of usernames, separated by a comma (,) or write Any for any authenticated user. If it is left blank there is no need for authentication for the policy. Service Filter Either choose a predefined service from the dropdown menu or make a custom service. The following custom services exist: All - Matches all protocols. TCP+UDP+ICMP - This service matches all ports on either the TCP or the UDP protocol, including ICMP. Custom TCP - This service is based on the TCP protocol. Custom UDP - This service is based on the UDP protocol. Custom TCP+UDP - This service uses both the TCP and UDP protocols. The following is used when making a custom service: Custom source/destination ports - For many services, a single destination port is sufficient. The source port used most often are all ports, 0-65535. The http service, for instance, uses destination port 80. A port range can also be used, meaning that a range 137139 covers ports 137, 138, and 139. Multiple ranges or individual ports may also be entered, separated by commas. For instance, a service can be defined as having source ports 102465535 and destination ports 80-82, 90-92, and 95. In this case, a TCP or UDP packet with the destination port being one of 80, 81, 82, 90, 91, 92 or 95, and the source port being in the range 1024-65535, will match this service. Schedule If a schedule should be used for the policy, choose one from the dropdown menu. These are specified on the Schedules page. If the policy should always be active, choose Always from the dropdown menu.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
Source Users/Groups
– Specifies if an authenticated username is needed for this policy
to match. Simply make a list of usernames separated by commas (,), specify an entire user
group, or write
Any
to indicate all authenticated users to enable authentication on this policy.
If it is left blank there is no need for authentication for the policy.
Destination Nets
– Specifies the span of IP addresses to be compared to the destination
IP of the received packet. Leave this blank to match everything.
Destination Users/Groups
– Specifies if an authenticated username is needed for this
policy to match. Either make a list of usernames, separated by a comma (,) or write Any for
any authenticated user. If it is left blank there is no need for authentication for the policy.
Service Filter
Either choose a predefined service from the dropdown menu or make a custom service.
The following custom services exist:
All
–
Matches all protocols.
TCP+UDP+ICMP
–
This service matches all ports on either the TCP or the UDP protocol,
including ICMP.
Custom TCP
–
This service is based on the TCP protocol.
Custom UDP
–
This service is based on the UDP protocol.
Custom TCP+UDP
–
This service uses both the TCP and UDP protocols.
The following is used when making a custom service:
Custom source/destination ports –
For many services, a single destination port is
sufficient. The source port used most often are all ports, 0-65535. The http service, for
instance, uses destination port 80. A port range can also be used, meaning that a range 137-
139 covers ports 137, 138, and 139. Multiple ranges or individual ports may also be entered,
separated by commas. For instance, a service can be defined as having source ports 1024-
65535 and destination ports 80-82, 90-92, and 95. In this case, a TCP or UDP packet with the
destination port being one of 80, 81, 82, 90, 91, 92 or 95, and the source port being in the
range 1024-65535, will match this service.
Schedule
If a schedule should be used for the policy, choose one from the dropdown menu. These
are specified on the
Schedules
page. If the policy should always be active, choose Always
from the dropdown menu.