Netgear SRX5308 SRX5308 Reference Manual - Page 89

Static Route Example, Table 3-5. RIP Configuration Settings continued - not connecting to modem

Page 89 highlights

ProSafe Gigabit Quad WAN SSL VPN Firewall SRX5308 Reference Manual Table 3-5. RIP Configuration Settings (continued) Setting Authentication for RIP-2B/2M required? (continued) Description (or Subfield and Description) Not Valid Before The beginning of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. Before this date and time, the MD5 key is not valid. Not Valid After The end of the lifetime of the MD5 key. Enter the month, date, year, hour, minute, and second. After this date and time, the MD5 key is no longer valid. 4. Click Apply to save your settings. Static Route Example In this example, we assume the following: • The VPN firewall's primary Internet access is through a cable modem to an ISP. • The VPN firewall is on a local LAN with IP address is 192.168.1.100. • The VPN firewall connects to a remote network where you must access a device. • The LAN IP address of the remote network is 134.177.0.0. When you first configured the VPN firewall, two implicit static routes were created: • A default static route was created with your ISP as the gateway. • A second static route was created to the local LAN for all 192.168.1.x addresses. With this configuration, if you attempt to access a device on the 134.177.0.0 remote network, the VPN firewall forwards your request to the ISP. In turn, the ISP forwards your request to the remote network, where the request is likely to be denied by the remote network's firewall. In this case you must define a static route, informing the VPN firewall that the 134.177.0.0 IP address should be accessed through the local LAN IP address (192.168.1.100). The static route on the VPN firewall must be defined as follows: • The destination IP address and IP subnet mask must specify that the static route applies to all 134.177.x.x IP addresses. • The gateway IP address must specify that all traffic for the 134.177.x.x IP addresses should be forwarded to the local LAN IP address (192.168.1.100). • A metric value of 1 should work since the VPN firewall is on the local LAN. • The static route can be made private only as a precautionary security measure in case RIP is activated. LAN Configuration v1.0, April 2010 3-29

  • 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
LAN Configuration
3-29
v1.0, April 2010
4.
Click
Apply
to save your settings.
Static Route Example
In this example, we assume the following:
The VPN firewall’s primary Internet access is through a cable modem to an ISP.
The VPN firewall is on a local LAN with IP address is 192.168.1.100.
The VPN firewall connects to a remote network where you must access a device.
The LAN IP address of the remote network is 134.177.0.0.
When you first configured the VPN firewall, two implicit static routes were created:
A default static route was created with your ISP as the gateway.
A second static route was created to the local LAN for all 192.168.1.x addresses.
With this configuration, if you attempt to access a device on the 134.177.0.0 remote network, the
VPN firewall forwards your request to the ISP. In turn, the ISP forwards your request to the remote
network, where the request is likely to be denied by the remote network’s firewall.
In this case you must define a static route, informing the VPN firewall that the 134.177.0.0 IP
address should be accessed through the local LAN IP address (192.168.1.100).
The static route on the VPN firewall must be defined as follows:
The destination IP address and IP subnet mask must specify that the static route applies to all
134.177.x.x IP addresses.
The gateway IP address must specify that all traffic for the 134.177.x.x IP addresses should be
forwarded to the local LAN IP address (192.168.1.100).
A metric value of 1 should work since the VPN firewall is on the local LAN.
The static route can be made private only as a precautionary security measure in case RIP is
activated.
Authentication for
RIP-2B/2M required?
(continued)
Not Valid Before
The beginning of the lifetime of the MD5 key. Enter the
month, date, year, hour, minute, and second. Before this
date and time, the MD5 key is not valid.
Not Valid After
The end of the lifetime of the MD5 key. Enter the month,
date, year, hour, minute, and second. After this date and
time, the MD5 key is no longer valid.
Table 3-5. RIP Configuration Settings (continued)
Setting
Description (or Subfield and Description)