From: Nick Drage <nickd@metastasis.org.uk>
To: netfilter@lists.netfilter.org
Subject: Re: IP port over 65535 ?!
Date: Wed, 31 May 2006 08:25:00 +0100 [thread overview]
Message-ID: <20060531072500.GS19917@metastasis.org.uk> (raw)
In-Reply-To: <013701c66990$0e9cc500$5e00800a@printserver>
On Wed, Apr 26, 2006 at 05:18:06PM -0700, Jesse Gordon wrote:
> I sometimes see a port number like this in Tcpdump:
>
> 10.0.0.76.2049 > 64.x.x.5.796094310: reply ERR 394
>
> 64.7.197.5.791752241 > 10.0.0.76.2049: 1460 proc-170106..
>
> Ever seen anything like this?
>
> I'm a small natting ISP -- all of the above looks good except that port
> number of 791752241..
That looks like some kind of issue with tcpdump or the underlying
library. Have you looked at the same traffic with tethereal/ethereal?
--
How can I miss you if you won't go away?
prev parent reply other threads:[~2006-05-31 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 0:18 IP port over 65535 ?! Jesse Gordon
2006-05-31 7:25 ` Nick Drage [this message]
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=20060531072500.GS19917@metastasis.org.uk \
--to=nickd@metastasis.org.uk \
--cc=netfilter@lists.netfilter.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