[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111122183727.01ab6f04@telperion.jlyo.org>
Date: Tue, 22 Nov 2011 18:37:27 -0600
From: Jesse Young <jlyo@...o.org>
To: David Miller <davem@...emloft.net>
Cc: netdev@...r.kernel.org
Subject: Re: Missing TCP SYN on loopback, retransmits after 1s
On Tue, 22 Nov 2011 19:23:38 -0500 (EST)
David Miller <davem@...emloft.net> wrote:
> From: Jesse Young <jlyo@...o.org>
> Date: Tue, 22 Nov 2011 18:13:20 -0600
>
> > What's also puzzling, is that I see no packet drop reporting in
> > $ ifconfig lo
> > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
> > inet 127.0.0.1 netmask 255.0.0.0
> > inet6 ::1 prefixlen 128 scopeid 0x10<host>
> > loop txqueuelen 0 (Local Loopback)
> > RX packets 276411482 bytes 15822880567 (14.7 GiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 276411482 bytes 15822880567 (14.7 GiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions
>
> The device driver therefore isn't even seeing the packets, they are
> being dropped elsewhere.
>
> Why is this "puzzling"?
>
> There's layers upon layers and thousands of places where packets can
> be dropped between the originating network stack and the actual device
> driver.
Maybe puzzling isn't the best word... just some more relevant
information. Also, this is the loopback interface, there is no device
driver, PHY or DLL layer in question here (just the loopback's mock
driver/PHY/DLL).
I presume that the drop is occuring in between the NET layer, and the sys
call interface, do you agree? Where should I begin looking?
--
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
Powered by blists - more mailing lists