dhclient3 not recognize -4 option sent by network manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: dhcp3-client
This is about interaction of nentowrk-manager and dhclient3 in current maverick.
My wifi AP does not support IPv6, so the nm is trying to instruct dhclient not to use it.
And apparently fails.
Described in: http://
My current syslog is:
Sep 8 22:50:54 note381 kernel: [ 154.330060] wlan0: no IPv6 routers present
Sep 8 22:51:27 note381 kernel: [ 187.330684] lo: Disabled Privacy Extensions
Sep 8 22:54:55 note381 dhclient: Internet Systems Consortium DHCP Client V3.1.3
Sep 8 22:54:55 note381 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Sep 8 22:54:55 note381 dhclient: All rights reserved.
Sep 8 22:54:55 note381 dhclient: For info, please visit https:/
Sep 8 22:54:55 note381 dhclient: Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server]
Sep 8 22:54:55 note381 dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
Sep 8 22:54:55 note381 dhclient: [-sf script-file] [interface]
affects: | dhcp3 (Ubuntu) → network-manager (Ubuntu) |
Thanks for reporting this bug and helping to make ubuntu better.
I believe this should be marked as a bug against network-manager rather
than dhcp3-client. There is a patch in network-manager which detects
the dhcp client at *compile* time and removes the -4 option, so clearly they
are aware of the issue. The question then is whether and how to detect it
at package installation or perhaps even daemon startup or runtime.