From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, nm127@freemail.hu
Subject: Re: [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is dropped after ~40 seconds
Date: Wed, 16 Dec 2009 15:47:13 -0800 [thread overview]
Message-ID: <20091216154713.f082e7cf.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14794-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
A 2.6.31 -> 2.6.32 regression.
On Sun, 13 Dec 2009 08:59:48 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14794
>
> Summary: IP address assigned by DHCP is dropped after ~40
> seconds
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.32
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: nm127@freemail.hu
> Regression: Yes
>
>
> Created an attachment (id=24165)
> --> (http://bugzilla.kernel.org/attachment.cgi?id=24165)
> Wireshark log while acquiring IP address
>
> The IP address which was assigned by DHCP is dropped and the address
> 169.254.123.251 is set. This happens on Clevo D4J model D410J with 2.6.32, but
> works correctly with 2.6.31.
>
> Steps to reproduce:
> 1. Boot the system
> 2. In an xterm window execute the following command to see the actual IP
> address settings:
> while true; do clear; date; /sbin/ifconfig; sleep 1; done
> 3. Unplug the network cable for some seconds: the IP address should be gone
> 4. Plug the network cable.
> 5. After about 10 seconds the IP address 192.168.1.64 assigned by DHCP is
> visible
> 6. After about 50 seconds (counting from the plug of the network cable) no IP
> address is assigned
> 7. After about 65 seconds (counting from the plug of the network cable) the IP
> address 169.254.123.251 is assigned. This IP address will not work on this
> network.
>
> I run Wireshark during the whole process, see the attached log file.
> Packet 25..28: DHCP address is fetched.
> Packet 63: DHCP release: this should not happen
>
next parent reply other threads:[~2009-12-16 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14794-10286@http.bugzilla.kernel.org/>
2009-12-16 23:47 ` Andrew Morton [this message]
2009-12-17 20:53 ` [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is dropped after ~40 seconds Németh Márton
2009-12-17 21:20 ` Peter Zijlstra
2009-12-17 21:24 ` Andrew Morton
2009-12-17 21:44 ` Jarek Poplawski
2009-12-18 7:56 ` Németh Márton
2009-12-18 8:16 ` Roland Dreier
2009-12-18 11:41 ` Jarek Poplawski
2009-12-18 16:17 ` Németh Márton
2009-12-18 16:57 ` Németh Márton
2009-12-18 17:05 ` Németh Márton
2009-12-18 8:22 ` Roland Dreier
2009-12-18 16:49 ` Németh Márton
2009-12-18 20:09 ` Jarek Poplawski
2009-12-19 10:26 ` Németh Márton
2009-12-19 13:48 ` Jarek Poplawski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091216154713.f082e7cf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm127@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).