Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8641 - NetworkManager doesn't call DHCP client on wired network
Attached to Project:
Arch Linux
Opened by Giacomo Rizzo (alt-os) - Thursday, 15 November 2007, 10:02 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 15 November 2007, 12:08 GMT
Opened by Giacomo Rizzo (alt-os) - Thursday, 15 November 2007, 10:02 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 15 November 2007, 12:08 GMT
|
DetailsDescription:
Since a few weeks (can't say exactly when, but it must be 2 or 3 weeks ago), and ONLY on wired network, NetworkManager stopped asking DHCP client for an IP address and beginned fixing it by is own, using 192.168.0.2. I even tryed stopping avahi and dhcdbd, but nothing changed. I tryed in different networks too. When I call dhclient from the shell, it happens that networkmanager disconnect the first time, and I must run dhclient a second time to have the network properly configured. Strangely, everything goes fine when using a wireless connection. Additional info: networkmanager 0.6.5-3 dhcdbd 3.0-1 hal 0.5.10-1 libnl 1.0pre6-1 ethernet module: e1000 Attached files: wireshark dump of a "networkmanager connection". |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Thursday, 15 November 2007, 12:08 GMT
Reason for closing: Not a bug
Thursday, 15 November 2007, 12:08 GMT
Reason for closing: Not a bug
nm-dhcp
Thank you very much :)