NTP at gw.ampr.org

List overview All Threads
Download

newer

older

Re: [FYI] OpenWrt Nodes - 22.03.0...

Now accepting applications for the...

lleachii＠aol.com

24 Oct 2022 24 Oct '22

9:38 p.m.

All, I'm not sure to whom to direct this question. I'm trying to research who informed me (likely the late Brian Kantor WB6CYT, SK) - that an NTP server exists at 44.0.0.1 (gw.ampr.org). Just doing some usual testing and updating of my node, I observed that there's no longer a NTP response from that IP. Is this by design, another issue, etc? I just wanted to ask, especially since AMPRGW is listed on the Wiki as an available NTP server. I wanted to update that information if the service no longer operates on that IP. -- 73, - LynwoodKB3VWG

Attachments:

attachment.html (text/html — 1.8 KB)

Show replies by date

Josh

24 Oct 24 Oct

10:05 p.m.

Hi Lynwood, I'm not seeing any issues with gw.ampr.org's NTP service from here. 12:46:24.471888 IP (tos 0xb8, ttl 61, id 41700, offset 0, flags [none], proto UDP (17), length 76) gw.ampr.org.ntp > ntp.vk2hff.ampr.org.ntp: [udp sum ok] NTPv4, length 48 Server, Leap indicator: (0), Stratum 2 (secondary reference), poll 8 (256s), precision -24 Root Delay: 0.000244, Root dispersion: 0.032897, Reference-ID: bigben.ucsd.edu - Josh VK2HFF On 25/10/2022 12:38 pm, lleachii--- via 44net wrote:

...

lleachii＠aol.com

11:09 p.m.

Josh, Interesting, I just got a response (it took a while) - I set a client to 44net (and not Public Internet) to be sure: user@machine:~$ ntpdate -q 44.0.0.1server 44.0.0.1, stratum 2, offset 0.006765, delay 0.0911724 Oct 22:53:28 ntpdate[2358]: adjust time server 44.0.0.1 offset 0.006765 sec root@OpenWrt:~# tcpdump -vvn -i tunl0 port 123tcpdump: listening on tunl0, link-type RAW (Raw IP), capture size 262144 bytes02:53:28.015158 IP (tos 0x0, ttl 63, id 45381, offset 0, flags [DF], proto UDP (17), length 76) 44.60.44.128.40861 > 44.0.0.1.123: [udp sum ok] NTPv4, length 48 Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 3 (8s), precision -6 Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID: (unspec) Reference Timestamp: 0.000000000 Originator Timestamp: 0.000000000 Receive Timestamp: 0.000000000 Transmit Timestamp: 3875655208.011475472 (2022/10/25 02:53:28) Originator - Receive Timestamp: 0.000000000 Originator - Transmit Timestamp: 3875655208.011475472 (2022/10/25 02:53:28)02:53:28.079405 IP (tos 0xb8, ttl 62, id 48601, offset 0, flags [none], proto UDP (17), length 76) 44.0.0.1.123 > 44.60.44.128.40861: [udp sum ok] NTPv4, length 48 Server, Leap indicator: (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24 Root Delay: 0.000213, Root dispersion: 0.037979, Reference-ID: 132.239.1.6 Reference Timestamp: 3875654362.142300152 (2022/10/25 02:39:22) Originator Timestamp: 3875655208.011475472 (2022/10/25 02:53:28) Receive Timestamp: 3875655208.051018718 (2022/10/25 02:53:28) Transmit Timestamp: 3875655208.051066605 (2022/10/25 02:53:28) Originator - Receive Timestamp: +0.039543245 Originator - Transmit Timestamp: +0.039591132 It doesn't respond to the Public Internet. This reminds me - does anyone have a link to the AMPRGW site that shows traffic statistics (e.g. for UDP, TCP, encaps-inside-header-not-44-SRC, etc.)? Thanks, - KB3VWG

Chris Smith

25 Oct 25 Oct

4:31 a.m.

The gateway server will respond on port 123 from 44. IPs but nothing else. Attached is yesterdays stats, is that what you were after? 73, Chris - G1FEF

...

On 25 Oct 2022, at 04:09, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote: Josh, Interesting, I just got a response (it took a while) - I set a client to 44net (and not Public Internet) to be sure: user@machine:~$ ntpdate -q 44.0.0.1 server 44.0.0.1, stratum 2, offset 0.006765, delay 0.09117 24 Oct 22:53:28 ntpdate[2358]: adjust time server 44.0.0.1 offset 0.006765 sec root@OpenWrt:~# tcpdump -vvn -i tunl0 port 123 tcpdump: listening on tunl0, link-type RAW (Raw IP), capture size 262144 bytes 02:53:28.015158 IP (tos 0x0, ttl 63, id 45381, offset 0, flags [DF], proto UDP (17), length 76) 44.60.44.128.40861 > 44.0.0.1.123: [udp sum ok] NTPv4, length 48 Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 3 (8s), precision -6 Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID: (unspec) Reference Timestamp: 0.000000000 Originator Timestamp: 0.000000000 Receive Timestamp: 0.000000000 Transmit Timestamp: 3875655208.011475472 (2022/10/25 02:53:28) Originator - Receive Timestamp: 0.000000000 Originator - Transmit Timestamp: 3875655208.011475472 (2022/10/25 02:53:28) 02:53:28.079405 IP (tos 0xb8, ttl 62, id 48601, offset 0, flags [none], proto UDP (17), length 76) 44.0.0.1.123 > 44.60.44.128.40861: [udp sum ok] NTPv4, length 48 Server, Leap indicator: (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24 Root Delay: 0.000213, Root dispersion: 0.037979, Reference-ID: 132.239.1.6 Reference Timestamp: 3875654362.142300152 (2022/10/25 02:39:22) Originator Timestamp: 3875655208.011475472 (2022/10/25 02:53:28) Receive Timestamp: 3875655208.051018718 (2022/10/25 02:53:28) Transmit Timestamp: 3875655208.051066605 (2022/10/25 02:53:28) Originator - Receive Timestamp: +0.039543245 Originator - Transmit Timestamp: +0.039591132 It doesn't respond to the Public Internet. This reminds me - does anyone have a link to the AMPRGW site that shows traffic statistics (e.g. for UDP, TCP, encaps-inside-header-not-44-SRC, etc.)? Thanks, - KB3VWG _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org

941

days inactive

941

days old

44net@mailman.ampr.org

Manage subscription

3 comments

3 participants

tags (0)

participants (3)

Chris Smith
Josh
lleachii＠aol.com