From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] bug or feature ? --- ip/ping -6
Date: Mon, 4 Jan 2016 05:04:42 -0800 [thread overview]
Message-ID: <f2dfab3cd6a05732cae046105f2e75c2@mule> (raw)
In-Reply-To: <20160104105139.GA26700@dinah>
> erik quanstrom <quanstro@quanstro.net> once said:
> > unfortunately, the simlification removes the code that solves an important
> > use case. it's important to be able to specify the protocol or network stack,
> > such as in
> >
> > ip/ping /net.alt/icmp!someaddress
>
> Most commands use an -x option and setnetmtpt(2) to arrange
> an alternate network root. Is there any reason not to do the
> same for ip/ping?
"most" commands do not. for example,
cpu -h /net.alt/tcp!ladd.quanstro.net
sorry i haven't the time to do statistics, but i'm pretty sure that
only programs lib ndb/dnsquery that do not take dial strings are
exceptions here. and they are self-inconsistent. some take -x
(bare option) and some take -x /mnt/pt.
that notwithstanding, it seems logical to allow icmpv6!host
as a proper dial string for ping, and this requires the same code.
i think it makes sense to do it as ping and traceroute have done.
- erik
next prev parent reply other threads:[~2016-01-04 13:04 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
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 [this message]
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=f2dfab3cd6a05732cae046105f2e75c2@mule \
--to=quanstro@quanstro.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).