Netgear SRX5308 SRX5308 Reference Manual - Page 259

Services, WAN destination IP address, LAN users, Single address, Address range, Groups, Warning

Page 259 highlights

ProSafe Gigabit Quad WAN SSL VPN Firewall SRX5308 Reference Manual Warning: This feature is for advanced administrators only! Incorrect configuration might cause serious problems. Each rule lets you specify the desired action for the connections covered by the rule: • BLOCK always • BLOCK by schedule, otherwise Allow • ALLOW always • ALLOW by schedule, otherwise Block The following section summarizes the various criteria that you can apply to inbound rules and that might increase traffic. For more information about inbound rules, see "Inbound Rules (Port Forwarding)" on page 4-6. For detailed procedures on how to configure inbound rules, see "Setting LAN WAN Rules" on page 4-11 and "Setting DMZ WAN Rules" on page 4-14. When you define inbound firewall rules, you can further refine their application according to the following criteria: • Services. You can specify the services or applications to be covered by an inbound rule. If the desired service or application does not appear in the list, you must define it using the Services screen (see "Services-Based Rules" on page 4-3 and "Adding Customized Services" on page 4-31). • WAN destination IP address. You can specify the destination IP address for incoming traffic. Traffic is directed to the specified address only when the destination IP address of the incoming packet matches the IP address of the selected WAN interface. • LAN users. You can specify which computers on your network are affected by an inbound rule. There are several options: - Any. The rule applies to all PCs and devices on your LAN. - Single address. The rule applies to the address of a particular PC. - Address range. The rule applies to a range of addresses. - Groups. The rule is applied to a group of PCs. (You can configure groups for LAN WAN outbound rules but not for DMZ WAN outbound rules.) The Known PCs and Devices table is an automatically maintained list of all known PCs and network devices and is generally referred to as the network database, which is described in "Managing the Network Database" on page 3-15. PCs and network devices are entered into the network database by various methods that are described in "Managing Groups and Hosts (LAN Groups)" on page 3-14. Network and System Management 8-5 v1.0, April 2010

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384

ProSafe Gigabit Quad WAN SSL VPN Firewall SRX5308 Reference Manual
Network and System Management
8-5
v1.0, April 2010
Each rule lets you specify the desired action for the connections covered by the rule:
BLOCK always
BLOCK by schedule, otherwise Allow
ALLOW always
ALLOW by schedule, otherwise Block
The following section summarizes the various criteria that you can apply to inbound rules and that
might increase traffic. For more information about inbound rules, see
“Inbound Rules (Port
Forwarding)” on page 4-6
. For detailed procedures on how to configure inbound rules, see
“Setting LAN WAN Rules” on page 4-11
and
“Setting DMZ WAN Rules” on page 4-14
.
When you define inbound firewall rules, you can further refine their application according to the
following criteria:
Services
. You can specify the services or applications to be covered by an inbound rule. If the
desired service or application does not appear in the list, you must define it using the Services
screen (see
“Services-Based Rules” on page 4-3
and
“Adding Customized Services” on
page 4-31
).
WAN destination IP address
. You can specify the destination IP address for incoming traffic.
Traffic is directed to the specified address only when the destination IP address of the
incoming packet matches the IP address of the selected WAN interface.
LAN users
.
You can specify which computers on your network are affected by an inbound
rule. There are several options:
Any
.
The rule applies to all PCs and devices on your LAN.
Single address
.
The rule applies to the address of a particular PC.
Address range
. The rule applies to a range of addresses.
Groups
.
The rule is applied to a group of PCs. (You can configure groups for LAN WAN
outbound rules but not for DMZ WAN outbound rules.) The Known PCs and Devices
table is an automatically maintained list of all known PCs and network devices and is
generally referred to as the network database, which is described in
“Managing the
Network Database” on page 3-15
. PCs and network devices are entered into the network
database by various methods that are described in
“Managing Groups and Hosts (LAN
Groups)” on page 3-14
.
Warning:
This feature is for advanced administrators only! Incorrect configuration
might cause serious problems.