Setting Dhcpv6 Overview - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01 Manual

Configuring screenos devices guide
Hide thumbs Also See for NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01:
Table of Contents

Advertisement

Table 22: Management Service Options (continued)
Service Options
SNMP
SSL
Global Pro (Security Manager)
Ping
Ident-Reset
NSGP
Related
Documentation

Setting DHCPv6 Overview

Copyright © 2010, Juniper Networks, Inc.
Your Action
Select this option to enable SNMP manageability. The security device supports both
SNMPv1 and SNMPv2c, and all relevant Management Information Base II (MIB II) groups,
as defined in RFC1213.
Select this option to enable the interface to receive HTTPS traffic for secure
management of the security device using the Web UI. Additionally, when this option is
enabled, you can also require WebAuth users to use SSL when connecting to the
WebAuth IP address on a device running ScreenOS 5.1 and later.
Select this option to enable the interface to receive NSM traffic.
Select this option to enable the interface to respond to an ICMP echo request, or ping,
which determines whether a specific IP address is accessible over the network.
Select this option to restore access that has been blocked by an unacknowledged
identification request. Services like Mail and FTP send identification requests. If they
receive no acknowledgement, they send the request again. While the request is
processing, there is no user access. The Ident-reset option sends a TCP reset
announcement in response to an IDENT request to port 113.
Select this option to enable the interface to handle NSGP traffic. When enabled, you
can also select to enforce IPsec authentication for NSGP traffic.
Setting Interface Properties Using the General Properties Screen on page 53
Setting Physical Link Attributes for Interfaces on page 55
An IPv6 router can only be a DHCPv6 server and an IPv6 host can only be a DHCP client.
As a DHCPv6 client, the interface can make the following requests from a DHCPv6 server:
Delegation of long-lived prefixes across an administrative boundary—The server does
not have to know the topology of the targeted local network. For example, an ISP can
use DHCPv6 to assign prefixes to downstream networks through downstream DHCP
clients. To speed up the client/server interaction, the client can request rapid commit
(if enabled). Rapid commit reduces the number of messages from four to two.
IP addresses of available DNS servers—The interface can also request DNS search-list
information. This list contains partial domain names, which assist DNS searches by
concatenating entered usernames to the domain names.
As a DHCPv6 server, the interface can provide both of these services to a DHCPv6 client.
To speed up prefix delegation, an IPv6 router configured to be a DHCPv6 server can
support a rapid commit option. You can also set a server preference option.
In the DHCPv6 screen, you can configure options such as a device-unique identification
(DUID), an identity association for prefix delegation identification (IAPD-ID), prefix
Chapter 3: Network Settings
57

Advertisement

Table of Contents
loading

Table of Contents