Hi, After analysing the packets I noticed that the data being sent from my reference client were shorter than the one sent from the eCos SNTP client. Looking at RFC 2030 it turns out that difference in length is to do with the 'KeyIdentifier' and the 'Message Digest', both of which are optional.
I confirmed with another client (MacOS X) that it worked too with the Solaris server. MacOS X also omits the 'KeyIdentifier' and the 'Message Digest' in the request. Changing the SNTP client on eCos to also omit those fields resulted in a response from the SNTP server on the Solaris machine. Linux probably handles nulled filled values for these two fields, whereas Solaris seems to consider them invalid. Given this observation and the fact that they are even set to anything by eCos, is there any reason for including them in the NTP_PACKET structure? Andre On 2-Nov-06, at 11:48 , Andre-John Mas wrote: > Hi, > > We have found the SNTP client can get the time from some servers but > not others. For example we have a Linux based SNTP server from which > we can get the time, but not from the SNTP server running on our > Solaris machines. Are there any known limitations with the client > implementation. > > I am currently checking to see if it is a server configuration issue, > but I would like a confirmation as to the client to see whether I am > spending my time in the right place. > > Andre -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
