A thought:
Cisco IOS (routers) solved this by putting IPv6 addresses on their own line,
then indenting the following line so that the columns line up.
This is pretty easy for scripts that parse the output to accomodate, and
visually it works, at least for me.
And since they have deployed a
Oh, here's a sample:
router#show ntp assoc
address ref clock st when poll reach delay offset disp
-~2600:3C03::F03C:91FF:FEDF:9B84
128.4.40.12 3265512 377 43.274 10.649 0.032
~149.20.68.17.INIT. 16 - 1024 0
(In reply to comment #7)
Good idea, and the problem is the refid is a 32-bit structure.
Its purpose is for loop detection - to make sure machine A doesn't
believe time from machine B if machine B is getting its time from A.
I've had some chats with Prof. Mills about this and we're gently
A thought:
Cisco IOS (routers) solved this by putting IPv6 addresses on their own line,
then indenting the following line so that the columns line up.
This is pretty easy for scripts that parse the output to accomodate, and
visually it works, at least for me.
And since they have deployed a
Oh, here's a sample:
router#show ntp assoc
address ref clock st when poll reach delay offset disp
-~2600:3C03::F03C:91FF:FEDF:9B84
128.4.40.12 3265512 377 43.274 10.649 0.032
~149.20.68.17.INIT. 16 - 1024 0
(In reply to comment #7)
Good idea, and the problem is the refid is a 32-bit structure.
Its purpose is for loop detection - to make sure machine A doesn't
believe time from machine B if machine B is getting its time from A.
I've had some chats with Prof. Mills about this and we're gently
