From: Ricardo Galli <gallir@uib.es>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: 2.6.0: Bad udp checksum in loopback interface
Date: Fri, 15 Aug 2003 13:11:48 +0200 [thread overview]
Message-ID: <200308151311.48831.gallir@uib.es> (raw)
tcpdump -v shows bad udp checksum in the loopback interface. But I'm not sure
if the packets is discarded or the error is ignored.
ponti:~# tcpdump -i lo -n -v
ponti:~# dig @192.168.0.3 gallimedina.net
13:02:12.360728 192.168.0.3.32827 > 192.168.0.3.53: [bad udp cksum 5e6d!]
35220+ A? gallimedina.net. (33) (DF) [ttl 0] (id 0, len 61)
13:02:12.364470 192.168.0.3.53 > 192.168.0.3.32827: 35220* 1/1/1
gallimedina.net. A 192.168.0.10 (85) (DF) [ttl 0] (id 12492, len 113)
ponti:~# dig @127.0.0.1 gallimedina.net
13:03:53.299883 127.0.0.1.32827 > 127.0.0.1.53: [bad udp cksum 167d!] 32901+
A? gallimedina.net. (33) (DF) [ttl 0] (id 0, len 61)
13:03:53.303448 127.0.0.1.53 > 127.0.0.1.32827: 32901* 1/1/1 gallimedina.net.
A 192.168.0.10 (85) (DF) [ttl 0] (id 7725, len 113)
This machine has a bridge, but I also tried in another one with netcat (nc -l
-u localhost -p 2000 and nc -u localhost 2000)
antoli:~# tcpdump -i lo -n -v
tcpdump: listening on lo
13:09:04.125385 127.0.0.1.32890 > 127.0.0.1.2000: [bad udp cksum 5a0!] udp 14
(DF) [ttl 0] (id 32006, len 42)
13:09:12.472940 127.0.0.1.2000 > 127.0.0.1.32890: [bad udp cksum 837!] udp 7
(DF) [ttl 0] (id 34086, len 35)
I saw the short message does arrive to the listening netcat, but tcpdump still
gives the bad udp error message.
Regards,
--
ricardo galli GPG id C8114D34
http://mnm.uib.es/~gallir/
next reply other threads:[~2003-08-15 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 11:11 Ricardo Galli [this message]
2003-08-15 11:49 ` 2.6.0: Bad udp checksum in loopback interface (me too!) Catalin BOIE
2003-08-15 16:08 ` 2.6.0: Bad udp checksum in loopback interface Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308151311.48831.gallir@uib.es \
--to=gallir@uib.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®