Re: Reminder - Team FTF meeting, make your travel plans now
Sanjeev Gupta : > On Fri, Apr 15, 2016 at 12:23 PM, Gary E. Miller wrote: > > > Oh, I'm bringing some guns. :-) > > > Well, that is one way to clean up the issue tracker[1], I suppose. > > [1] Offer a free training lesson to anyone who closes a bug. Jeez, what > were you thinking I meant? Free training will indeed be offered at the Geeks With Guns range expedition early Friday afternoon. I will be one of the range officers. -- http://www.catb.org/~esr/";>Eric S. Raymond ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: Reminder - Team FTF meeting, make your travel plans now
Gary E. Miller : > Yo Eric! > > On Fri, 15 Apr 2016 01:30:54 -0400 > "Eric S. Raymond" wrote: > > > Gary E. Miller : > > > Anyone going near the airport Thursday night? > > > > Possibly Cathy and me. What time are you landing? > > That would be great. I in at 8pm from MSP. Arrgh. No can do. By 8PM we'll already have been there for hours in order to make the GOH dinner. Sorry. -- http://www.catb.org/~esr/";>Eric S. Raymond signature.asc Description: Digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Finding abusive NTP clients
I just pushed a tweak to ntpq's mrulist command to provide more info if the average interval between requests is tiny. Anybody running a pool server might like to try it out. It now looks like this: ntpq> hostnames no ntpq> mru mincount=1000 sort=avgint Ctrl-C will stop MRU retrieval and display partial results. Retrieved 239 unique MRU entries and 0 updates. lstint avgint rstr r m v count rport remote address == 35374 0.03 190 . 3 4 5046 44762 64.72.56.95 670 0.04 190 . 3 4 4148 38778 162.243.188.66 57962 0.06 190 . 3 4 1345 33523 96.41.112.161 90455 0.07 190 . 3 3 1877 49488 2601:644:500:e800:a9d6:8245:1f95:b31b 66199 0.07 190 . 3 3 2081 54645 159.191.174.119 47234 0.07 190 . 3 3 1084 40403 108.227.128.23 62845 0.08 190 . 3 3 1956 47876 71.95.206.54 19026 0.08 190 . 3 1 3931 63329 190.14.219.238 460 0.08 190 . 3 4 1877 56897 72.130.39.211 40670 0.08 190 . 3 3 1629 42184 98.203.248.229 90375 0.09 190 . 3 4 1185 38002 24.56.50.247 60720 0.09 190 . 3 3 1599 65462 216.100.91.14 16506 0.09 190 . 3 3 1026 57813 75.172.167.145 7633 0.09 190 . 3 3 1557 37974 67.1.146.70 58813 0.10 190 . 3 1 3134 2410 73.179.193.171 5947 0.10 190 . 3 3 1171 52276 104.32.81.108 90798 0.11 190 . 3 4 1388 34042 198.199.99.66 ... -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: Reminder - Team FTF meeting, make your travel plans now
Gary E. Miller : > Anyone going near the airport Thursday night? Possibly Cathy and me. What time are you landing? > Oh, I'm bringing some guns. :-) Excellent. Geeks With Guns will welcome you. -- http://www.catb.org/~esr/";>Eric S. Raymond signature.asc Description: Digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: Finding abusive NTP clients
On Fri, Apr 15, 2016 at 7:05 PM, Hal Murray wrote: > I just pushed a tweak to ntpq's mrulist command to provide more info if the > average > interval between requests is tiny. Anybody running a pool server might > like > to try it out. > I am running a server in the SG pool. Suggestions welcome. root@ntpmon:~/ntpsec# ntpq -V ntpd 0.9.3-e13b054 Apr 15 2016 22:07:22 root@ntpmon:~/ntpsec# clear root@ntpmon:~/ntpsec# ntpq ntpq> hostnames no ntpq> mru mincount=1000 sort=avgint Ctrl-C will stop MRU retrieval and display partial results. Retrieved 58 unique MRU entries and 0 updates. lstint avgint rstr r m v count rport remote address == 0 0.01 1f0 L 3 4 32250 123 27.126.220.102 0 0.02 1f0 L 3 4 35659 123 27.126.220.105 0 0.02 1f0 L 3 4 35789 123 27.126.220.106 0 0.02 1f0 L 3 4 35766 123 27.126.220.103 0 0.02 1f0 L 3 4 35780 123 27.126.220.101 0 0.02 1f0 L 3 4 32843 123 27.126.220.104 1 0.51 1f0 L 3 3 2877243 18012 202.136.171.166 0 1.14 1f0 L 3 4 1282569 54878 52.74.115.126 1 1.71 5f0 K 1 1 1074 49332 116.87.59.232 14 2.35 1f0 L 3 4 5761 44258 52.74.95.23 0 2.91 1f0 L 3 4 86573 52007 58.182.99.14 4 2.92 1f0 L 3 4 454070 7950 155.69.160.32 2 3.14 1f0 L 3 3 159948 356 110.50.226.157 1 3.24 1f0 L 3 4 75141 38130 116.87.179.211 3 4.69 1f0 L 3 3 311400 59081 202.151.35.238 -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: Finding abusive NTP clients
++ On Fri, Apr 15, 2016 at 7:28 AM Sanjeev Gupta wrote: > > On Fri, Apr 15, 2016 at 7:05 PM, Hal Murray > wrote: > >> I just pushed a tweak to ntpq's mrulist command to provide more info if >> the >> average >> interval between requests is tiny. Anybody running a pool server might >> like >> to try it out. >> > > I am running a server in the SG pool. Suggestions welcome. > > root@ntpmon:~/ntpsec# ntpq -V > ntpd 0.9.3-e13b054 Apr 15 2016 22:07:22 > root@ntpmon:~/ntpsec# clear > root@ntpmon:~/ntpsec# ntpq > > ntpq> hostnames no > ntpq> mru mincount=1000 sort=avgint > Ctrl-C will stop MRU retrieval and display partial results. > Retrieved 58 unique MRU entries and 0 updates. > > lstint avgint rstr r m v count rport remote address > > == > 0 0.01 1f0 L 3 4 32250 123 27.126.220.102 > 0 0.02 1f0 L 3 4 35659 123 27.126.220.105 > 0 0.02 1f0 L 3 4 35789 123 27.126.220.106 > 0 0.02 1f0 L 3 4 35766 123 27.126.220.103 > 0 0.02 1f0 L 3 4 35780 123 27.126.220.101 > 0 0.02 1f0 L 3 4 32843 123 27.126.220.104 > 1 0.51 1f0 L 3 3 2877243 18012 202.136.171.166 > 0 1.14 1f0 L 3 4 1282569 54878 52.74.115.126 > 1 1.71 5f0 K 1 1 1074 49332 116.87.59.232 > 14 2.35 1f0 L 3 4 5761 44258 52.74.95.23 > 0 2.91 1f0 L 3 4 86573 52007 58.182.99.14 > 4 2.92 1f0 L 3 4 454070 7950 155.69.160.32 > 2 3.14 1f0 L 3 3 159948 356 110.50.226.157 > 1 3.24 1f0 L 3 4 75141 38130 116.87.179.211 > 3 4.69 1f0 L 3 3 311400 59081 202.151.35.238 > > > -- > Sanjeev Gupta > +65 98551208 http://www.linkedin.com/in/ghane > ___ > devel mailing list > devel@ntpsec.org > http://lists.ntpsec.org/mailman/listinfo/devel ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
soon, Navisys GR-701-W
Hi! I have just ordered a batch of the Navisys GR-701-W USB connected GPS receivers. They are probably at least 5 weeks from delivery to my hackerspace. When they arrive, I will ship some to some NTPsec people, and then put the rest up for sale as an electronics part up on Etsy and Tindie, probably for about $45/each. If I work out a good enough way to do it, I may have the NTPsec logo & url silkscreened onto the them. The GR-701-W provides only a USB interface, and so lacks the final precision of a PPS interface. OTOH, someone can just thoughtlessly plug one into a random PC or WRG, install gpsd&ntpsec, and have a good-enough compliant stratum 1 server. I decided not to at this time order a lot of the Navisys GR-701-T, which is a TTL interface with a PPS line. While this is a more precise source and easier for RasbPi/etc hobbyists, they are more likely to want to use the GPS receiver HAT and daughterboard units already easily available to them. ..m ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: soon, Navisys GR-701-W
On 2016-04-15 17:57 +, Mark Atwood wrote: > Hi! > > I have just ordered a batch of the Navisys GR-701-W USB connected GPS > receivers.?? They are probably at least 5 weeks from delivery to my > hackerspace. When they arrive, I will ship some to some NTPsec people, and > then put the rest up for sale as an electronics part up on Etsy and Tindie, > probably for about $45/each. If I work out a good enough way to do it, I > may > have the NTPsec logo & url silkscreened onto the them. Very cool! I could certainly take two of these. I have been looking for some USB GPS receivers but I have absolutely no idea bout them. It's tough to find one that seems reasonable/reliable. > I decided not to at this time order a lot of the Navisys GR-701-T, which is a > TTL interface with a PPS line.?? While this is a more precise source and > easier > for RasbPi/etc hobbyists, they are more likely to want to use the GPS receiver > HAT and daughterboard units already easily available to them. Makes sense. I'm looking at buying ~20 GPS chips and soldering up my own boards for them. This way if the chip fails all I have to do is replace that the rest of the parts will be robust. They're going to be cycled a lot so I expect a lot of failures over time. Amar. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: soon, Navisys GR-701-W
Yo Mark! On Fri, 15 Apr 2016 17:57:30 + Mark Atwood wrote: > The GR-701-W provides only a USB interface, and so lacks the final > precision of a PPS interface. Only a low speed USB interface. I have been beating on them to upgrade to High Speed. That ups the PPS from +/1 1mill Sec to around +/- 125 micro Sec. > plug one into a random PC or WRG, install gpsd&ntpsec, and have a > good-enough compliant stratum 1 server. Yup. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 pgph6nHULj4LD.pgp Description: OpenPGP digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: Reminder - Team FTF meeting, make your travel plans now
Yo Eric! On Fri, 15 Apr 2016 06:59:07 -0400 "Eric S. Raymond" wrote: > > That would be great. I in at 8pm from MSP. > > Arrgh. No can do. By 8PM we'll already have been there for hours > in order to make the GOH dinner. Sorry. No worries, I'll get something to work. RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 pgpcTkntuzqIy.pgp Description: OpenPGP digital signature ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
