[an error occurred while processing this directive][an error occurred while processing this directive]

option-82 (DHCP Relay Agent)

Syntax

option-82 <circuit-id> <remote-id>;

Hierarchy Level

[edit forwarding-options dhp-relay authentication username-include],[edit forwarding-options dhp-relay group group-name authentication username-include],[edit logical-systems logical-system-name forwarding-options dhcp-relay authentication username-include],[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name authentication username-include],[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay authentication username-include],[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay group group-name authentication username-include],[edit routing-instances routing-instance-name forwarding-options dhcp-relay authentication username-include],[edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name authentication username-include]

Release Information

Statement introduced in JUNOS Release 9.1.

Description

Specify the option 82 that is concatenated with the username during the subscriber authentication process. You can specify either, both, or neither the Agent Circuit ID and the Agent Remote ID suboptions. If you specify both, the Agent Circuit ID is supplied first, followed by a delimiter, and then the Agent Remote ID. If neither suboption is supplied, the raw payload of option 82 is concatenated to the username.

Note: The option 82 value used in creating the username is based on the option 82 value that is encoded in the outgoing (relayed) PDU.

Options

circuit-id—The string for the Agent Circuit ID suboption (suboption 1).

remote-id—The string for the Agent Remote ID suboption (suboption 2).

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.


Published: 2010-04-15

[an error occurred while processing this directive]