public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: <gabucino@mplayerhq.hu>
To: linux-8086@vger.kernel.org
Subject: strange ping results
Date: Thu, 26 Sep 2002 16:59:31 +0200	[thread overview]
Message-ID: <20020926145931.GA383@woodstock> (raw)

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

I'm using EDE stable (0.1.0) on noname 286/16, connected to Linux/LFS (2.4.19) via SLIP 9600bps.
I get strange ping outputs :)
Doing a test:

64 octets from 10.1.3.2: icmp_seq=73 ttl=63 time=194.0 ms
64 octets from 10.1.3.2: icmp_seq=74 ttl=63 time=194.0 ms
64 octets from 10.1.189.2: icmp_seq=75 ttl=63 time=194.0 ms

Meanwhile checked with tcpdump:
16:52:27.921937 10.1.0.2 > 10.1.3.2: icmp: echo request (DF)
16:52:28.115240 10.1.3.2 > 10.1.0.2: icmp: echo reply
16:52:28.921963 10.1.0.2 > 10.1.3.2: icmp: echo request (DF)
16:52:29.115240 10.1.3.2 > 10.1.0.2: icmp: echo reply
16:52:29.922014 10.1.0.2 > 10.1.3.2: icmp: echo request (DF)
16:52:30.115239 10.1.189.2 > 10.1.0.2: icmp: echo reply     

Hm :) What could be the cause?
It could be buggy I/O card (16bit), but:

sl0       Link encap:Serial Line IP  
          inet addr:10.1.3.1  P-t-P:10.1.3.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:296  Metric:1
          RX packets:968 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 
          RX bytes:81312 (79.4 Kb)  TX bytes:86340 (84.3 Kb)

No errors.

BTW: what's the usage of urlget? Tried ftp://x.x.x.x but it doesn't generate
any traffic.

-- 
Gabucino

/ Worshipping Niedermayer 4ever /
"Do you always look at it encoded?" (C) D. R. F.
"minden lehet. ez nem." (c) A'rpi

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

                 reply	other threads:[~2002-09-26 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020926145931.GA383@woodstock \
    --to=gabucino@mplayerhq.hu \
    --cc=linux-8086@vger.kernel.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