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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 13 Nov 2016 20:51:46 +0100
From:   Mason <>
To:     Andrew Lunn <>
Cc:     netdev <>,
        Florian Fainelli <>,
        Mans Rullgard <>,
        Sergei Shtylyov <>,
        Tom Lendacky <>,
        Zach Brown <>,
        Shaohui Xie <>,
        Tim Beale <>,
        Brian Hill <>,
        Vince Bridgers <>,
        Balakumaran Kannan <>,
        "David S. Miller" <>,
        Sebastian Frias <>,
        Kirill Kapranov <>
Subject: Re: Debugging Ethernet issues

On 13/11/2016 04:09, Andrew Lunn wrote:

> Mason wrote:
>> When connected to a Gigabit switch
>> 3.4 negotiates a LAN DHCP setup instantly
>> 4.7 requires over 5 seconds to do so
> When you run tcpdump on the DHCP server, are you noticing the first
> request is missing?
> What can happen is the dhclient gets started immediately and sends out
> its first request before auto-negotiation has finished. So this first packet
> gets lost. The retransmit after a few seconds is then successful.

I will run tcpdump on the server as I run udhcpc on the client
for Linux 3.4 vs 4.7

Do you know what would make auto-negotiation fail at 100 Mbps
on 4.7? (whereas it succeeds on 3.4)

(Thinking out loud) If the problem were in auto-negotiation,
then if should work if I hard-code speed and duplex using
ethtool, right? (IIRC, hard-coding doesn't help.)


Powered by blists - more mailing lists