Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jan 2008 22:18:10 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        net@freebsd.org
Subject:   Re: Text for IPv6 Scope
Message-ID:  <20080108220558.L36482@maildrop.int.zabbadoz.net>
In-Reply-To: <864pdongvk.wl%rpaulo@fnop.net>
References:  <20080104215626.GA88922@goku.pumpky.net> <477F674F.7020706@FreeBSD.org> <864pdongvk.wl%rpaulo@fnop.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Jan 2008, Rui Paulo wrote:

> At Sat, 05 Jan 2008 11:17:35 +0000,
> Bruce M. Simpson wrote:
>>
>> Crist J. Clark wrote:
>>> Anyone up for adding text to the scopeid field in the ifconfig(8)
>>> output for IPv6 addresses? Other OSes do. To avoid too much
>>> disruption to the current format, the text is appended after the
>>> currently printed hexadecimal field.
>>>
>>> Example:
>>>
>>> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>>         options=8<VLAN_MTU>
>>>         inet6 fe80::290:27ff:fe13:2540%fxp0 prefixlen 64 scopeid 0x5(site-local)
>>>
>>> While we're at it, update the in6.h file to include all scopes
>>> in RFC4291.
>>>
>>> Look OK? Anyone up for applying these?
>>
>> This kind of output might be cooler?
>>
>>         inet6 fe80::290:27ff:fe13:2540%fxp0 prefixlen 64 scope site
>>
>
> Yes, I would want something like this too, we don't really need the numbers.

I'd go with something number+space+text as that going to least likely
break existing scripts (unless they match on line end;).

Another thing I am worried about is the output getting more likely
>80 chars which is a bit of a pain.

-- 
Bjoern A. Zeeb                                 bzeeb at Zabbadoz dot NeT
Software is harder than hardware  so better get it right the first time.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080108220558.L36482>