Rich, I suggest you don't want that. What you need is a fudge on the interface, not the association. A fudge on the association is hard due to the limitations imposed by the configuration process. For instance, some Sun machines show asymmetric delays on the Ether interfaces of over two milliseconds. It gets even harder with multiple interfaces of different types on the same machine. Even harder for gigabit Etherfaces with interrupt coalescing.
Dave Rich Wales wrote: >My home network is connected to the outside world via a cable modem. > >I'm running a refclock at home (on a FreeBSD server running ntpd >4.2.5p215), which I want to refer to both at home and elsewhere. >The cable modem system appears to be introducing an offset of about >2 msec (compared to a refclock on my work network, which I have >reason to believe is trustworthy). > >I would like to be able to tell ntpd (4.2.5p181) on my work machine >to fudge the offset it gets from my home clock by about 2 msec, in >order to counter the cable modem assymetry. > >However, I do *not* want to fudge the offset on the refclock itself, >because I want the hosts on my home network to see the server "as is". >I'm not sure what to do, because as best I can tell, I can specify a >"fudge time1" only in connection with a refclock. > >Is there any way to fudge the offset on a "peer" or (non-refclock) >"server" configuration command? If not, can this be considered as >an enhancement? Or am I missing some very good reason why this is a >Really Bad Idea that should (and will) never be implemented? > >Rich Wales / ri...@richw.org >_______________________________________________ >questions mailing list >questions@lists.ntp.org >https://lists.ntp.org/mailman/listinfo/questions > > _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
