Package: dhcp3-client
Version: 3.0.4-10
Followup-For: Bug #384271
> Honestly, I don't consider this a bug. Your networking configuration is
> invalid.
This maybe so (I'm not a dhcp guru) so I wouldn't immediately know.
But I've seen this kind of configuration with several maior ISPs in
the Netherlands. Also windows clients do not have a problem with it
so this behavior isn't going away soon.
Also you could argue (I haven't looked at the specs), that the fact
the dhcp-server sends 'router=a.b.c.d', means you can assume you can
reach the router on the connection you have with the provider.
I attached a one line patch for the dhcp-client script that just assumes
that; It adds a route specifically for the router. For people that have
their router on the local network this won't be a problem, for the people
that are bitten by this bug it means the get a working dhcp-client.
grts Tim
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (900, 'testing'), (20, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18.3
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to nl_NL.utf8)
Versions of packages dhcp3-client depends on:
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii debianutils 2.17 Miscellaneous utilities specific t
ii dhcp3-common 3.0.4-10 Common files used by all the dhcp3
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
dhcp3-client recommends no packages.
-- debconf information excluded
--- /sbin/dhclient-script 2006-10-18 07:14:58.000000000 +0200
+++ dhclient-script 2006-11-29 21:00:29.000000000 +0100
@@ -162,6 +162,7 @@
$new_broadcast_arg $mtu_arg
for router in $new_routers; do
+ route add -host $router dev $interface
route add default dev $interface gw $router $metric_arg
done
fi
