Dell PowerConnect J-8216 Release Notes JUNOS version 10.3 - Page 45

Errata for the Junos OS Hardware Documentation

Page 45 highlights

Errata and Changes in Documentation for Junos OS Release 10.3 for J-SRX Series Services Gateways procedure, however, is incorrect. This command would forward users to my-website.com before authentication, not after. To redirect users after authentication, the command must include: • The IP address of the Infranet Controller to be used for authentication • The ?target= option and URL to distinguish a forwarding address to be used after authentication • Escape characters substituted for any special characters in the URL name The following text in Step 2 is incorrect: [edit services unified-access-control] user@host# set captive-portal my-captive-portal-policy redirect-url https://my-website.com The correct text for Step 2 is as follows: [edit services unified-access-control] user@host# set captive-portal my-captive-portal-policy redirect-url https://192.168.0.100/?target=my%2Dwebsite%2Ecom • In the "Example: Configuring an IPsec Phase 2 Proposal (CLI)" section of the Junos OS Security Configuration Guide, the second paragraph of the first example states that the SA, ". . . terminates after 1800 KB of data pass through it." It should instead say, ". . . after 1800 seconds." • In the "Example: Accommodating End-to-End TCP Communication for J Series Services Routers" section of the Junos OS Security Configuration Guide, one CLI command given in the example in both the CLI Quick Configuration and Step-by-Step Procedure is incomplete. The set security flow tcp-mss all-tcp command must be followed by the keyword mss value. Therefore, the CLI example in both cases should read set security flow tcp-mss all-tcp mss 1400. • In the section "Example: Using NAT and the H.323 ALG to Enable Incoming Calls (CLI)" in the Junos OS Security Configuration Guide, the following text is incorrect: user@host# set security policy from-zone zone1 to-zone zone2 policy zone1_to_zone2 then permit source-nat pool p1 The correct text is as follows: user@host# set security policy from-zone zone1 to-zone zone2 policy zone1_to_zone2 then permit • The "Using NAT and the H.323 ALG to Enable Incoming Calls" example uses the old NAT version. The example has been revised to use the new NAT version in Junos OS Release 10.4. • The "Configuring Static NAT for Incoming SIP Calls" example incorrectly states the command to configure static NAT as set security nat interface ge-0/0/2.0 static-nat 1.1.1.3/32 host 10.1.1.3/32. The example has been reworked in Junos OS Release 10.4. Errata for the Junos OS Hardware Documentation This section lists outstanding issues with the hardware documentation. 45

  • 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

procedure, however, is incorrect. This command would forward users to
my-website.com before authentication, not after.
To redirect users after authentication, the command must include:
The IP address of the Infranet Controller to be used for authentication
The
?target=
option and URL to distinguish a forwarding address to be used after
authentication
Escape characters substituted for any special characters in the URL name
The following text in Step 2 is incorrect:
[edit services unified-access-control]
user@host#
set captive-portal my-captive-portal-policy redirect-url
https://my-website.com
The correct text for Step 2 is as follows:
[edit services unified-access-control]
user@host#
set captive-portal my-captive-portal-policy redirect-url
In the “Example: Configuring an IPsec Phase 2 Proposal (CLI)” section of the
Junos OS
Security Configuration Guide
, the second paragraph of the first example states that the
SA, “. . . terminates after 1800 KB of data pass through it.” It should instead say, “. . .
after 1800 seconds.”
In the “Example: Accommodating End-to-End TCP Communication for J Series Services
Routers” section of the
Junos OS Security Configuration Guide
, one CLI command given
in the example in both the CLI Quick Configuration and Step-by-Step Procedure is
incomplete. The
set security flow tcp-mss all-tcp
command must be followed by the
keyword
mss value
. Therefore, the CLI example in both cases should read
set security
flow tcp-mss all-tcp mss 1400.
In the section "Example: Using NAT and the H.323 ALG to Enable Incoming Calls (CLI)"
in the
Junos OS Security Configuration Guide
, the following text is incorrect:
user@host# set security policy from-zone zone1 to-zone zone2 policy zone1_to_zone2
then permit source-nat pool p1
The correct text is as follows:
user@host# set security policy from-zone zone1 to-zone zone2 policy zone1_to_zone2
then permit
The “Using NAT and the H.323 ALG to Enable Incoming Calls” example uses the old
NAT version. The example has been revised to use the new NAT version in Junos OS
Release 10.4.
The “Configuring Static NAT for Incoming SIP Calls” example incorrectly states the
command to configure static NAT as
set security nat interface ge-0/0/2.0 static-nat
1.1.1.3/32 host 10.1.1.3/32
. The example has been reworked in Junos OS Release 10.4.
Errata for the Junos OS Hardware Documentation
This section lists outstanding issues with the hardware documentation.
45
Errata and Changes in Documentation for Junos OS Release 10.3 for J-SRX Series Services Gateways