Article View: comp.dcom.modems.cable
Article #451Re: BIZARRE tcp/ip problem ATTN: Navas/Swit
From: Lawrence Baldwin
Date: Tue, 06 Feb 2001 11:55
Date: Tue, 06 Feb 2001 11:55
58 lines
3344 bytes
3344 bytes
David Ciesnik wrote: > > Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com> wrote: > > > Oh yeah, and David didn't make it very easy on me, guy has cable modem, > > but no phone...man! > > Lawrence, > > Thanks for spending the time and effort helping me get my connection back > up!! Your expert knowledge on packet routing was definitely key in > finding the solution. :) Packet analysis, yes. Packet routing, no. No problem...packets are my life. > I also did a traceroute to my machine from an outside server like Randy > and found there to be a major delay on the hop right before my router. > Last week there WAS a problem with the T1 router that comes into my > neighborhood, but this was supposedly fixed. It appears that this router > is still causing some issues. Could this router be the issue? Since we can send test pings to those devices, it's hard for us to tell. Regardless, the 500ms delay on Hop #19 (or Hop #1 from your prospective) is extreme...it should be <10ms. Unless your cable provider has actually sold you a satellite connection. >But why > would it allow me to throw 512k packets past it, but not 1400k packets??? Every input and output router interface can be assigned an MTU also. Most let them default to 1500 bytes, which is the larget packets most users send anyway. However, someone could have mis-configured it to say: 512. I don't think that is the problem though, since *some* packets still get through as we range sizes from 513 bytes - 900 bytes. I suspect there is a T1 physical problem that is sensitive to packet size. If there are "slips" happening on a T1 at some interval, you can frequently squeeze small packets through (< interval), whereas large packets always fail (e.g. > interval). The next question is are other users attached to this same router experiencing the same problem? Let's do some ping tests to other IP addresses on the same subnet. lb. -- ------------------------- Lawrence Baldwin Protocol Scientist 678-624-0924 http://www.mynetwatchman.com/about.htm - I'm under attack, now what?
Technical Details
Message-ID:
<3A7FE626.21F04D5@mynetwatchman.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mailReferences:
<94Bf6.1733$5s2.61515@wormhole.dimensional.com> <3A7F7266.B06A04CC@mynetwatchman.com> <J7Nf6.1742$5s2.62100@wormhole.dimensional.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1122a6,20d8aef3c030d409 X-Google-Attributes: gid1122a6,public X-Google-Thread: 113850,eb550c41b41f5182 X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2001-02-06 03:55:31 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news1.atl.POSTED!not-for-mail Message-ID: <3A7FE626.21F04D5@mynetwatchman.com> From: Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com> X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.dcom.modems.cable,bellsouth.net.support.adsl Subject: Re: BIZARRE tcp/ip problem ATTN: Navas/Swit References: <94Bf6.1733$5s2.61515@wormhole.dimensional.com> <3A7F7266.B06A04CC@mynetwatchman.com> <J7Nf6.1742$5s2.62100@wormhole.dimensional.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Date: Tue, 06 Feb 2001 06:55:18 -0500 NNTP-Posting-Host: 208.61.191.103 X-Trace: news1.atl 981460519 208.61.191.103 (Tue, 06 Feb 2001 06:55:19 EST) NNTP-Posting-Date: Tue, 06 Feb 2001 06:55:19 EST