From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: "Manfred Spraul" <manfred@colorfullife.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: How to debug very strange packet delivery problem?
Date: Fri, 4 Jan 2002 22:21:35 -0700 [thread overview]
Message-ID: <00cc01c195a8$d7e4b960$6caaa8c0@kevin> (raw)
In-Reply-To: <000701c19575$fed79ca0$010411ac@local>
Hadn't gone that far yet, no. Luckily at this time the machines are actually
located in the same office, so this shouldn't be too hard to do. Once the
problem machine is relocated to 30+ miles away, it would be a bit more
difficult :-)
----- Original Message -----
From: "Manfred Spraul" <manfred@colorfullife.com>
To: ""Kevin P. Fleming"" <kevin@labsysgrp.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, January 04, 2002 4:17 PM
Subject: Re: How to debug very strange packet delivery problem?
> > - watched the packets leave from the source machine with tcpdump on
> > the outbound interface, and the packets arrive intact at the problem
> > machine with tcpdump on the ppp interface
>
> Have you dumped the complete packet on both ends, and checked that it
> arrives really unchanged? (except the IP checksum and the ttl).
> IIRC the option should be -x -s 1500
>
> Perhaps some traffic shaper/firewall corrupts incomming SYN packets?
>
> --
> Manfred
>
>
>
>
next prev parent reply other threads:[~2002-01-05 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 23:17 How to debug very strange packet delivery problem? Manfred Spraul
2002-01-05 5:21 ` Kevin P. Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 4:38 Kevin P. Fleming
2002-01-04 23:00 ` bert hubert
2002-01-05 5:20 ` Kevin P. Fleming
2002-01-05 15:20 ` Mika Liljeberg
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='00cc01c195a8$d7e4b960$6caaa8c0@kevin' \
--to=kevin@labsysgrp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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