From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bug or feature ? --- ip/ping -6
Date: Wed, 30 Dec 2015 15:05:33 +0000 [thread overview]
Message-ID: <18123F6C-5742-4E3D-906F-A7D4D8C40412@quintile.net> (raw)
In-Reply-To: <2F96B09F-7524-473A-B883-9A7B7DD09978@ar.aichi-u.ac.jp>
If I where redesigning ping I wouldn't repeat any info that is common on each line - I.e. ip addresses or the column titles: rtt, ave etc.
consider plan9's ps(1) which has no column titles. they are described in the man page and are obvious from the context once you have read the man page once.
Having said this, I understand that tradition is also a strong guiding principal.
-Steve
> On 30 Dec 2015, at 12:48, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>
> hello,
>
> is the following output of ping reasonable enough?
>
>
> io% 6.ping -an3 hebe
> sending 3 64 byte messages 1000 ms apart to icmp!192.168.0.6!1
> 192.168.0.5 -> 192.168.0.6
> 0: 192.168.0.6 -> 192.168.0.5 rtt 88 µs, avg rtt 88 µs, ttl = 255
> 1: 192.168.0.6 -> 192.168.0.5 rtt 83 µs, avg rtt 85 µs, ttl = 255
> 2: 192.168.0.6 -> 192.168.0.5 rtt 80 µs, avg rtt 83 µs, ttl = 255
>
> io% 6.ping -an3 192.168.0.6
> sending 3 64 byte messages 1000 ms apart to icmp!192.168.0.6!1
> 192.168.0.5 -> 192.168.0.6
> 0: 192.168.0.6 -> 192.168.0.5 rtt 107 µs, avg rtt 107 µs, ttl = 255
> 1: 192.168.0.6 -> 192.168.0.5 rtt 84 µs, avg rtt 95 µs, ttl = 255
> 2: 192.168.0.6 -> 192.168.0.5 rtt 95 µs, avg rtt 95 µs, ttl = 255
>
> io% 6.ping -an3 2402:6b00:22cd:bf80::6
> sending 3 64 byte messages 1000 ms apart to icmpv6!2402:6b00:22cd:bf80::6!1
> 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6
> 0: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 103 µs, avg rtt 103 µs, ttl = 255
> 1: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 96 µs, avg rtt 99 µs, ttl = 255
> 2: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 83 µs, avg rtt 94 µs, ttl = 255
>
> io% 6.ping -6an3 hebe
> sending 3 64 byte messages 1000 ms apart to icmpv6!2402:6b00:22cd:bf80::6!1
> 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6
> 0: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 101 µs, avg rtt 101 µs, ttl = 255
> 1: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 82 µs, avg rtt 91 µs, ttl = 255
> 2: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 89 µs, avg rtt 90 µs, ttl = 255
>
> io% 6.ping -6an3 192.168.0.6
> sending 3 64 byte messages 1000 ms apart to icmp!192.168.0.6!1
> 192.168.0.5 -> 192.168.0.6
> 0: 192.168.0.6 -> 192.168.0.5 rtt 90 µs, avg rtt 90 µs, ttl = 255
> 1: 192.168.0.6 -> 192.168.0.5 rtt 94 µs, avg rtt 92 µs, ttl = 255
> 2: 192.168.0.6 -> 192.168.0.5 rtt 90 µs, avg rtt 91 µs, ttl = 255
>
> io% 6.ping -6an3 2402:6b00:22cd:bf80::6
> sending 3 64 byte messages 1000 ms apart to icmpv6!2402:6b00:22cd:bf80::6!1
> 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6
> 0: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 101 µs, avg rtt 101 µs, ttl = 255
> 1: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 272 µs, avg rtt 186 µs, ttl = 255
> 2: 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5 rtt 102 µs, avg rtt 158 µs, ttl = 255
>
> code is simplified.
>
> io% ls -l
> --rw-rw-r-- M 327 arisawa arisawa 9942 Dec 30 21:27 ping.c
> --rw-rw-r-- M 327 arisawa arisawa 10943 Dec 28 15:59 ping.c.orig
> io%
>
> Kenji Arisawa
>
>
>
>> 2015/12/28 18:04、arisawa <arisawa@ar.aichi-u.ac.jp> のメール：
>>
>> hello 9fans,
>>
>> I have once posted the message below to 9front mailing list.
>> however looking the origin of the problem, now I think better place is 9fans.
>>
>> == message posted to 9front mailing list ==
>>
>> I am feeling weird that ip/ping -6 does not ping to ipv6 address with /lib/ndb/local.
>>
>> # sys=io
>> # ip=192.168.0.5
>> # ip=2402:6b00:22cd:bf80::5
>> #
>> hebe% ip/ping -6a io
>> sending 32 64 byte messages 1000 ms apart to icmpv6!io!1
>> 2402:6b00:22cd:bf80::6 -> 192.168.0.5
>> 0: 192.168.0.5 -> 192.168.0.6 rtt 104 µs, avg rtt 104 µs, ttl = 255
>> 1: 192.168.0.5 -> 192.168.0.6 rtt 85 µs, avg rtt 94 µs, ttl = 255
>> 2: 192.168.0.5 -> 192.168.0.6 rtt 85 µs, avg rtt 91 µs, ttl = 255
>> 3: 192.168.0.5 -> 192.168.0.6 rtt 85 µs, avg rtt 89 µs, ttl = 255
>>
>> this weirdness comes from the order of ip attributes.
>>
>> # sys=io
>> # ip=2402:6b00:22cd:bf80::5
>> # ip=192.168.0.5
>> #
>> hebe% ip/ping -6a io
>> sending 32 64 byte messages 1000 ms apart to icmpv6!io!1
>> 2402:6b00:22cd:bf80::6 -> 2402:6b00:22cd:bf80::5
>> 0: 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6 rtt 102 µs, avg rtt 102 µs, ttl = 255
>> 1: 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6 rtt 88 µs, avg rtt 95 µs, ttl = 255
>> 2: 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6 rtt 84 µs, avg rtt 91 µs, ttl = 255
>> 3: 2402:6b00:22cd:bf80::5 -> 2402:6b00:22cd:bf80::6 rtt 104 µs, avg rtt 94 µs, ttl = 255
>>
>> is this a feature or a bug?
>>
>> Kenji Arisawa
>
next prev parent reply other threads:[~2015-12-30 15:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 9:04 arisawa
2015-12-29 0:10 ` Anthony Martin
2015-12-30 12:48 ` arisawa
2015-12-30 13:21 ` Charles Forsyth
2015-12-30 15:05 ` Steve Simon [this message]
2015-12-30 15:26 ` Kurt H Maier
2015-12-30 19:05 ` Steve Simon
2015-12-30 22:43 ` Kenny Lasse Hoff Levinsen
2015-12-30 23:36 ` Steve Simon
2015-12-31 0:16 ` Bakul Shah
2015-12-31 1:36 ` arisawa
2015-12-31 3:44 ` Dave Eckhardt
2016-01-02 1:12 ` erik quanstrom
2016-01-02 1:54 ` erik quanstrom
2016-01-03 19:58 ` hiro
2016-01-03 20:04 ` erik quanstrom
2016-01-03 20:31 ` erik quanstrom
2016-01-03 21:40 ` hiro
2016-01-03 21:43 ` hiro
2016-01-03 21:47 ` erik quanstrom
2016-01-04 1:31 ` erik quanstrom
2016-01-04 10:51 ` Anthony Martin
2016-01-04 13:04 ` erik quanstrom
2016-01-04 13:58 ` erik quanstrom
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=18123F6C-5742-4E3D-906F-A7D4D8C40412@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).