Re: CVS commit: src/external/bsd/dhcpcd/dist

[Frank Kardel <kardel%netbsd.org@localhost>]

Joerg Sonnenberger wrote:
> On Fri, Jan 09, 2009 at 07:42:03PM +0100, Frank Kardel wrote:
>   
> > In the stable version (the one NetBSD ships) it is possible to configure  
> > or unconfigure peers via ntpdc.
> >     
>
> I might be missing something, but how do I delete a peer?
>
> Joerg
ntpdc> keyid 1

ntpdc> passwd

MD5 Password: 

ntpdc> pe

    remote           local      st poll reach  delay   offset    disp

=======================================================================

^10.0.3.15       10.0.3.1        16   64    0 0.00000  0.000000 4.00000

^ff05::101       fe80::201:29ff: 16   64    0 0.00000  0.000000 4.00000

=GENERIC(0)      127.0.0.1        0   16  377 0.00000  0.000003 0.01518

=GENERIC(1)      127.0.0.1        0   64  377 0.00000  0.003531 0.03099

*PPS(0)          127.0.0.1        0   16  377 0.00000  0.000003 0.01503

^224.0.1.1       84.176.237.143  16   64    0 0.00000  0.000000 4.00000

ntpdc> adds some.peer

done!

ntpdc> pe

    remote           local      st poll reach  delay   offset    disp

=======================================================================

^10.0.3.15       10.0.3.1        16   64    0 0.00000  0.000000 4.00000

^ff05::101       fe80::201:29ff: 16   64    0 0.00000  0.000000 4.00000

=some.peer       84.176.237.143  16   64    0 0.00000  0.000000 4.00000

=GENERIC(0)      127.0.0.1        0   16  377 0.00000  0.000004 0.01523

=GENERIC(1)      127.0.0.1        0   64  377 0.00000  0.003531 0.03099

*PPS(0)          127.0.0.1        0   16  377 0.00000  0.000004 0.01515

^224.0.1.1       84.176.237.143  16   64    0 0.00000  0.000000 4.00000

ntpdc> unco some.peer

done!

ntpdc> pe

    remote           local      st poll reach  delay   offset    disp

=======================================================================

^10.0.3.15       10.0.3.1        16   64    0 0.00000  0.000000 4.00000

^ff05::101       fe80::201:29ff: 16   64    0 0.00000  0.000000 4.00000

=GENERIC(0)      127.0.0.1        0   16  377 0.00000  0.000004 0.01538

=GENERIC(1)      127.0.0.1        0   64  377 0.00000  0.003711 0.03113

*PPS(0)          127.0.0.1        0   16  377 0.00000  0.000004 0.01584

^224.0.1.1       84.176.237.143  16   64    0 0.00000  0.000000 4.00000

ntpdc> 

For that you need at add a key to the key file. select a requestkey and 
that also as trusted key.
Then you can use ntpdc for configuration of peers.

Before the dynamic interface code there where some script solutions that 
used ntpdc to
make ntpd aware of changes of peers.

See http://bugs.ntp.org/51 - the scripts are in the attachments.

Frank

PS: shouldn't we move ntp config discussions away from source-changes@ ?