[ntp:questions] Re: Problems with ntpdsim

David L. Mills mills at udel.edu
Fri Feb 25 21:35:31 UTC 2005


Mauro,

I don't know what you are doing, but your data spans more than one day. 
  It could be you have more than one host in the configuration file. The 
simulator supports only one at the moment. The peerstats aren't very 
useful in simulation. The loopstats are the most useful, as they show 
the response of the system to time steps, etc.

Dave

Mauro Fiacco wrote:

> Hi,
> 
> I am trying to use ntpdsim. However, it seems that it has some problems,
> I wander if anybody can help me.
> 
> The following are the first few lines from the logs, generated by
> ntpdsim (it includes peerstats and rawstats):
> 
> /* snip */
> 15024 83085.708 172.28.0.6 172.28.0.121 717.000499750 128.000000000 128.000000000 3439032598.811603069
> 15024 83085.708 172.28.0.6 9034 427967118.093948603 0.000000238 7.937500238 0.000000238
> 15024 75140.593 172.28.0.6 172.28.0.121 1230.000499750 128.000000000 128.000000000 3455949340.705173373
> 15024 75140.593 172.28.0.6 9054 419508490.647163451 0.000000238 7.937500238 0.000000238
> 15025 51821.994 172.28.0.6 172.28.0.121 15816.000499750 128.000000000 128.000000000 3358973125.535136700
> 15025 51821.994 172.28.0.6 90f4 467989305.232181787 0.000000238 7.937500238 0.000000238
> 15025 27093.276 172.28.0.6 172.28.0.121 16331.000499750 128.000000000 128.000000000 3409461076.636985421
> 15025 27093.276 172.28.0.6 90f4 442745072.181257427 0.000000238 7.937500238 0.000000238
> 15024 80372.756 172.28.0.6 172.28.0.121 16847.000499750 128.000000000 128.000000000 3476734632.346126676
> 15024 80372.756 172.28.0.6 90f4 409108036.326686800 0.000000238 7.937500238 0.000000238
> /* snip */
> 
> Note that the large difference between the first and last timestamp
> values... also the entries are randomly ordered
> 
> I am using the suggested argument values for netdsim.
> 
> Regards,
> 
> Mauro
> 
> PS I also get this line from the debug option which may be relevant (??):
> 
>         peer 172.28.0.251 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
> 
> 



More information about the questions mailing list