Bug 156351 - NetworkManager prevents dhclient from running.
NetworkManager prevents dhclient from running.
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-29 03:35 EDT by David Woodhouse
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 0.6.x
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-31 22:48:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Woodhouse 2005-04-29 03:35:21 EDT
While NetworkManager is running, dhclient on other interfaces fails:

       Listening on LPF/bnep0/00:0d:93:05:4a:3e
       Sending on   LPF/bnep0/00:0d:93:05:4a:3e
       Can't bind to dhcp address: Address already in use
       Please make sure there is no other dhcp server
       running and that there's no entry for dhcp or
       bootp in /etc/inetd.conf.   

NetworkManager should bind to the specific device which it wants to listen on,
in the same way that dhclient presumably does.
Comment 1 David Woodhouse 2005-04-29 03:39:51 EDT
(Alternatively, if NetworkManager were to manage the Bluetooth networking for me
so I don't have to bring it up manually with 'ifup bnep0', that would be
acceptable too :)
Comment 2 Dan Williams 2005-04-29 07:34:52 EDT
Hmm, it should be binding to a specific device, it should only bind to the
device that its done DHCP on.  Other devices have no open sockets on them for
DHCP, or should not...  probably a bug.
Comment 3 Dan Williams 2005-04-29 07:35:27 EDT
Note that right now I'm reworking the connection code to use dhcdbd+dhclient
anyway, so the internal DHCP client will go away quite soon (but not for FC4).
Comment 4 David Woodhouse 2005-06-30 05:26:46 EDT
Still happening in FC4 release. It's easy to trigger.... just let NetworkManager
run and then try to bring up some other interface... like 'ifup bnep0'...


Jun 30 10:21:17 shinybook kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Jun 30 10:21:17 shinybook kernel: Bluetooth: BNEP filters: protocol multicast
Jun 30 10:21:17 shinybook pand[3047]: Bluetooth PAN daemon version 2.15
Jun 30 10:21:17 shinybook pand[3047]: Inquiring
Jun 30 10:21:30 shinybook pand[3047]: Searching for NAP on 00:0A:3A:62:BD:F2
Jun 30 10:21:36 shinybook hcid[1937]: pin_code_request (sba=00:0D:93:05:4A:3E,
dba=00:0A:3A:62:BD:F2)
Jun 30 10:21:52 shinybook hcid[1937]: link_key_notify (sba=00:0D:93:05:4A:3E)
Jun 30 10:21:52 shinybook hcid[1937]: Saving link key 00:0D:93:05:4A:3E
00:0A:3A:62:BD:F2
Jun 30 10:21:53 shinybook pand[3047]: Connecting to 00:0A:3A:62:BD:F2
Jun 30 10:21:53 shinybook pand[3047]: bnep0 connected
Jun 30 10:21:55 shinybook dhclient: Can't bind to dhcp address: Address already
in use
Jun 30 10:21:55 shinybook dhclient: Please make sure there is no other dhcp server
Jun 30 10:21:55 shinybook dhclient: running and that there's no entry for dhcp or
Jun 30 10:21:55 shinybook dhclient: bootp in /etc/inetd.conf.   Also make sure you
Jun 30 10:21:55 shinybook dhclient: are not running HP JetAdmin software, which
Jun 30 10:21:55 shinybook dhclient: includes a bootp server.
Jun 30 10:21:55 shinybook dhclient: exiting.

Comment 5 David Woodhouse 2005-10-09 16:25:36 EDT
This is still causing dhcp to fail on FC4.
Comment 6 Dan Williams 2007-10-31 22:48:18 EDT
way old, fixed in FC5 I'm pretty sure (with dhcdbd)

Note You need to log in before you can comment on or make changes to this bug.