Classful routing is no longer widely used. Our current support
for DHCP option 33 (DHO_STATIC_ROUTES) does not treat the provided
information as classful routes but as host routes.
Is this deliberate or accidental on our part?
If accidental I would recommend the diff below, removing the handling
of this option, and then looking into providing support for option
121 (classless static routes). Rather than fixing classful routes.
Thoughts?
.... Ken
Index: dhclient-script
===================================================================
RCS file: /cvs/src/sbin/dhclient/dhclient-script,v
retrieving revision 1.21
diff -u -p -r1.21 dhclient-script
--- dhclient-script 4 Apr 2011 12:22:41 -0000 1.21
+++ dhclient-script 7 Apr 2011 16:01:36 -0000
@@ -54,15 +54,6 @@ delete_old_routes() {
# Delete existing default route. We only allow one, so no need to
# process $old_routers list.
route -q $rdomain -n flush -inet -iface $interface
-
- if [ -n "$old_static_routes" ]; then
- set $old_static_routes
- while [ $# -gt 1 ]; do
- route -q $rdomain delete "$1" "$2"
- shift; shift
- done
- fi
-
arp -dan
}
@@ -78,14 +69,6 @@ add_new_routes() {
# stop processing the list after the first one.
break
done
-
- if [ -n "$new_static_routes" ]; then
- set $new_static_routes
- while [ $# -gt 1 ]; do
- route -q $rdomain add $1 $2
- shift; shift
- done
- fi
}
add_new_resolv_conf() {
