From: Frank van Maarseveen <fvm@tasking.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.4.5-pre1: Bogus ARP packets containing NFS file data? (2)
Date: Tue, 15 May 2001 18:47:24 +0200 [thread overview]
Message-ID: <20010515184724.A1754@espoo.tasking.nl> (raw)
In-Reply-To: <20010515175212.A31058@espoo.tasking.nl>
In-Reply-To: <20010515175212.A31058@espoo.tasking.nl>; from fvm on Tue, May 15, 2001 at 05:52:12PM +0200
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Got the image of 3 interesting packets by letting a modified tcpdump dump
the entire packet buffer in arp_print().
Original tcpdump output:
16:23:17.108993 P 0:60:97:ba:b4:f5 0:0:0:0:0:1 arp 1514: arp-#8192 for proto #1500 (138) hardware #17664 (36)
16:23:17.809024 P 0:60:97:ba:b4:f5 0:0:0:0:0:1 arp 1514: arp-#8192 for proto #1500 (139) hardware #17664 (36)
16:23:17.810256 P 0:60:97:ba:b4:f5 0:0:0:0:0:1 arp 1514: arp-#8377 for proto #1500 (139) hardware #17664 (36)
strings 1.bin:
espoo
b0VIM 5.7
espoo
~fvm/ctri/c_flow.c
3210#"!
strings 2.bin:
espoo
b0VIM 5.7
espoo
~fvm/ctri/c_flow.c
3210#"!
strings 3.bin:
Corresponding packet data attached (note: not suitable for tcpdump -r anymore).
--
Frank
[-- Attachment #2: 1.bin --]
[-- Type: application/octet-stream, Size: 1500 bytes --]
[-- Attachment #3: 2.bin --]
[-- Type: application/octet-stream, Size: 1500 bytes --]
[-- Attachment #4: 3.bin --]
[-- Type: application/octet-stream, Size: 1500 bytes --]
next prev parent reply other threads:[~2001-05-15 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 15:52 2.4.5-pre1: Bogus ARP packets containing NFS file data? Frank van Maarseveen
2001-05-15 16:47 ` Frank van Maarseveen [this message]
2001-05-15 17:06 ` 2.4.5-pre1: Bogus ARP packets containing NFS file data? (3) Frank van Maarseveen
2001-05-16 13:21 ` 2.4.5-pre2: Bogus ARP packets containing NFS file data? Frank van Maarseveen
2001-05-18 19:22 ` 2.4.x: Bogus ARP packets containing NFS file data Frank van Maarseveen
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=20010515184724.A1754@espoo.tasking.nl \
--to=fvm@tasking.nl \
--cc=frank_van_maarseveen@tasking.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).