[cid:image.png@b6e4bcbbf655a54c797d3ff.b6e4bcbbf] Hi,
Thanks for reaching out. If it were up to us, we’d solve all your problems, but renter’s insurance is what we do best. For everything else, we suggest you contact your leasing professional or property management company. Feel free send us your questions by responding to this email. You can also give us a call using the toll-free number below, Monday through Friday, 8 a.m-8 p.m. EST. Assurant Insurance Service Center On behalf of Greystar Phone 1.800.249.1104 Email greys...@assurant.com Need a faster response? Chat with us 8AM – 5PM Monday – Friday at https://resident.assurant.com/poi/confirmation. You will need the three letter Client ID and resident ID listed in the subject line above. You can also self-service your Assurant policy by visiting www.MyAssurantPolicy.com<http://www.MyAssurantPolicy.com>. ------------------- Original Message ------------------- From: vom513 <vom...@gmail.com>; Received: Sat Dec 03 2022 13:54:34 GMT-0500 (Eastern Standard Time) To: questions@lists.ntp.org; Subject: [questions] Local ST 1 (GPS/GNSS) servers are consistently offset from internet ST1/2 Hello all, This has been bugging me for a bit - but not enough till now to post a message :) I have two boxes here at home (this is “hobbyist” grade gear, not big commercial appliances). My hardware is: SyncBOX - https://www.worldtimesolutions.com/products/gps_time_server.html This is connected to a small “Jetway” x86 mini PC via DB9 / real UART serial. UPUTronics Pi Hat - https://thepihut.com/products/raspberry-pi-gps-hat It’s on a Pi obviously (3B I think) Both of these appear to be very stable. I graph the offset in MRTG and they both average about +/- 1-2 us. However - when I compare them each individually to a list of about 10 public ST1 and ST2 servers, they both are averaging about -3.5 ms offset. I did this with ntpdate -q and punched the values into Excel. To also back this data up - I feed a public pool member with these two guys - and my graphs on the server management page also show ~ -3.5 ms offset. (These are the same box…) https://www.ntppool.org/scores/216.143.11.126 https://www.ntppool.org/scores/2607:ff70:11::10 Also - ignore the scatter up above 0. I recently set prefer on both these guys to nail them down and track the pool graphs. So while I guess 3ms isn’t the end of the world, I’m just scratching my head as to why both my boxes are consistent with this offset from the “world”. I suppose I could config both to offset by this amount in their config, but that seems a bit heavy handed. I’d much rather understand why they both converge at this offset. Thanks in advance for any info and clue. PS: Something I just thought of before I hit send… Both of these are behind my home cable modem. And while the jitter is actually pretty good, I know there is inherent latency and jitter in most current DOCSIS networks. I think DOCSIS 3.1 has some really nice bufferbloat / latency / jitter “fixes” (AQM I think it’s called) - but my provider isn’t there yet (and I’m on Docsis 3.0 anyway). Could this be it ? -- This is questions@lists.ntp.org Subscribe: questions+subscr...@lists.ntp.org Unsubscribe: questions+unsubscr...@lists.ntp.org ********************************************************************** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you.
