Arul,

This was a deliberate choice to avoid interaction between misconfigured
conditions. Consider what happens if some perp configures peer and
client associations with the same server. Formerly, this was really bad
news; now it actually works, even if ill advised.

Dave

Arul Kumar C wrote:
> Hi Experts,
>
> Could you please help me in understanding the difference between the
> findexistingpeer() in NTPv3 and NTPv4. In NTPv4 the findexistingpeer()
> additionally check the mode too. Why is this so ? This could allow
> two different associations for a same server with different mode, right
> ?
>
> Could you please explain the reason for this change, if any ?
>
> Thanks,
> Arul Kumar C
> -~-
>

Hi Dave,

I got the reason. Thanks for this info.

Thanks,
Arul Kumar C
-~-

David L. Mills wrote:
> Arul,
>
> This was a deliberate choice to avoid interaction between misconfigured
> conditions. Consider what happens if some perp configures peer and
> client associations with the same server. Formerly, this was really bad
> news; now it actually works, even if ill advised.
>
> Dave
>
> Arul Kumar C wrote:
> > Hi Experts,
> >
> > Could you please help me in understanding the difference between the
> > findexistingpeer() in NTPv3 and NTPv4. In NTPv4 the findexistingpeer()
> > additionally check the mode too. Why is this so ? This could allow
> > two different associations for a same server with different mode, right
> > ?
> >
> > Could you please explain the reason for this change, if any ?
> >
> > Thanks,
> > Arul Kumar C
> > -~-
> >