These are the flash codes that I found in 3-5.92. They probably apply to your situation but I don't guarantee it.
/* * Define flasher bits (tests 1 through 8 in packet procedure) * These reveal the state at the last grumble from the peer and are * most handy for diagnosing problems, even if not strictly a state * variable in the spec. These are recorded in the peer structure. */ #define TEST1 0x01 /* duplicate packet received */ #define TEST2 0x02 /* bogus packet received */ #define TEST3 0x04 /* protocol unsynchronized */ #define TEST4 0x08 /* peer delay/dispersion bounds check */ #define TEST5 0x10 /* peer authentication failed */ #define TEST6 0x20 /* peer clock unsynchronized */ #define TEST7 0x40 /* peer stratum out of bounds */ #define TEST8 0x80 /* root delay/dispersion bounds check */ Danny -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
