Ubuntu
network-manager package

dhclient doesn't get any dhcpack

Bug #415799 reported by V Sauta
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Fix Released
Undecided
Unassigned
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

(Pardon my English)
dhclient doesn't get any dhcpack, but it did est. 2 weeks ago.
DHCP doesn't work properly in NetworkManager while connecting to both wireless and ethernet networks.
Even when calling "dhclient eth0", it writes "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval XX", but doesn't receive any reply.
Nothing had changed in my router. But dhclient have given up working properly.

ProblemType: Bug
Architecture: amd64
Date: Wed Aug 19 11:47:32 2009
DistroRelease: Ubuntu 9.10
Package: dhcp3-client 3.1.2-1ubuntu5
ProcEnviron:
 LANGUAGE=ru_RU.UTF-8
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SourcePackage: dhcp3
Uname: Linux 2.6.31-5-generic x86_64

Revision history for this message
V Sauta (tsukushima) wrote :
Chuck Short (zulcss)
affects: dhcp3 (Ubuntu) → network-manager (Ubuntu)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

If it doesn't work with n-m or dhclient itself, it looks a little more like a possible issue with dhclient, rather than network-manager. Marking invalid for n-m, incomplete for dhcp3...

I notice that your bug report states using dhcp3-client 3.1.2-1ubuntu5, but version 3.1.2-1ubuntu7 is now available in the repositories. Could you please re-run your test and try to get a DHCP address from both NetworkManager and the 'dhclient eth0' command and report back on your results? Thanks.

Changed in dhcp3 (Ubuntu):
status: New → Incomplete
Changed in network-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Chuck Short (zulcss) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in dhcp3 (Ubuntu):
status: Incomplete → Invalid
V Sauta (tsukushima)
Changed in dhcp3 (Ubuntu):
status: Invalid → Fix Released
Changed in network-manager (Ubuntu):
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.