pub enum KissCode {
Show 14 variants
Unknown,
AssociationBelongsToAnycastServer,
AssociationBelongsToBroadcastServer,
AssociationBelongsToManycastServer,
ServerAuthenticationFailed,
AutokeySequenceFailed,
CryptographicAuthenticationFailed,
AccessDenied,
LostPeer,
AssociationNotYetSynchronized,
NoKeyFound,
RateExceeded,
TinkeringWithAssociation,
StepChange,
}
Expand description
Kiss code, reason of a Kiss-o’-Death reply.
Kiss code provides information about why the SNTP server sent a Kiss-o’-Death packet, i.e. why the request has been rejected. This enum is generally a 1-to-1 mapping to SNTP RFC kiss codes, see RFC 5905 section 7.4.
Variants§
Unknown
Unknown code
AssociationBelongsToAnycastServer
The association belongs to a anycast server
AssociationBelongsToBroadcastServer
The association belongs to a broadcast server
AssociationBelongsToManycastServer
The association belongs to a manycast server
ServerAuthenticationFailed
Server authentication failed
AutokeySequenceFailed
Autokey sequence failed
CryptographicAuthenticationFailed
Cryptographic authentication or identification failed
AccessDenied
Access denied by remote server
LostPeer
Lost peer in symmetric mode
AssociationNotYetSynchronized
The association has not yet synchronized for the first time
NoKeyFound
No key found. Either the key was never installed or is not trusted
RateExceeded
Rate exceeded. The server has temporarily denied access because the client exceeded the rate threshold
TinkeringWithAssociation
Somebody is tinkering with the association from a remote host running ntpdc. Not to worry unless some rascal has stolen your keys
StepChange
A step change in system time has occurred, but the association has not yet resynchronized