Symantec 360R Administration Guide - Page 73

Redirecting services, To con a service

Page 73 highlights

Network traffic control 73 Configuring services port number. For protocols that use a single port number, the listen on port starting and ending port number is the same. Redirecting services You can also configure services to be redirected from the ports they would normally enter (Listen on Port) to another port (Redirect to Port). Service redirection only applies to inbound rules. Outbound rules ignore this setting. For example, to redirect inbound Web traffic entering on port 80 and using TCP protocol, to an internal Web server listening for TCP on port 8080, you would create a new service application called WEB_8080. Select TCP as the protocol, and type 80 for both the start and end Listen to Ports. For both the start and end Redirect To Ports, type 8080. Then create and enable an inbound rule for the Web application server that uses WEB_8080 as a service. Note: Redirection port range sizes must be the same as the Listen on port ranges. For example, if the Listen on port range is 21 to 25, the redirection port range must also be four ports. To redirect inbound traffic to the original destination port, leave the redirect fields blank. To configure a service Create a service before you add it to an inbound rule. Once you create a service, you can update or delete it. See "Services tab field descriptions" on page 182. To configure a service 1 In the SGMI, in the left pane, click Firewall. 2 Under Application Settings, in the Name text box, type a name for the service that represents the application. 3 In the Protocol drop-down list, select TCP or UDP. 4 In the Listen on Port(s): Start text box, type a port number. 5 In the Listen on Port(s): End text box, type a port number. 6 In the Redirect to Port(s): Start text box, type a port number. Redirect only applies to inbound rules. If you are creating a service for an outbound rule, leave the Redirect to Port(s) text boxes blank. To redirect inbound traffic to the original destination port, leave the Redirect text boxes blank.

  • 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
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

73
Network traffic control
Configuring services
port number. For protocols that use a single port number, the listen on port
starting and ending port number is the same.
Redirecting services
You can also configure services to be redirected from the ports they would
normally enter (Listen on Port) to another port (Redirect to Port). Service
redirection only applies to inbound rules. Outbound rules ignore this setting.
For example, to redirect inbound Web traffic entering on port 80 and using TCP
protocol, to an internal Web server listening for TCP on port 8080, you would
create a new service application called WEB_8080. Select TCP as the protocol,
and type 80 for both the start and end Listen to Ports. For both the start and end
Redirect To Ports, type 8080. Then create and enable an inbound rule for the
Web application server that uses WEB_8080 as a service.
Note:
Redirection port range sizes must be the same as the Listen on port
ranges. For example, if the Listen on port range is 21 to 25, the redirection port
range must also be four ports.
To redirect inbound traffic to the original destination port, leave the redirect
fields blank.
To configure a service
Create a service before you add it to an inbound rule. Once you create a service,
you can update or delete it.
See
“Services tab field descriptions”
on page 182.
To configure a service
1
In the SGMI, in the left pane, click
Firewall
.
2
Under Application Settings, in the Name text box, type a name for the
service that represents the application.
3
In the Protocol drop-down list, select
TCP
or
UDP
.
4
In the Listen on Port(s): Start text box, type a port number.
5
In the Listen on Port(s): End text box, type a port number.
6
In the Redirect to Port(s): Start text box, type a port number.
Redirect only applies to inbound rules. If you are creating a service for an
outbound rule, leave the Redirect to Port(s) text boxes blank.
To redirect inbound traffic to the original destination port, leave the
Redirect text boxes blank.