[ipv6calc] Suggested output format

Peter Bieringer pb at bieringer.de
Fri Apr 4 22:26:21 CEST 2003


--On Thursday, April 03, 2003 09:15:16 PM +0200 Lionel Elie Mamane
<lionel at mamane.lu> wrote:

> On Thu, Apr 03, 2003 at 08:29:37PM +0200, Peter Bieringer wrote:
> 
>> <lionel at mamane.lu> wrote:
> 
>>> ipv6calc currently doesn't support the following format:
> 
>>> network byte order, in octal notation with \-escaping
> 
>>> E.g. 2001:888:19f0:0:210:5aff:fe45:9b17 would be:
>>> \40\1\10\210\31\360\0\0\2\20\132\377\376\105\233\27

> No, just the 16 bytes, raw, each in octal notation with '\'
> prepended.

Too easy ;-)

A 15 minute hack does the job:

$ ./ipv6calc --out octal 2001:888:19f0:0:210:5aff:fe45:9b17
No input type specified, try autodetection...found type: ipv6addr
\40\1\10\210\31\360\0\0\2\20\132\377\376\105\233\27


See latest CVS whether it fits all cases. If yes, send a note and I will
create a new release.

BTW: makes it sense to implement this output format also for IPv4? It can
be done, but if not, it saves me about 10 minutes ;-)

        Peter
-- 
Dr. Peter Bieringer                     http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D               mailto: pb at bieringer dot de 
Deep Space 6 Co-Founder and Core Member  http://www.deepspace6.net/


More information about the ipv6calc mailing list