From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: Can anyone tell wat's going on here?
Date: Wed, 11 May 2005 13:31:03 -0500 [thread overview]
Message-ID: <42824F67.6010701@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0505111249010.3025@palangana>
> palangana:~# tethereal -i ppp0 '(host xxx.xxx.xxx.xxx) or (port 22)' Capturing on ppp0
> 0.000000 201.252.166.212 -> xxx.xxx.xxx.xxx SSH Encrypted request packet len=48
> 0.159113 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=48
> 0.159304 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 4874 > ssh [ACK] Seq=48 Ack=48 Win=2540 Len=0 TSV=59055726 TSER=229209706
> 0.210101 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=144
> 0.210259 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 4874 > ssh [ACK] Seq=48 Ack=192 Win=2812 Len=0 TSV=59055777 TSER=229209709
> 0.383142 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=1440
> 0.383456 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 4874 > ssh [ACK] Seq=48 Ack=1632 Win=3532 Len=0 TSV=59055950 TSER=229209716
> 0.463144 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=1440
> 0.463349 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 4874 > ssh [ACK] Seq=48 Ack=3072 Win=4252 Len=0 TSV=59056030 TSER=229209716
> 0.463154 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=16
> 0.463481 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 4874 > ssh [ACK] Seq=48 Ack=3088 Win=4252 Len=0 TSV=59056030 TSER=229209717
>
> but from a client this happens:
>
> palangana:~# tethereal -i ppp0 '(host xxx.xxx.xxx.xxx ) or (port 22)' Capturing on ppp0
> 0.000000 201.252.166.212 -> xxx.xxx.xxx.xxx SSH Encrypted request packet len=48
> 0.074706 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=48
> 0.104737 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=144
> 0.105109 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 1356 > ssh [ACK] Seq=48 Ack=192 Win=64399 Len=0
> 0.118746 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH Encrypted response packet len=144
> 0.226971 201.252.166.212 -> xxx.xxx.xxx.xxx TCP 1356 > ssh [ACK] Seq=48 Ack=336 Win=64255 Len=0
> 0.367701 xxx.xxx.xxx.xxx -> 201.252.166.212 SSH [TCP Previous segment lost] Encrypted response packet len=1292
> 0.368144 201.252.166.212 -> xxx.xxx.xxx.xxx TCP [TCP Dup ACK 6#1] 1356 > ssh [ACK] Seq=48 Ack=336 Win=64255 Len=0 SLE=1796 SRE=3088
One thing jumps out to me, namely your TCP window size is different when you are working from your client (NATed) system. I'm not familiar with dealing with MTU issues, but someone else on this list (Jason do you have any comments?) might be able to help you more than I can.
The other thing that comes to mind is that you might be having problem with your USB modem driver. I personally try to avoid USB (for many different reasons) and thus can not help you with that either. Sorry. :(
Grant. . . .
prev parent reply other threads:[~2005-05-11 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 15:49 Can anyone tell wat's going on here? Sergio Penkale
2005-05-11 16:03 ` Steven M Campbell
2005-05-11 18:27 ` Sergio Penkale
2005-05-11 18:30 ` Jason Opperisano
2005-05-11 23:47 ` Sergio Penkale
2005-05-11 18:31 ` Taylor, Grant [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=42824F67.6010701@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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