netdev - Re: E1000E/82567LM-3: link reported up too soon

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100920.125447.220082714.davem@davemloft.net>
Date:	Mon, 20 Sep 2010 12:54:47 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	arno@...isbad.org
Cc:	brian.haley@...com, netdev@...r.kernel.org
Subject: Re: E1000E/82567LM-3: link reported up too soon

From: arno@...isbad.org (Arnaud Ebalard)
Date: Mon, 20 Sep 2010 20:57:46 +0200

> On some ethernet devices (at least), link may be reported up (NEWLINK
> received by userspace with flags indicating UP and RUNNING) before the
> interface is really usable. When sending packets as soon as the link is
> available, the first one may be dropped. That's what you see on the
> capture above.

The link being up doesn't mean an address has been assigned to the
interface for the protocol you are using yet.

I think you have to schedule whatever it is you need to make sure it
runs after dhcp successfully complete.
--
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