4-28
Stinger®
IP2000 Configuration Guide
IP Router Configuration
Configuring
ip-route
profiles
Sample DHCP option 82 configuration
This example builds on the sample DHCP relay configuration described in “Sample
DHCP relay configuration” on page 4-26. The
connection
profile to the CPE router in
that sample configuration does not require any changes to support option 82.
For sites that support option 82, the DHCP server configuration typically requires the
presence of an ID in DHCP queries. For example, the DHCP server in this example is
configured to recognize the CPE router at 3.3.3.3 across interface 7.7.7.7, and to
require a circuit ID. If the DHCP request forwarded to the server by the IP2000 does
not contain the circuit ID, the server refuses to return an address.
The following commands configure the IP2000 for DHCP option 82:
admin> read ip-global
admin> list bootp-relay
[in IP-GLOBAL:bootp-relay]
active = yes
bootp-servers = [ 2.2.2.142 0.0.0.0 ]
relay-agent-information = { { no 0.0.0.0 } { no 0.0.0.0 } }
The next commands enable the circuit identifier suboption of DHCP option 82 and
specify the Gigabit Ethernet address as the ID:
admin> set relay-agent-information circuit-id enable = yes
admin> set relay-agent-information circuit-id if-id = 2.2.2.2
admin> write -f
Configuring
ip-route
profiles
Any profile that specifies how to reach an IP device or subnet (such as an
ip-interface
,
connection
, or RADIUS user profile) specifies a static IP route to that
destination. However, you can also configure static routes explicitly, to extend or
fine-tune the routing table.
remote-id:enable
Enable/disable the remote identifier suboption of DHCP
option 82. If enabled, the IP2000 encodes a globally
unique identifier of the remote CPE from which it
received a DHCP client-to-server packet, to ensure that
DHCP responses are sent back to the proper remote
client. The IP2000 can use this field in addition to or
instead of the circuit-id field.
remote-id:if-ip
IP address of one of the IP2000 IP interfaces. If both IDs
are enabled, only one interface IP address is needed. If
no address is specified in this field or in the
if-ip
field
of an enabled
circuit-id
subprofile, the Stinger uses
the system address (
ip-global:system-ip-addr
) if that
value has been defined.
Parameter
Setting