netdev - Re: [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is dropped after ~40 seconds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091216154713.f082e7cf.akpm@linux-foundation.org>
Date:	Wed, 16 Dec 2009 15:47:13 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	netdev@...r.kernel.org
Cc:	bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, nm127@...email.hu
Subject: Re: [Bugme-new] [Bug 14794] New: IP address assigned by DHCP is
 dropped after ~40 seconds


(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@...zilla.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@...ux-foundation.org
>         ReportedBy: nm127@...email.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
> 


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html