Is there any way to prevent the BOOTP client from injecting a default
route? When I originally set things up our DHCP server would not send
a default route because there was no gateway, local only. If you
leave out the default route, the server will try proxy-arp when ends
up putting a default route to itself in the routing table.
The problem is that on startup the servers actually setup static
networks with default routes out another interface. The problem is,
if the BOOTP client puts in a default route, we cannot easily add
another default because one already exists.
The only way I've found around this behavior was to error the BOOTP
client out and send it a default gateway that does not exist on the
local net the DHCP server provides. This causes the BOOTP client not
to set a default route and all works fine. Obviously this seems like
a cobb/hack and was wondering if there was a BOOTP option or kernel
tweak that can be done to tell the BOOTP client not to use proxy-arp.
--
Robert Blayzor, BOFH
INOC, LLC
rblayzor@inoc.net
http://www.inoc.net/~rblayzor/
