> On 30/05/2016, at 11:39 PM, Miroslav Lichvar wrote:
>
> On Mon, May 30, 2016 at 10:55:31PM +1200, Bryan Christianson wrote:
>> I like the MAC-style format too. Even without IPv6 we have the ambiguity
>> associated with reference clocks
>> e.g.
>> Reference ID:
> On 30/05/2016, at 7:22 PM, Miroslav Lichvar wrote:
>
> On Sat, May 28, 2016 at 10:17:31AM +1200, Bryan Christianson wrote:
>>
>> Maybe it could just be displayed as 8 hex digits.
>
> I think that would be the best solution. I was considering to use
> the MAC-style
On Sat, May 28, 2016 at 10:17:31AM +1200, Bryan Christianson wrote:
> >>> This has been argued in the past. The refid is 4 bytes, so it cannot fit
> >>> in
> >>> the whole IPv6 address. And it really is not worth expanding the size of
> >>> the
> >>> refid. For refclocks it is a four character
Maybe for chrony 2.5 (I think its probably too late for 2.4) the chronyc
tracking display should carry a warning that the first field is not an IP
address and that the format will change in the future. The change could then be
made in chrony 2.6.
Do you really want an extra paragraph of
> On 28/05/2016, at 10:08 AM, Bill Unruh wrote:
>
>
>
> William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
> Physics | Advanced Research | Fax: +1(604)822-5324
> UBC, Vancouver,BC | Program in Cosmology | un...@physics.ubc.ca
> Canada
> On 28/05/2016, at 9:56 AM, Bill Unruh wrote:
>
> On Sat, 28 May 2016, Bryan Christianson wrote:
>
>> I recently installed an IPv6 network on my lan. When crony syncs to a server
>> using IPv6 it extracts some bits from the IPv6 address of the server and
>> then
On Sat, 28 May 2016, Bryan Christianson wrote:
I recently installed an IPv6 network on my lan. When crony syncs to a server
using IPv6 it extracts some bits from the IPv6 address of the server and then
displays them in the Reference ID as an IPv4 address which bears no
relationship to any