Package: ifupdown Version: 0.6.8+nmu1 Severity: normal
Situation: the client is configured *not* to use network-manager, but instead eth0 is added to the "auto" line in /etc/network/interfaces. The dhcp-server has configured serveral options including: * option 3 (Router) * option 121 (Classless Static Routes) According to RFC 3442, clients that receive and support option 121 MUST ignore option 3 if present. Problem: the routes from *both* option 3 and option 121 are added to the kernel routing table, the client ends up with 2 default gateways. Additional info: * Tested with dhcp server on Windows 2008 R2 * Windows clients are found to contain the same bug. * Ubuntu 10.04 is found to contain the same bug. This bug probably is present in multiple versions of Debian and derived distributions. * When using network-manager, option 3 is used and option 121 is not (correct behaviour according to RFC 3442). * Using dhcpcd instead of dhclient (dhcp3-client), option 121 is used and option 3 is ignored (like it should). -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii net-tools 1.60-22 The NET-3 networking toolkit ifupdown recommends no packages. Versions of packages ifupdown suggests: ii dhcp3-client 3.1.1-6+lenny4 DHCP client ii iproute 20080725-2 networking and traffic control too pn ppp <none> (no description available) -- no debconf information
