On Thursday 22 September 2005 06:16 pm, Arnold Schekkerman wrote: > 0x5b0 has the 0x20 bit set: 0xb0 = 0x80 + 0x20 + 0x10 (0xB == 11 decimal)
D'oh! I've been living in the world of high-level languages too long.
> So your limiting is working! :-)
But it's *not* working, or at least my understanding of it:
$ ntpdc -nc
remote address port local address count m ver code avgint lstint
===============================================================================
71.10.124.9 62936 10.0.5.16 8276 3 4 5b0 81 85
That shows this particular client to be limited, right? And yet:
$ sudo tcpdump -n port 123 and host 71.10.124.9
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
22:11:18.121024 IP 71.10.124.9.62936 > 10.0.5.16.123: NTPv4, Client, length 48
22:11:18.121218 IP 10.0.5.16.123 > 71.10.124.9.62936: NTPv4, Server, length 48
22:11:19.125007 IP 71.10.124.9.62936 > 10.0.5.16.123: NTPv4, Client, length 48
22:11:19.125208 IP 10.0.5.16.123 > 71.10.124.9.62936: NTPv4, Server, length 48
22:11:22.167848 IP 71.10.124.9.62936 > 10.0.5.16.123: NTPv4, Client, length 48
22:11:22.167919 IP 10.0.5.16.123 > 71.10.124.9.62936: NTPv4, Server, length 48
22:11:23.118427 IP 71.10.124.9.62936 > 10.0.5.16.123: NTPv4, Client, length 48
22:11:23.118630 IP 10.0.5.16.123 > 71.10.124.9.62936: NTPv4, Server, length 48
22:11:24.140489 IP 71.10.124.9.62936 > 10.0.5.16.123: NTPv4, Client, length 48
22:11:24.140682 IP 10.0.5.16.123 > 71.10.124.9.62936: NTPv4, Server, length 48
Here's my server, cheerfully replying to every single packet from that
client. It looks like I'm even returning valid answers, if I'm reading
this correctly:
$ sudo tcpdump -vv -n port 123 and host 71.10.124.9
tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
22:14:16.159827 IP (tos 0x0, ttl 50, id 0, offset 0, flags [DF], proto: UDP
(17), length: 76) 71.10.124.9.62936 > 10.0.5.16.123: [udp sum ok] NTPv4, length
48
Client, Leap indicator: (0), Stratum 11, poll 6s, precision -20
Root Delay: 0.000000, Root dispersion: 0.012039, Reference-ID:
127.127.1.0
Reference Timestamp: 3336433929.833383999 (2005/09/22 22:12:09)
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 3336433937.833414999 (2005/09/22 22:12:17)
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 3336433937.833414999 (2005/09/22
22:12:17)
22:14:16.160016 IP (tos 0x10, ttl 64, id 9831, offset 0, flags [none], proto:
UDP (17), length: 76) 10.0.5.16.123 > 71.10.124.9.62936: [udp sum ok] NTPv4,
length 48
Server, Leap indicator: (0), Stratum 2, poll 6s, precision -19
Root Delay: 0.073501, Root dispersion: 0.055480, Reference-ID:
192.43.244.18
Reference Timestamp: 3336432659.859969212 (2005/09/22 21:50:59)
Originator Timestamp: 3336433937.833414999 (2005/09/22 22:12:17)
Receive Timestamp: 3336434056.159917082 (2005/09/22 22:14:16)
Transmit Timestamp: 3336434056.159972677 (2005/09/22 22:14:16)
Originator - Receive Timestamp: +118.326502083
Originator - Transmit Timestamp: +118.326557678
My response doesn't look like the description of a kod packet that I'd read
in ntp.conf(5).
--
Kirk Strauser
pgpdk6INzPd6a.pgp
Description: PGP signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
