pfSense Gold Subscription

Author Topic: wierd bug: MULTIPLE:SINGLE?  (Read 2870 times)

0 Members and 1 Guest are viewing this topic.

Offline energy

  • Jr. Member
  • **
  • Posts: 40
  • Karma: +0/-0
    • View Profile
wierd bug: MULTIPLE:SINGLE?
« on: October 03, 2006, 11:17:36 pm »
I think since I installed RC3-B, I have the whole day long and its still going on and it even dont go away even when reset states 100 times and rebooted like 5 times.
When i do tcpdump -vv i see hundreds of crazy packets all from arp who-has (different ip's from 10.0.0.0/8 and lot of different ip's from normal net ranges)
I know udp port 132 is for nntp time but this is crazy. Anyone know how this fix this?



udp    myip:61955 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:57860 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51463 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63751 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:49672 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61194 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51470 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61200 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:64017 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:64275 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60180 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62230 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62742 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:54556 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51997 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50468 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60200 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:54825 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61737 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52783 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61747 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60724 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50486 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51255 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:57144 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60729 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59197 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58430 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58178 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61766 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62025 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62027 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52813 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:64081 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53332 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:49752 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53082 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60251 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58205 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50270 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60766 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:64100 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50023 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59240 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60013 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:56686 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63599 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62832 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62579 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:49268 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:64372 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52597 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63096 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59259 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53628 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59004 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62076 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60546 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60291 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58507 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50316 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51596 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:56460 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50829 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52110 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51087 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50064 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50066 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:56470 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:56726 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53145 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61084 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53149 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:65438 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:55202 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61606 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59815 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62375 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50088 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52137 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:55977 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:54192 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60343 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51898 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50363 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:53181 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:55742 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58303 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61122 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62658 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:54468 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63439 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:59861 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60886 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63447 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61657 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:51420 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:49630 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62174 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52193 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:50404 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:61669 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:65509 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:52454 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:49642 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:63978 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:57069 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:55022 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:62969 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60922 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:57597 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:58365 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:55550 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:56574 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp    myip:60671 -> ISP DNS Server:53    MULTIPLE:SINGLE
udp     myip:63528 -> 204.9.53.11:123     MULTIPLE:MULTIPLE
udp    myip:57784 -> ISP DNS Server:53    MULTIPLE:MULTIPLE
udp    myip:50064 -> 213.84.230.57:123    MULTIPLE:MULTIPLE
udp    myip:55573 -> 194.88.2.60:123    MULTIPLE:MULTIPLE
udp    myip:64807 -> 62.166.22.106:123    MULTIPLE:MULTIPLE
udp    myip:57258 -> 213.84.46.114:123    MULTIPLE:MULTIPLE
udp    myip:55511 -> 213.84.251.124:123    MULTIPLE:MULTIPLE
udp    myip:64094 -> 213.84.14.169:123    MULTIPLE:MULTIPLE
udp    myip:60533 -> 81.207.92.186:123    MULTIPLE:MULTIPLE
udp     myip:58641 -> 216.75.55.11:123     MULTIPLE:MULTIPLE

« Last Edit: October 03, 2006, 11:20:32 pm by energy »

Offline hoba

  • Administrator
  • Hero Member
  • *****
  • Posts: 5837
  • Karma: +3/-0
  • What was the problem to this solution again?
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #1 on: October 04, 2006, 01:10:51 am »
RC3b changes the ntp-daemon that is in use for syncing your time. Do you see lots of ntpd messages ( like Oct 4 08:10:11    ntpd[660]: adjusting local clock by 0.150322s ) in your systemlogs? Maybe your hardwareclock is not very accurate and it tries to compensate this by syncing very often? I checked states at one of my boxes that runs RC3b since a day before we released it and it only shows few connections like these and also not all the time. However ntpd seems to be a bit more active than the previously used version that was replaced due to having randomly kind of dns issues on some hardware.

Offline energy

  • Jr. Member
  • **
  • Posts: 40
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #2 on: October 04, 2006, 01:38:56 am »
RC3b changes the ntp-daemon that is in use for syncing your time. Do you see lots of ntpd messages ( like Oct 4 08:10:11    ntpd[660]: adjusting local clock by 0.150322s ) in your systemlogs? Maybe your hardwareclock is not very accurate and it tries to compensate this by syncing very often? I checked states at one of my boxes that runs RC3b since a day before we released it and it only shows few connections like these and also not all the time. However ntpd seems to be a bit more active than the previously used version that was replaced due to having randomly kind of dns issues on some hardware.


Yes its spamming like hell and its sending lots of packages, so its a bug that need to be fixed?

