Linmodems Mailing list Archives

Google
 
Web archives.linmodems.org

Return-Path: <stodolsk@rcn.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 14333 invoked from network); 7 Mar 2001 13:17:57 -0000
Received: from saturn.er.doe.gov (192.73.213.100)
  by www.linmodems.org with SMTP; 7 Mar 2001 13:17:57 -0000
Received: from rcn.com (66-44-13-102.s864.apx2.lnh.md.dialup.rcn.com [66.44.13.102]) by saturn.er.doe.gov (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA21226; Wed, 7 Mar 2001 08:17:16 -0500
Sender: marv@rcn.com
Message-ID: <3AA634D5.90C4EBBB@rcn.com>
Date: Wed, 07 Mar 2001 08:17:09 -0500
From: Marvin Stodolsky <stodolsk@rcn.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: radoni@crosswinds.net
CC: discuss@linmodems.org, Mark Spieth <mark@digivation.com.au>
Subject: ltmodem, f3 Re:  corrupt pings
References: <20010307080424.8936F4CB9A@member-mx1.crosswinds.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eric

There is a ltmodem-5.78f3 sent out to a sub-group, for testing of newly
implemented support for PCMCIA Lucent modems.  Is that the one you are
using?

Though I don't have a PCMCIA modem, my laptop is under that f3 ltmodem.o
with  kernel-2.4.2 :

Per below, problems are not apparent.  Can you perhaps check the same
driver on a with different hardware to ascertain that its not a problem
through your local routing?

MarvS
=======================
Module                  Size  Used by
ppp_deflate            39584   1  (autoclean)
bsd_comp                4208   0  (autoclean)
ppp_async               5968   1  (autoclean)
ltmodem               361232   1  (autoclean)
isa-pnp                28048   0  (autoclean) [ltmodem]
ppp_generic            12928   3  (autoclean) [ppp_deflate bsd_comp
ppp_async]


koala:/home/marv# ping  www.com
PING www.com (209.132.205.227): 56 data bytes
64 bytes from 209.132.205.227: icmp_seq=0 ttl=244 time=249.3 ms
64 bytes from 209.132.205.227: icmp_seq=1 ttl=244 time=239.8 ms
64 bytes from 209.132.205.227: icmp_seq=2 ttl=244 time=239.9 ms
64 bytes from 209.132.205.227: icmp_seq=3 ttl=244 time=239.9 ms
64 bytes from 209.132.205.227: icmp_seq=4 ttl=244 time=239.9 ms
64 bytes from 209.132.205.227: icmp_seq=5 ttl=244 time=240.0 ms
64 bytes from 209.132.205.227: icmp_seq=6 ttl=244 time=239.9 ms
^[c64 bytes from 209.132.205.227: icmp_seq=7 ttl=244 time=239.9 ms
64 bytes from 209.132.205.227: icmp_seq=8 ttl=244 time=229.9 ms

--- www.com ping statistics ---
10 packets transmitted, 9 packets received, 10% packet loss
round-trip min/avg/max = 229.9/239.8/249.3 ms
koala:/home/marv# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3904  Metric:1
          RX packets:77 errors:0 dropped:0 overruns:0 frame:0
          TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:66.44.13.102  P-t-P:208.59.89.134 
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
========================
> Shattow wrote:
> 
> hi again.  this is a long message.
> 
> okay so i'm testing ltmodem 5.78f3 (don't ask me for a copy) and i still
> get corrupt pings.   my question is....  is there just something about the
> closed source part of ltmodem that is causing the corrupt data, or is there
> someone who explain to me ideas on why this is happening?  old episodes of
> "wonder woman" are starting to melt into reruns of "sanford & son"....
> help?    ;o]
> 
> -eric shattow
> 
> (below is the relevent ping data.   linux kernel 2.4.3-pre2, devfs, isapnp
> built as module, serial built as module)
> 
> erisha:~$ ping www.com
> PING www.com (209.132.205.227): 56 octets data
> 64 octets from 209.132.205.227: icmp_seq=0 ttl=242 time=269.7 ms
> 64 octets from 209.132.205.227: icmp_seq=1 ttl=242 time=270.1 ms
> 64 octets from 209.132.205.227: icmp_seq=2 ttl=242 time=8840.0 ms
> wrong data byte #0 should be 0x94 but was 0x8c8c 93 a5 3a cd cd 7 0
>         8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 
> erisha:~$ ping www.networksolutions.com
> ping: unknown host www.networksolutions.com
> 
> ######   looks like my connection was dropped yet again ####
> 
> i can only manage 10 or 20 second connections.  so....   any takers?
> 
> -eric

Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003