netdev - Re: data received but not detected

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: <20080618062857.GA3598@2ka.mipt.ru>
Date:	Wed, 18 Jun 2008 10:28:58 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Travis Stratman <tstratman@...cinc.com>
Cc:	Ben Greear <greearb@...delatech.com>, netdev@...r.kernel.org
Subject: Re: data received but not detected

Hi.

On Tue, Jun 17, 2008 at 05:58:26PM -0500, Travis Stratman (tstratman@...cinc.com) wrote:
> I understand that there is no guarantee of anything with UDP, but it
> seems to me that if there is a packet in the buffer (it shows up after
> another packet comes in behind it) the system should know about it,
> right?

Did you run wireshark on receiver or sender?
Check MIB stats if packet was dropped because of low mem or incorrect
checksumm or some other problematic fields in UDP header. Sending part
can see it perfectly correct, which will not be the issue on the
receiver. If packet was delivered to receiving host, udp input path is
rather simple so there are no places which can race with something and
thus lost the packet.

-- 
	Evgeniy Polyakov
--
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