Offline hoba

  • Administrator
  • Hero Member
  • *****
  • Posts: 5837
  • Karma: +3/-0
  • What was the problem to this solution again?
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #3 on: October 04, 2006, 02:29:28 am »
Maybe we need to have a closer look to only let ntp jump in to the specified periods. We'll look into it.

Offline energy

  • Jr. Member
  • **
  • Posts: 40
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #4 on: October 04, 2006, 12:15:10 pm »
My hardware clock is setup right but check out the system log:

Oct 4 18:59:49    ntpd[1131]: adjusting local clock by 0.208591s
Oct 4 18:48:12    ntpd[1131]: adjusting local clock by 0.144876s
Oct 4 17:51:08    ntpd[1131]: adjusting local clock by 0.175209s
Oct 4 17:46:53    ntpd[1131]: adjusting local clock by 0.228473s
Oct 4 17:36:52    ntpd[1131]: adjusting local clock by 0.170004s
Oct 4 16:27:00    ntpd[1131]: adjusting local clock by 0.187381s
Oct 4 15:30:26    ntpd[1131]: adjusting local clock by 0.166316s
Oct 4 15:27:04    ntpd[1131]: adjusting local clock by 0.252670s
Oct 4 15:20:42    ntpd[1131]: adjusting local clock by 0.170410s
Oct 4 14:17:06    ntpd[1131]: adjusting local clock by 0.140318s
Oct 4 14:10:38    ntpd[1131]: adjusting local clock by 0.203578s
Oct 4 14:00:32    ntpd[1131]: adjusting local clock by 0.219042s
Oct 4 12:45:40    ntpd[1131]: adjusting local clock by 0.192782s
Oct 4 12:38:23    ntpd[1131]: adjusting local clock by 0.174781s
Oct 4 12:12:46    ntpd[1131]: adjusting local clock by -0.306057s
Oct 4 12:09:40    ntpd[1131]: adjusting local clock by -1.844034s
Oct 4 12:06:59    ntpd[1131]: adjusting local clock by -2.422097s
Oct 4 12:04:11    ntpd[1131]: adjusting local clock by -3.195886s
Oct 4 12:00:42    ntpd[1131]: adjusting local clock by -4.306083s
Oct 4 11:56:56    ntpd[1131]: adjusting local clock by -5.861005s
Oct 4 11:52:34    ntpd[1131]: adjusting local clock by -6.574293s
Oct 4 11:48:50    ntpd[1131]: adjusting local clock by -7.879791s
Oct 4 11:45:09    ntpd[1131]: adjusting local clock by -9.119301s
Oct 4 11:41:19    ntpd[1131]: adjusting local clock by -10.229933s
Oct 4 11:37:50    ntpd[1131]: adjusting local clock by -11.361811s
Oct 4 11:34:41    ntpd[1131]: adjusting local clock by -12.165456s
Oct 4 11:30:21    ntpd[1131]: adjusting local clock by -13.657401s
Oct 4 11:28:30    ntpd[1131]: adjusting local clock by -14.681717s
Oct 4 11:24:09    ntpd[1131]: adjusting local clock by -15.575149s
Oct 4 11:22:01    ntpd[1131]: adjusting local clock by -16.541050s
Oct 4 11:17:43    ntpd[1131]: adjusting local clock by -17.187066s
Oct 4 11:15:02    ntpd[1131]: adjusting local clock by -18.556671s
Oct 4 11:11:44    ntpd[1131]: adjusting local clock by -19.297054s
Oct 4 11:07:38    ntpd[1131]: adjusting local clock by -20.383986s
Oct 4 11:04:32    ntpd[1131]: adjusting local clock by -21.382426s
Oct 4 11:00:13    ntpd[1131]: adjusting local clock by -22.650962s
Oct 4 10:55:54    ntpd[1131]: adjusting local clock by -24.131263s
Oct 4 10:52:09    ntpd[1131]: adjusting local clock by -25.482542s
Oct 4 10:48:18    ntpd[1131]: adjusting local clock by -26.317656s
Oct 4 10:46:02    ntpd[1131]: adjusting local clock by -27.360983s
Oct 4 10:43:53    ntpd[1131]: adjusting local clock by -28.251769s
Oct 4 10:41:12    ntpd[1131]: adjusting local clock by -28.717556s
Oct 4 10:37:35    ntpd[1131]: adjusting local clock by -30.159572s
Oct 4 10:33:42    ntpd[1131]: adjusting local clock by -31.241637s
Oct 4 10:29:59    ntpd[1131]: adjusting local clock by -32.539856s
Oct 4 10:26:55    ntpd[1131]: adjusting local clock by -33.061540s
Oct 4 10:23:35    ntpd[1131]: adjusting local clock by -33.993178s
Oct 4 10:20:19    ntpd[1131]: adjusting local clock by -35.136921s
Oct 4 10:16:09    ntpd[1131]: adjusting local clock by -36.758732s
Oct 4 10:13:20    ntpd[1131]: adjusting local clock by -37.223784s
Oct 4 10:09:43    ntpd[1131]: adjusting local clock by -38.490783s
Oct 4 10:06:01    ntpd[1131]: adjusting local clock by -39.261836s
Oct 4 10:02:20    ntpd[1131]: adjusting local clock by -40.538240s
Oct 4 09:59:36    ntpd[1131]: adjusting local clock by -41.759971s
Oct 4 09:56:23    ntpd[1131]: adjusting local clock by -42.565387s
Oct 4 09:53:21    ntpd[1131]: adjusting local clock by -43.679063s
Oct 4 09:51:02    ntpd[1131]: adjusting local clock by -44.550676s
Oct 4 09:47:26    ntpd[1131]: adjusting local clock by -45.461797s
Oct 4 09:43:49    ntpd[1131]: adjusting local clock by -46.222141s
Oct 4 09:40:23    ntpd[1131]: adjusting local clock by -47.694072s
Oct 4 09:37:06    ntpd[1131]: adjusting local clock by -48.746400s
Oct 4 09:33:21    ntpd[1131]: adjusting local clock by -50.021202s
Oct 4 09:29:47    ntpd[1131]: adjusting local clock by -51.066253s
Oct 4 09:26:01    ntpd[1131]: adjusting local clock by -51.894315s
Oct 4 09:21:42    ntpd[1131]: adjusting local clock by -53.156179s
Oct 4 09:17:58    ntpd[1131]: adjusting local clock by -54.381976s
Oct 4 09:14:04    ntpd[1131]: adjusting local clock by -55.422368s
Oct 4 09:12:26    ntpd[1131]: adjusting local clock by -56.479535s
Oct 4 09:09:18    ntpd[1131]: adjusting local clock by -57.207745s
Oct 4 09:06:48    ntpd[1131]: adjusting local clock by -57.557736s

