NTP server remain in Soliciting pool server



  • Hi,

    i configured my pfsense box to act as ntp server but when i start service i have in log:

    Jul 6 22:34:14 pfsense ntpd[16302]: Soliciting pool server 85.199.214.99
    Jul 6 22:34:19 pfsense ntpd[16302]: Soliciting pool server 193.234.225.237
    Jul 6 22:34:50 pfsense ntpd[16302]: Soliciting pool server 193.183.98.38
    Jul 6 22:35:01 pfsense ntpd[16302]: Soliciting pool server 151.3.106.211
    Jul 6 22:35:18 pfsense ntpd[16302]: Soliciting pool server 147.135.207.213
    Jul 6 22:35:24 pfsense ntpd[16302]: Soliciting pool server 212.45.144.3
    Jul 6 22:35:55 pfsense ntpd[16302]: Soliciting pool server 37.247.53.178
    Jul 6 22:36:05 pfsense ntpd[16302]: Soliciting pool server 193.204.114.233
    Jul 6 22:36:23 pfsense ntpd[16302]: Soliciting pool server 94.177.187.22
    Jul 6 22:36:28 pfsense ntpd[16302]: Soliciting pool server 212.45.144.206

    and server doesn't align to any ntp peer

    ntpq -c pe
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     0.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
     1.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
     2.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
     3.pfsense.pool. .POOL.          16 p    -   64    0    0.000    0.000   0.000
    
    
    ntpq -c rv
    associd=0 status=0016 leap_none, sync_unspec, 1 event, restart,
    version="ntpd 4.2.8p11@1.3728-o Wed Feb 28 13:29:50 UTC 2018 (1)",
    processor="amd64", system="FreeBSD/11.1-RELEASE-p10", leap=00,
    stratum=12, precision=-22, rootdelay=0.000, rootdisp=0.000,
    refid=127.0.0.1,
    reftime=00000000.00000000  Thu, Feb  7 2036  7:28:16.000,
    clock=deea5285.5da9aa9e  Fri, Jul  6 2018 22:41:41.365, peer=0, tc=3,
    mintc=3, offset=0.000000, frequency=0.000, sys_jitter=0.000000,
    clk_jitter=0.000, clk_wander=0.000
    
    

    ntpdate works with any server...

    Suggestion?





  • Thank you for the hint, i try to set outbound NAT but without any results.

    I think i have a cmos battery problem on server....



  • tracing internet interface i see:

    07:39:34.139358 IP (tos 0xb8, ttl 64, id 60682, offset 0, flags [none], proto UDP (17), length 76)
        host234-*************************.62795 > host122-133-14-31.serverdedicati.aruba.it.ntp: [bad udp cksum 0xe1cf -> 0x1415!] NTPv4, length 48
    	Client, Leap indicator:  (0), Stratum 12 (secondary reference), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: localhost
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739930774.139337060 (2018/07/07 07:39:34)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739930774.139337060 (2018/07/07 07:39:34)
    
    

  • Rebel Alliance Global Moderator

    And there is no answer in that trace.. A cmos battery has ZERO to do with not getting any answers.

    On your query you see via your internet interface what is the source IP? Did it get changed to your public IP? via your outbound nat?

    Can not sync time if you do not get any answers.

    example - here is sniff showing answers to queries

    0_1530961441738_ntpanswers.png

    You can send queries all day long - if you don't get answers then no ntp can not set time. You not showing what your public IP is.. So maybe its sending it with your rfc1918 address? See mine starts with 64.43 - this is pfsense wan IP.



  • i have only an internet interface that isn't WAN (now is disabled for migration reason and i use another internet interface, on firewall i have only outbound rules for that interface) and my interface ip is: 80.19.236.234

    in trace i see:

    2:54:59.035150 IP (tos 0xb8, ttl 64, id 10329, offset 0, flags [none], proto UDP (17), length 76)
        host234-236-static.19-80-b.business.telecomitalia.it.20029 > host122-133-14-31.serverdedicati.aruba.it.ntp: [bad udp cksum 0xe1cf -> 0x957f!] NTPv4, length 48
    	Client, Leap indicator:  (0), Stratum 12 (secondary reference), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: localhost
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739949699.035073183 (2018/07/07 12:54:59)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739949699.035073183 (2018/07/07 12:54:59)
    12:55:18.035092 IP (tos 0xb8, ttl 64, id 30896, offset 0, flags [none], proto UDP (17), length 76)
        host234-236-static.19-80-b.business.telecomitalia.it.3022 > host209-165-213-188.serverdedicati.aruba.it.ntp: [bad udp cksum 0x9fee -> 0xef4e!] NTPv4, length 48
    	Client, Leap indicator:  (0), Stratum 12 (secondary reference), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: localhost
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739949718.035045195 (2018/07/07 12:55:18)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739949718.035045195 (2018/07/07 12:55:18)
    12:55:20.035051 IP (tos 0xb8, ttl 64, id 61237, offset 0, flags [none], proto UDP (17), length 76)
        host234-236-static.19-80-b.business.telecomitalia.it.14535 > radha.parvati.it.ntp: [bad udp cksum 0xae7e -> 0xd173!] NTPv4, length 48
    	Client, Leap indicator:  (0), Stratum 12 (secondary reference), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: localhost
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739949720.035028167 (2018/07/07 12:55:20)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739949720.035028167 (2018/07/07 12:55:20)
    
    

    it's the same address


  • Rebel Alliance Global Moderator

    See my edit on above post - if you do not not get answers then no you can not set ntp time. Your just showing queries for time, no answers. Also why you seeing bad cksum?

    You sure your sending out the right interface - you see inbound traffic on this interface to your public IP 80.19.x.x?



  • yes i don't receive answers, i try to disable hw checksum and i have the same result (tcpdump with -n option):

    13:14:55.219835 IP (tos 0xb8, ttl 64, id 56864, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.57839 > 213.251.52.250.123: [udp sum ok] NTPv4, length 48
    	Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000045, Reference-ID: (unspec)
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739950895.219811470 (2018/07/07 13:14:55)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739950895.219811470 (2018/07/07 13:14:55)
    13:14:55.221144 IP (tos 0xb8, ttl 64, id 41563, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.28614 > 212.45.144.3.123: [udp sum ok] NTPv4, length 48
    	Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000045, Reference-ID: (unspec)
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739950895.221124008 (2018/07/07 13:14:55)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739950895.221124008 (2018/07/07 13:14:55)
    
    

    with ntpdate it works:

    13:16:43.059987 IP (tos 0x0, ttl 64, id 39284, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.32668 > 212.45.144.88.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:   3739951003.059947639 (2018/07/07 13:16:43)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739951003.059947639 (2018/07/07 13:16:43)
    13:16:43.094639 IP (tos 0x0, ttl 51, id 60653, offset 0, flags [none], proto UDP (17), length 76)
        212.45.144.88.123 > 80.19.236.234.32668: [udp sum ok] NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 5 (32s), precision -23
    	Root Delay: 0.003234, Root dispersion: 0.027084, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739950267.035690859 (2018/07/07 13:04:27)
    	  Originator Timestamp: 3739951003.059947639 (2018/07/07 13:16:43)
    	  Receive Timestamp:    3739951003.122896487 (2018/07/07 13:16:43)
    	  Transmit Timestamp:   3739951003.122907538 (2018/07/07 13:16:43)
    	    Originator - Receive Timestamp:  +0.062948848
    	    Originator - Transmit Timestamp: +0.062959899
    13:16:43.259950 IP (tos 0x0, ttl 64, id 1511, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.65245 > 94.177.187.22.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:   3739951003.259929982 (2018/07/07 13:16:43)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739951003.259929982 (2018/07/07 13:16:43)
    
    

  • Rebel Alliance Global Moderator

    I only see 1 response from 212.45.144.88, set that as you server - do you get answers from that when doing normal polling?



  • ntpdate pool.ntp.org (working):

    17:37:28.738900 IP (tos 0x0, ttl 64, id 46241, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.16997 > 37.247.53.178.123: 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:   3739966648.738873633 (2018/07/07 17:37:28)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966648.738873633 (2018/07/07 17:37:28)
    17:37:28.774609 IP (tos 0x0, ttl 55, id 17361, offset 0, flags [none], proto UDP (17), length 76)
        37.247.53.178.123 > 80.19.236.234.16997: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -17
    	Root Delay: 0.002838, Root dispersion: 0.022964, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739966429.211028222 (2018/07/07 17:33:49)
    	  Originator Timestamp: 3739966648.738873633 (2018/07/07 17:37:28)
    	  Receive Timestamp:    3739966648.846336729 (2018/07/07 17:37:28)
    	  Transmit Timestamp:   3739966648.846437153 (2018/07/07 17:37:28)
    	    Originator - Receive Timestamp:  +0.107463096
    	    Originator - Transmit Timestamp: +0.107563520
    17:37:28.938863 IP (tos 0x0, ttl 64, id 4622, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.37969 > 31.14.133.122.123: 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:   3739966648.938848221 (2018/07/07 17:37:28)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966648.938848221 (2018/07/07 17:37:28)
    17:37:28.977245 IP (tos 0x18, ttl 54, id 36942, offset 0, flags [DF], proto UDP (17), length 76)
        31.14.133.122.123 > 80.19.236.234.37969: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24
    	Root Delay: 0.013458, Root dispersion: 0.035873, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739965342.476267622 (2018/07/07 17:15:42)
    	  Originator Timestamp: 3739966648.938848221 (2018/07/07 17:37:28)
    	  Receive Timestamp:    3739966649.042009668 (2018/07/07 17:37:29)
    	  Transmit Timestamp:   3739966649.042053883 (2018/07/07 17:37:29)
    	    Originator - Receive Timestamp:  +0.103161446
    	    Originator - Transmit Timestamp: +0.103205661
    17:37:29.138852 IP (tos 0x0, ttl 64, id 64406, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.9901 > 193.204.114.233.123: 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:   3739966649.138839090 (2018/07/07 17:37:29)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966649.138839090 (2018/07/07 17:37:29)
    17:37:29.175421 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.9901: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966636.937985248 (2018/07/07 17:37:16)
    	  Originator Timestamp: 3739966649.138839090 (2018/07/07 17:37:29)
    	  Receive Timestamp:    3739966649.245455990 (2018/07/07 17:37:29)
    	  Transmit Timestamp:   3739966649.245526093 (2018/07/07 17:37:29)
    	    Originator - Receive Timestamp:  +0.106616899
    	    Originator - Transmit Timestamp: +0.106687002
    17:37:30.738873 IP (tos 0x0, ttl 64, id 42645, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.16997 > 37.247.53.178.123: 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:   3739966650.738848566 (2018/07/07 17:37:30)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966650.738848566 (2018/07/07 17:37:30)
    17:37:30.774733 IP (tos 0x0, ttl 55, id 41113, offset 0, flags [none], proto UDP (17), length 76)
        37.247.53.178.123 > 80.19.236.234.16997: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -17
    	Root Delay: 0.002838, Root dispersion: 0.022994, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739966429.211028222 (2018/07/07 17:33:49)
    	  Originator Timestamp: 3739966650.738848566 (2018/07/07 17:37:30)
    	  Receive Timestamp:    3739966650.845466964 (2018/07/07 17:37:30)
    	  Transmit Timestamp:   3739966650.845567208 (2018/07/07 17:37:30)
    	    Originator - Receive Timestamp:  +0.106618398
    	    Originator - Transmit Timestamp: +0.106718642
    17:37:30.938866 IP (tos 0x0, ttl 64, id 22256, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.37969 > 31.14.133.122.123: 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:   3739966650.938847131 (2018/07/07 17:37:30)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966650.938847131 (2018/07/07 17:37:30)
    17:37:30.977591 IP (tos 0x18, ttl 54, id 37204, offset 0, flags [DF], proto UDP (17), length 76)
        31.14.133.122.123 > 80.19.236.234.37969: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24
    	Root Delay: 0.013458, Root dispersion: 0.035903, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739965342.476267622 (2018/07/07 17:15:42)
    	  Originator Timestamp: 3739966650.938847131 (2018/07/07 17:37:30)
    	  Receive Timestamp:    3739966651.041143178 (2018/07/07 17:37:31)
    	  Transmit Timestamp:   3739966651.041201581 (2018/07/07 17:37:31)
    	    Originator - Receive Timestamp:  +0.102296046
    	    Originator - Transmit Timestamp: +0.102354450
    17:37:31.138859 IP (tos 0x0, ttl 64, id 11417, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.9901 > 193.204.114.233.123: 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:   3739966651.138844175 (2018/07/07 17:37:31)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966651.138844175 (2018/07/07 17:37:31)
    17:37:31.175286 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.9901: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966636.937985248 (2018/07/07 17:37:16)
    	  Originator Timestamp: 3739966651.138844175 (2018/07/07 17:37:31)
    	  Receive Timestamp:    3739966651.244656434 (2018/07/07 17:37:31)
    	  Transmit Timestamp:   3739966651.244685454 (2018/07/07 17:37:31)
    	    Originator - Receive Timestamp:  +0.105812258
    	    Originator - Transmit Timestamp: +0.105841278
    17:37:32.738866 IP (tos 0x0, ttl 64, id 64921, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.16997 > 37.247.53.178.123: 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:   3739966652.738848264 (2018/07/07 17:37:32)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966652.738848264 (2018/07/07 17:37:32)
    17:37:32.775080 IP (tos 0x0, ttl 55, id 35789, offset 0, flags [none], proto UDP (17), length 76)
        37.247.53.178.123 > 80.19.236.234.16997: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -17
    	Root Delay: 0.002838, Root dispersion: 0.023025, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739966429.211028222 (2018/07/07 17:33:49)
    	  Originator Timestamp: 3739966652.738848264 (2018/07/07 17:37:32)
    	  Receive Timestamp:    3739966652.844773115 (2018/07/07 17:37:32)
    	  Transmit Timestamp:   3739966652.844876786 (2018/07/07 17:37:32)
    	    Originator - Receive Timestamp:  +0.105924851
    	    Originator - Transmit Timestamp: +0.106028522
    17:37:32.938853 IP (tos 0x0, ttl 64, id 31164, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.37969 > 31.14.133.122.123: 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:   3739966652.938839968 (2018/07/07 17:37:32)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966652.938839968 (2018/07/07 17:37:32)
    17:37:32.977196 IP (tos 0x18, ttl 54, id 37226, offset 0, flags [DF], proto UDP (17), length 76)
        31.14.133.122.123 > 80.19.236.234.37969: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24
    	Root Delay: 0.013458, Root dispersion: 0.035934, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739965342.476267622 (2018/07/07 17:15:42)
    	  Originator Timestamp: 3739966652.938839968 (2018/07/07 17:37:32)
    	  Receive Timestamp:    3739966653.040010133 (2018/07/07 17:37:33)
    	  Transmit Timestamp:   3739966653.040064491 (2018/07/07 17:37:33)
    	    Originator - Receive Timestamp:  +0.101170164
    	    Originator - Transmit Timestamp: +0.101224523
    17:37:33.138883 IP (tos 0x0, ttl 64, id 42750, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.9901 > 193.204.114.233.123: 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:   3739966653.138859943 (2018/07/07 17:37:33)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966653.138859943 (2018/07/07 17:37:33)
    17:37:33.174924 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.9901: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966636.937985248 (2018/07/07 17:37:16)
    	  Originator Timestamp: 3739966653.138859943 (2018/07/07 17:37:33)
    	  Receive Timestamp:    3739966653.243290990 (2018/07/07 17:37:33)
    	  Transmit Timestamp:   3739966653.243319572 (2018/07/07 17:37:33)
    	    Originator - Receive Timestamp:  +0.104431046
    	    Originator - Transmit Timestamp: +0.104459628
    17:37:34.738862 IP (tos 0x0, ttl 64, id 56543, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.16997 > 37.247.53.178.123: 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:   3739966654.738846807 (2018/07/07 17:37:34)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966654.738846807 (2018/07/07 17:37:34)
    17:37:34.773463 IP (tos 0x0, ttl 55, id 18526, offset 0, flags [none], proto UDP (17), length 76)
        37.247.53.178.123 > 80.19.236.234.16997: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -17
    	Root Delay: 0.002838, Root dispersion: 0.023056, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739966429.211028222 (2018/07/07 17:33:49)
    	  Originator Timestamp: 3739966654.738846807 (2018/07/07 17:37:34)
    	  Receive Timestamp:    3739966654.842268114 (2018/07/07 17:37:34)
    	  Transmit Timestamp:   3739966654.842390639 (2018/07/07 17:37:34)
    	    Originator - Receive Timestamp:  +0.103421307
    	    Originator - Transmit Timestamp: +0.103543831
    17:37:34.938852 IP (tos 0x0, ttl 64, id 29619, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.37969 > 31.14.133.122.123: 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:   3739966654.938838098 (2018/07/07 17:37:34)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966654.938838098 (2018/07/07 17:37:34)
    17:37:34.980999 IP (tos 0x18, ttl 54, id 37334, offset 0, flags [DF], proto UDP (17), length 76)
        31.14.133.122.123 > 80.19.236.234.37969: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 3 (8s), precision -24
    	Root Delay: 0.013458, Root dispersion: 0.035964, Reference-ID: 193.204.114.233
    	  Reference Timestamp:  3739965342.476267622 (2018/07/07 17:15:42)
    	  Originator Timestamp: 3739966654.938838098 (2018/07/07 17:37:34)
    	  Receive Timestamp:    3739966655.039145234 (2018/07/07 17:37:35)
    	  Transmit Timestamp:   3739966655.039811867 (2018/07/07 17:37:35)
    	    Originator - Receive Timestamp:  +0.100307136
    	    Originator - Transmit Timestamp: +0.100973768
    17:37:35.138849 IP (tos 0x0, ttl 64, id 26680, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.9901 > 193.204.114.233.123: 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:   3739966655.138838748 (2018/07/07 17:37:35)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966655.138838748 (2018/07/07 17:37:35)
    17:37:35.175490 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.9901: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966636.937985248 (2018/07/07 17:37:16)
    	  Originator Timestamp: 3739966655.138838748 (2018/07/07 17:37:35)
    	  Receive Timestamp:    3739966655.242506354 (2018/07/07 17:37:35)
    	  Transmit Timestamp:   3739966655.242539580 (2018/07/07 17:37:35)
    	    Originator - Receive Timestamp:  +0.103667605
    	    Originator - Transmit Timestamp: +0.103700831
    
    

    ntpdate 193.204.114.233 (working):

    17:39:37.151932 IP (tos 0x0, ttl 64, id 20750, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.21986 > 193.204.114.233.123: 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:   3739966777.151878014 (2018/07/07 17:39:37)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966777.151878014 (2018/07/07 17:39:37)
    17:39:37.188592 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.21986: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966764.937969415 (2018/07/07 17:39:24)
    	  Originator Timestamp: 3739966777.151878014 (2018/07/07 17:39:37)
    	  Receive Timestamp:    3739966777.195522184 (2018/07/07 17:39:37)
    	  Transmit Timestamp:   3739966777.195590332 (2018/07/07 17:39:37)
    	    Originator - Receive Timestamp:  +0.043644169
    	    Originator - Transmit Timestamp: +0.043712317
    17:39:39.151861 IP (tos 0x0, ttl 64, id 32849, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.21986 > 193.204.114.233.123: 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:   3739966779.151836144 (2018/07/07 17:39:39)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966779.151836144 (2018/07/07 17:39:39)
    17:39:39.188923 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.21986: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966764.937969415 (2018/07/07 17:39:24)
    	  Originator Timestamp: 3739966779.151836144 (2018/07/07 17:39:39)
    	  Receive Timestamp:    3739966779.194457897 (2018/07/07 17:39:39)
    	  Transmit Timestamp:   3739966779.194492815 (2018/07/07 17:39:39)
    	    Originator - Receive Timestamp:  +0.042621753
    	    Originator - Transmit Timestamp: +0.042656671
    17:39:41.151849 IP (tos 0x0, ttl 64, id 30116, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.21986 > 193.204.114.233.123: 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:   3739966781.151832129 (2018/07/07 17:39:41)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966781.151832129 (2018/07/07 17:39:41)
    17:39:41.188473 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.21986: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966764.937969415 (2018/07/07 17:39:24)
    	  Originator Timestamp: 3739966781.151832129 (2018/07/07 17:39:41)
    	  Receive Timestamp:    3739966781.193585521 (2018/07/07 17:39:41)
    	  Transmit Timestamp:   3739966781.193621093 (2018/07/07 17:39:41)
    	    Originator - Receive Timestamp:  +0.041753392
    	    Originator - Transmit Timestamp: +0.041788964
    17:39:43.151850 IP (tos 0x0, ttl 64, id 39611, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.21986 > 193.204.114.233.123: 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:   3739966783.151834198 (2018/07/07 17:39:43)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966783.151834198 (2018/07/07 17:39:43)
    17:39:43.188581 IP (tos 0x18, ttl 55, id 0, offset 0, flags [DF], proto UDP (17), length 76)
        193.204.114.233.123 > 80.19.236.234.21986: NTPv4, length 48
    	Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision -21
    	Root Delay: 0.000000, Root dispersion: 0.000106, Reference-ID: CTD^@
    	  Reference Timestamp:  3739966764.937969415 (2018/07/07 17:39:24)
    	  Originator Timestamp: 3739966783.151834198 (2018/07/07 17:39:43)
    	  Receive Timestamp:    3739966783.192476902 (2018/07/07 17:39:43)
    	  Transmit Timestamp:   3739966783.192562134 (2018/07/07 17:39:43)
    	    Originator - Receive Timestamp:  +0.040642704
    	    Originator - Transmit Timestamp: +0.040727936
    
    

    ntpd configured with server 193.204.114.233 (not working)

    17:41:11.813935 IP (tos 0xb8, ttl 64, id 52443, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.60873 > 193.204.114.233.123: NTPv4, length 48
    	Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739966871.813850720 (2018/07/07 17:41:11)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966871.813850720 (2018/07/07 17:41:11)
    17:42:17.813841 IP (tos 0xb8, ttl 64, id 44388, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.60873 > 193.204.114.233.123: NTPv4, length 48
    	Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.000991, Reference-ID: (unspec)
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739966937.813828187 (2018/07/07 17:42:17)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739966937.813828187 (2018/07/07 17:42:17)
    17:43:22.813852 IP (tos 0xb8, ttl 64, id 33761, offset 0, flags [none], proto UDP (17), length 76)
        80.19.236.234.24047 > 193.204.114.233.123: NTPv4, length 48
    	Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 6 (64s), precision -22
    	Root Delay: 0.000000, Root dispersion: 0.001968, Reference-ID: (unspec)
    	  Reference Timestamp:  0.000000000
    	  Originator Timestamp: 0.000000000
    	  Receive Timestamp:    0.000000000
    	  Transmit Timestamp:   3739967002.813821695 (2018/07/07 17:43:22)
    	    Originator - Receive Timestamp:  0.000000000
    	    Originator - Transmit Timestamp: 3739967002.813821695 (2018/07/07 17:43:22)
    
    
    
    

    ntpd.log:

    Jul  7 17:41:10 pfsense ntpd[97948]: 193.204.114.233 8011 81 mobilize assoc 6563
    Jul  7 17:41:10 pfsense ntpd[97948]: 0.0.0.0 c01d 0d kern kernel time sync enabled
    Jul  7 17:41:10 pfsense ntpd[97948]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM
    Jul  7 17:41:10 pfsense ntpd[97948]: 0.0.0.0 c016 06 restart
    
    
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     ntp2.inrim.it   .INIT.          16 u    -   64    0    0.000    0.000   0.000
    
    ntpq> readvar
    associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart,
    version="ntpd 4.2.8p11@1.3728-o Wed Feb 28 13:29:50 UTC 2018 (1)",
    processor="amd64", system="FreeBSD/11.1-RELEASE-p10", leap=11,
    stratum=16, precision=-22, rootdelay=0.000, rootdisp=3.045, refid=INIT,
    reftime=00000000.00000000  Thu, Feb  7 2036  7:28:16.000,
    clock=deeb5e61.fea0d439  Sat, Jul  7 2018 17:44:33.994, peer=0, tc=3,
    mintc=3, offset=0.000000, frequency=0.000, sys_jitter=0.000000,
    clk_jitter=0.000, clk_wander=0.000
    
    
    ind assid status  conf reach auth condition  last_event cnt
    ===========================================================
      1  6563  8011   yes    no  none    reject    mobilize  1
    
    

  • Rebel Alliance Global Moderator

    And are you getting answers? Your reach is 0 (zero) you can not sync time if you do not get answers...

    You seem to be sending out the queries - but if you do not get an answer, then no you can not sync... That has ZERO to do with pfsense.

    What is this

    Thu, Feb 7 2036

    ntpq> readvar
    associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
    version="ntpd 4.2.8p11@1.3728-o Fri Mar 16 18:58:06 UTC 2018 (1)",
    processor="amd64", system="FreeBSD/11.1-RELEASE-p10", leap=00, stratum=2,
    precision=-21, rootdelay=0.230, rootdisp=14.828, refid=192.168.3.32,
    reftime=deeb62ad.1d5fcc1b  Sat, Jul  7 2018 11:02:53.114,
    clock=deeb6310.a0d7f0a0  Sat, Jul  7 2018 11:04:32.628, peer=23915, tc=9,
    mintc=3, offset=0.120466, frequency=3.615, sys_jitter=0.127323,
    clk_jitter=0.157, clk_wander=0.017
    

    If your sending ref of 2036 - maybe the ntp server your asking just ignores you and does not answer. See my reftime

    Looks like your normal queries are using a date of feb 7, 2036... Adjust the date and time on your pfsense box to be atleast close! ;)



  • reftime=00000000.00000000 Thu, Feb 7 2036 7:28:16.000 is not the problem at initial sync...

    i've configured another internal ntp server that works and pfsense box ntpd using that server works...


  • Rebel Alliance Global Moderator

    So your saying ntp works talking to your ntp server locally, but does not get answers remotely? But it not getting answers is related to what? How is an ntp server not answering something you clearly sent out pfsense issue? If it was something wrong with the query - then your local ntp server wouldn't answer it either.

    Your local ntp server taking a different path to sync to outside, is it not syncing to outside?



  • my local ntp server reach internet through pfsense box and works fine, sync and serve.

    pfsense box using my local ntp server works fine:

    ntpq> readvar
    associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
    version="ntpd 4.2.8p11@1.3728-o Wed Feb 28 13:29:50 UTC 2018 (1)",
    processor="amd64", system="FreeBSD/11.1-RELEASE-p10", leap=00, stratum=3,
    precision=-22, rootdelay=36.095, rootdisp=47.551, refid=10.10.11.2,
    reftime=deec69b4.f16fb644  Sun, Jul  8 2018 12:45:08.943,
    clock=deec69bf.29ca9dae  Sun, Jul  8 2018 12:45:19.163, peer=44435, tc=6,
    mintc=3, offset=2.311372, frequency=3.350, sys_jitter=0.000000,
    clk_jitter=0.134, clk_wander=0.052
    
    
    ntpq> peers
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     10.10.11.2      .POOL.          16 p    -   64    0    0.000    0.000   0.000
    *wpad.*****.**  193.204.114.105  2 u   35   64  377    0.145    2.311   0.049
    
    
    ntpq> as
    
    ind assid status  conf reach auth condition  last_event cnt
    ===========================================================
      1 44434  8811   yes  none  none    reject    mobilize  1
      2 44435  161a    no   yes  none  sys.peer    sys_peer  1
    
    
    

  • Rebel Alliance Global Moderator

    Why would you have it marked pool when clearly its not?

    So my question is does this ntp server take the same "path" to the internet that pfsense would take on its own? Or are you routing this traffic different pfsense local traffic would take - ie the default route/gateway?

    You stated

    i have only an internet interface that isn't WAN (now is disabled for migration reason



  • for pool configuration is just an oversight.

    ntp server take the same path of pfsense (not WAN)


  • Rebel Alliance Global Moderator

    Well that makes zero sense - is the ntp server using the same servers you were trying to sync pfsense with?

    You sure the ref time thing is not an issue. I don't recall every seeing such a ref time.. it is one of the rollover dates.. Now that your ntp is syncing and your time is good. What if you change to from your local server to external on pfsense?

    So your saying that when you ntp server that is internal talks to the outside to sync its time its using the same bath and "the same source ip" as when pfsense itself goes out to the internet to talk to ntp. That 80.19.a.b address, your sure its not say 80.19.a.c ? or something like that?

    Makes not sense that ntp server would answer your client, but not the client on pfsense?

    What version of pfsense are you using? 2.4.3p1?



  • 0_1531055737710_Screenshot from 2018-07-08 15-15-04.png

    yes the same servers.

    mtr from my local server:

    0_1531055952421_Screenshot from 2018-07-08 15-17-49.png

    mtr from my pfsense box

    0_1531055969317_Screenshot from 2018-07-08 15-18-37.png

    it's the same...


  • Rebel Alliance Global Moderator

    Not what I asked exactly... I asked if the source IP is the same..

    While you might hit the same gateway that .233, maybe your coming from .A when natting your clients behind pfsense but pfsense is using .B as its IP. For example if you have a VIP setup when you have multiple IPs from the ISP..

    You only have the 1 public IP, and no vips setup on pfsense where it could be using a different source IP.

    Just makes no sense that your not getting any replies to your queries when pfsense does them, but do get replies when client behind pfsense does the query.



  • 80.19.236.233 is my public router

    80.19.236.234 is my pfsense public interface directly connected to 80.19.236.233

    ntp internal server is 10.10.11.2 connected to pfsense 10.10.11.1


  • Rebel Alliance Global Moderator

    Well then why does server X not respond to a ntp query when it comes from pfsense, but does respond when it comes from client behind pfsense? That is the million dollar question.

    Since the source IP is the same. The clients are the same ntp version it looks like.

    ntpd 4.2.8p11@1.3728-o

    So I would suggest you set pfsense to use both your local ntp, and public ntp. It will now query both of them. Are you not seeing answers from the public ones? See my output below, you see pfsense syncs to my local stratum 1 ntp server I run. But it also asks pool as backup to if my local goes down (pi with gps as my ntp server). you will notice that they all show reach of 377.. Means talking to them and getting answers..

    0_1531132271539_ntpservers.png



  • @johnpoz said in NTP server remain in Soliciting pool server:

    Well then why does server X not respond to a ntp query when it comes from pfsense, but does respond when it comes from client behind pfsense? That is the million dollar question.

    yes, pfsense box not respond to a ntp query but a client of pfsense box works.

    I tried to configured local and public ntp server but public doesn't work as usual...


  • Rebel Alliance Global Moderator

    Makes ZERO sense... Really going to need a sniff on your outbound interface so we can see the ntp queries from your client behind pfsense and the queries from pfsense itself so we can try and figure out why the ones from pfsense do not get any responses.

    I would suggest you sniff on your outbound interface for 123 udp with host of one of the public servers your client and pfsense are doing queries for.

    Then download this and open in wireshark.. Maybe we can spot the difference in the queries that would explain why the server doesn't respond, or its possible maybe it is and its not getting back to you. I run a server in the pool.. So its open to the internet IPv4 and IPv6.. Let me send you the IP in a private chat - and set pfsense to use that server. And I can sniff on my wan to see if getting your query and if I send a response.

    I will setup a sniff right now for your 80.x.x.x IP... Give me 2 seconds.


  • Rebel Alliance Global Moderator

    Ok I have sniff running for your IP on my wan udp 123... Set pfsense to use this IP and see if you get any responses or not.. Let me know after its been running a few minutes and I will stop the sniff and take a look

    BTW: please do not post my full public IP its 64.53.x.x



  • Ok, some ntp packet sent to your ntp but without any response.


  • Rebel Alliance Global Moderator

    No nothing captured.. I never got those packets.


  • Rebel Alliance Global Moderator

    Not from that IP you say is your public IP. You sure pfsense is sending them out the right hole??


  • Rebel Alliance Global Moderator

    Since it seems now via chat you do have VIPs... How about you post your outbound nats so we can figure out what IP pfsense would use vs your clients when talking outbound.



  • 0_1531160651020_Screenshot from 2018-07-09 20-23-54.png


  • Rebel Alliance Global Moderator

    There are no hybrid rules above that? Or below that? From those your clients and pfsense itself would be using whatever the IP of ADSL20PUB is... Do you have other connections? What interfaces do you have your ntp set to use in the ntp setup page?

    Do you have any port forwards setup on your client interfaces for ntp? (udp 123)



  • @johnpoz said in NTP server remain in Soliciting pool server:

    There are no hybrid rules above that? Or below that?

    No only Automatic outbound NAT rule generation.

    Do you have other connections?

    No, only ADSL20PUB, WAN is disabled

    What interfaces do you have your ntp set to use in the ntp setup page?

    all interfaces except ADSL20PUB

    Do you have any port forwards setup on your client interfaces for ntp? (udp 123)

    No, only 1:1 nat on virtual IP


  • Rebel Alliance Global Moderator

    well makes no sense at all then dude... I suggest you sniff on this adsl20pub interface with pfsense and clients doing ntp to same server so we can try and figure out what is going on.

    From your outbound nat it would not be possible for your clients to be using any other IP other than adsl20pub interface. So how is it exactly you have VIPs setup?? Are they for inbound only traffic?

    What I can tel you is I never saw an traffic from your IP o 123 UDP.. So if I never got it - its impossible for me to answer.

    So your dong 1:1 nat, but you outbound nat to your adsl20pub... So if your on a client and you go to whatsmyip you see the adsl20pub IP??

    Are you doing a 1:1 nat with this .234 IP?

    Make sure your client that is working behind is pointing to a different ntp server than pfsense when you do your sniff so we can be sure of which traffic is what in the sniff.



  • @johnpoz said in NTP server remain in Soliciting pool server:

    well makes no sense at all then dude...

    yes...doesn't has sense at all.

    So how is it exactly you have VIPs setup?? Are they for inbound only traffic?

    only 3 web server (one for each VIP configured) with 80, 443 and 8080 port open

    So your dong 1:1 nat, but you outbound nat to your adsl20pub... So if your on a client and you go to whatsmyip you see the adsl20pub IP?

    my 1:1 natted server show VIP assigned on whatsmyip

    normal client (as ntp server) show ADSL20PUB main address

    juniper@kirk:~$ curl ipinfo.io/ip
    80.19.236.234
    
    


  • pfsense box show:

    [2.4.3-RELEASE][admin@pfsense.mkdevice.it]/root: curl ipinfo.io/ip
    80.19.236.234
    
    

  • Rebel Alliance Global Moderator

    you do understand that ntp is going to bind to one of the IPs your listening on and use that for its queries right.. So that could be different when it goes outbound.. But if you have auto outbound nat then its should be the your adsl20pub IP.

    Set your ntp server to use say 1.2.3.4 (some public ntp server) grab listing for your country on the ntp site. Set your client to use different public ntp server say 4.5.6.7... Then sniff on your adsl20pub interface for udp 123 and we should see these queries go out. We can then look at them in wireshark and try and figure out why queries pfsense is doing is not getting answered. My IP never saw queries from that 80.19.236.234 address that is for sure. And I get and answer 100's of ntp queries every few minutes My IP is member of ntp pool.



  • attached two trace, one of my ntp local server and one of pfsense box with the same server configured.

    1_1531170243257_pfsense.pcap 0_1531170243256_local.pcap