From owner-freebsd-net@FreeBSD.ORG Wed Feb 12 06:25:13 2014 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E51B48B0; Wed, 12 Feb 2014 06:25:12 +0000 (UTC) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A8D1D1ADB; Wed, 12 Feb 2014 06:25:12 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id lf10so8713163pab.18 for ; Tue, 11 Feb 2014 22:25:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=iKJ2QkNTVTByqscPi65H1/eflrTPeTH9kIIId6tISXk=; b=oz00q7Bm+wZV/hZ65dWSkRiMX9OG52b2qMbM6QKyB3nmuFaGV579qjerYTAoEP/oKq 4VQsb0r8/84foTYT2cC2gGH8T2TOXcSojKio+BS4aDvUnXOF8KYnElQW1zb14ZGHLyVT Ibx2CtxJnuffbQzvxJFolppafMLlNYqTQd4eOs59cCZzVGSmNlBSypYhhCvEVS4Yvn26 tOPY9GHUgd+Kb8LWDgsl2dhIMbGy9PFXPJOuTVKk5TEsGFeupxsXvpzDEgeQzOUpOjrb lnxw19J9/WT2g6uWgpbqJHS5axTwFrmmtz1mMtNe8tktVzJRN9kj9yrKqaSwDMB77uQu soew== MIME-Version: 1.0 X-Received: by 10.66.121.234 with SMTP id ln10mr37182915pab.20.1392186312336; Tue, 11 Feb 2014 22:25:12 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.30.1 with HTTP; Tue, 11 Feb 2014 22:25:12 -0800 (PST) In-Reply-To: References: <1063008459.20140111160525@serebryakov.spb.ru> <52D14140.3090003@gibfest.dk> <20140111.143644.41639035.sthaug@nethelp.no> <52D15185.50802@gibfest.dk> <0c45208d87526a80f559ac09e28163c2.authenticated@ultimatedns.net> Date: Tue, 11 Feb 2014 22:25:12 -0800 X-Google-Sender-Auth: Or25MvNbKOiJruB4YCglMfAQBM4 Message-ID: Subject: Re: Merge ping+ping6 and traceroue+traceroute6 to single utilities? From: Kevin Oberman To: Jason Hellenthal Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "lev@freebsd.org" , Jim Thompson , Thomas Steen Rasmussen , Eitan Adler , Chris H , "sthaug@nethelp.no" , "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 06:25:13 -0000 On Tue, Feb 11, 2014 at 9:56 PM, Jason Hellenthal wrote: > It would be awesome if there was a -rfc1149 flag that would print a ascii > pigeon to the terminal... > > > On Wed, Feb 12, 2014 at 12:41 AM, Eitan Adler > wrote: > > > On Wed, Feb 12, 2014 at 12:19 AM, Jim Thompson wrote: > > > > > > > > >> On Feb 11, 2014, at 21:25, Jason Hellenthal > > wrote: > > >> > > >> Haha careful 64 might be considered 64bit protocol support ;-) > > > > > > IPv6 addresses are 128 bits, (because: innumeracy). > > > > > >> and someone might confuse 46 as a DHCP option rfc2132 > > > > > > The NetBIOS node type? > > > The joke might be funnier as 0x46, which is the VISA protocol (an > > instrumentation bus). > > > > I'm just waiting for RFC 1149 support. > > > > > > > > -- > > Eitan Adler > > > For those who are new at IPv6, the ping6 and traceroute6 commands come from the WIDE KAME project. KAME developed one of the earliest IPv6 stacks and WIDE used FreeBSD. It became the FreeBSD IPv6 stack and the ping6 and traceroute6 utilities were brought in with the rest of the KAME code. When these tools were written, the IPv6 stack and the supporting libraries and APIs were very primitive. I suspect that it was quicker to write new tools than to try to integrate IPv6 into the existing standard tools and , when things were so rough, there was a clear effort to avoid changes to working IPv4 code. Separate IPv4 and IPv6 tools made sense then, but the need has long vanished... probably even before the KAME project ended. But the old, separate tools lived on through simple inertia. And so it is today. Inertia is NO reason that it should be this way forever. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com