Boot protocol (bootp) requests to other networks – Lucent Technologies 6000 User Manual
Page 377

Configuring IP Routing
Configuring system-level routing policies
MAX 6000/3000 Network Configuration Guide
9-13
advertises the entire pool as a route, and only privately knows which IP addresses in the pool 
are active, a remote network can improperly send the MAX unit a packet for an inactive IP 
address. Depending on the static-route specification, these packets are either bounced with an 
ICMP host unreachable message or silently discarded.
For example, the following static route specifies the black-hole interface, so it silently discards 
all packets whose destination falls in the pool’s subnet. In addition to the Dest and Gateway 
parameters that define the pool, be sure you have set the Metric, Preference, Cost, and Private 
parameters as shown.
Ethernet
Static Rtes
pool-net
Name=pool-net
Active=Yes
Dest=10.12.253.0/26
Gateway=127.0.0.0
Preference=0
Metric=0
Cost=0
Private=No
The routing table contains the following lines:
D
estination Gateway IF Flg Pref Met Use Age
10.12.253.0/26 - bh0 C 0 0 0 172162
127.0.0.0/32 - bh0 CP 0 0 0 172163
127.0.0.1/32 - lo0 CP 0 0 0 172163
127.0.0.2/32 - rj0 CP 0 0 0 172163
When you configure Connection profiles to assign IP addresses from the pool, make sure you 
set the Private parameter to Yes. For example:
Ethernet
Connections
Connection profile
Ip options...
LAN Adrs=0.0.0.0/0
WAN Alias=0.0.0.0
IF Adrs=0.0.0.0/0
Preference=100
Cost=0
Private=Yes
RIP=Off
Pool=1
Boot Protocol (BOOTP) requests to other networks
By default, a MAX unit does not relay Boot Protocol (BOOTP) requests to other networks. 
You can enable it to do so by setting parameters in the Ethernet > Mod Config > BOOTP Relay 
profile.
To configure the unit to enable BOOTP relay, you must set the Boot Relay Enable parameter to 
Yes. In addition, you must disable Ethernet > Mod Config > TServ Options > SLIP BOOTP. 
