[Bug 616809] Re: ifupdown: dhcp behaviour does not comply with RFC 3442

[Bug Watch Updater]

** Changed in: isc-dhcp (Debian)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/616809

Title:
  ifupdown: dhcp behaviour does not comply with RFC 3442

Status in “isc-dhcp” package in Ubuntu:
  Triaged
Status in “isc-dhcp” package in Debian:
  Fix Released

Bug description:
  Binary package hint: ifupdown

  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 several 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 121 and option 3 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.
  * Debian GNU/Linux 5.0.5 (Lenny) is found to contain the same bug. This bug is probably 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:
  Ubuntu 10.04.1 LTS
  Kernel: Linux 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 06:07:29 UTC 2010 i686 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/616809/+subscriptions