Offline sullrich

  • Hero Member
  • *****
  • Posts: 5110
  • Karma: +3/-0
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #5 on: October 04, 2006, 02:01:40 pm »
This is normal.  Your machines REAL TIME CLOCK is being adjusted.  The amount of times that it is doing this tells me your motherboards time keeping is crap, and it is fixing this.

Offline energy

  • Jr. Member
  • **
  • Posts: 40
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #6 on: October 06, 2006, 02:14:30 am »
This is normal.  Your machines REAL TIME CLOCK is being adjusted.  The amount of times that it is doing this tells me your motherboards time keeping is crap, and it is fixing this.

You say its normal but it still cant fix it cause its allways trying to fix it.

Offline hoba

  • Administrator
  • Hero Member
  • *****
  • Posts: 5837
  • Karma: +3/-0
  • What was the problem to this solution again?
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #7 on: October 06, 2006, 02:54:22 am »
It's not always trying to fix it DOES fix it and keeps your broken clock accurate or at least it tries to do it's best. With the latest RC3 update these messages are in their own systemlogstab to not "spam" the main tab in kind your clock is really that broken.

Offline enCecity

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #8 on: October 06, 2006, 07:29:26 am »
me running on wrap from pcengines.ch

important note from doc http://www.pcengines.ch/wrap1c.pdf:
WRAP does not include a battery backup for the real-time clock (RTC).

Offline hoba

  • Administrator
  • Hero Member
  • *****
  • Posts: 5837
  • Karma: +3/-0
  • What was the problem to this solution again?
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #9 on: October 06, 2006, 07:46:22 am »
me running on wrap from pcengines.ch

important note from doc http://www.pcengines.ch/wrap1c.pdf:
WRAP does not include a battery backup for the real-time clock (RTC).

That's no problem as it will do a timesync as soon as the specified timeserver is reachable right after bootup.

Offline enCecity

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #10 on: October 06, 2006, 11:39:26 am »
does this thread provide a solution to our problem?
http://forum.openwrt.org/viewtopic.php?pid=20909

Offline enCecity

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #11 on: October 06, 2006, 12:18:19 pm »
never mind, consider it as done.
only point left: adjust txt on syslog to 'Last 50 OpenNTPD log entries'

Offline sullrich

  • Hero Member
  • *****
  • Posts: 5110
  • Karma: +3/-0
    • View Profile
    • pfSense
Re: wierd bug: MULTIPLE:SINGLE?
« Reply #12 on: October 06, 2006, 06:59:03 pm »
Already fixed in cvs.  Thanks.