PittiGi
Occasional Visitor
....I tried, but without successMayrbe try an IP address rather than an URL?
It shouldn’t matter, but.........
....I tried, but without successMayrbe try an IP address rather than an URL?
It shouldn’t matter, but.........
....I tried, but without success
ntp: Start NTP update
Ok, will check. but first I have to reflash the firmware, because I went back to 384.5 which works flawlessAre you using the default NTP server (pool.ntp.org)?
Can you check syslog for any errors after the line showing
Code:ntp: Start NTP update
If 384.5 works fine for you, you might as well wait for 384.7 stable. Updating again to an alpha build solely to check syslog for a possible NTP error might be a bit excessive (unless your really eager to try 384.7 alpha builds of course)Ok, will check. but first I have to reflash the firmware, because I went back to 384.5 which works flawless
Too late, oops I did itIf 384.5 works fine for you, you might as well wait for 384.7 stable. Updating again to an alpha build solely to check syslog for a possible NTP error might be a bit excessive (unless your really eager to try 384.7 alpha builds of course)
Too late, oops I did it
This time I installed clean again, but set up the router in mediabridge-mode just to see if it shows the same problem, and yes it did
I used serveral different time server adresses.
This is the interesting part of the log after NTP update:
Feb 14 01:00:27 ntp: start NTP update
Feb 14 01:00:42 ntp: start NTP update
Feb 14 01:00:57 qtn: bootcfg.tgz exists
Feb 14 01:00:57 ntp: start NTP update
Aug 30 05:32:55 rc_service: ntp 210:notify_rc restart_diskmon
Aug 30 05:32:55 disk_monitor: Finish
Aug 30 05:32:56 disk_monitor: be idle
Aug 30 05:33:51 crond[265]: time disparity of 809492 minutes detected
May 5 07:04:59 syslogd started: BusyBox v1.25.1
May 5 07:04:59 kernel: klogd started: BusyBox v1.25.1 (2018-08-26 12:12:53 EDT)
May 5 07:04:59 kernel: Linux version 2.6.36.4brcmarm (merlin@ubuntu-dev) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Sun Aug 26 12:22:40 EDT 2018
I saved the whole log, if interested in, I would upload it
German timezone. But normally there´s no reason for changing the timezone, as you have already pointed out. This strange behaviour of the router is also reproduceable in original firmware. So, wait and see, thanks for your interest, will flashing back to 384.5Looking at it, it seems to fail the first two times, probably WAN isn't up yet, but after the third try it does sync correctly (at least the date, I don't know which timezone you're in/you've set). After that it falls back to May 5th... I don't have a clue what's going on. If I'm correct, you can leave it at pool.ntp.org, it should automatically direct you to one of the closest NTP servers in the offical pool, so there shouldn't be a need to change it.
Me too, on a 5300...I did a "dirty" flash from 384.6 with not a single problem. I am currently on 384.7 alpha2. All were done "dirty"
May 5 07:05:10 lldpd[578]: minimal kernel version required is 2.6.39, got 2.6.36.4brcmarm
May 5 07:05:10 lldpd[578]: lldpd may be unable to detect bonds and bridges correctly
May 5 07:05:10 lldpd[578]: consider recompiling with --enable-oldies option
Ok got it.lldpd is only used by AiMesh, and it seems that doesn't prevent it from working properly on stock firmware, so I would just ignore that message. Lldpd isn't used by my firmware, it's just a leftover.
Any update on AC3200 GPL status?
Any update on AC3200 GPL status?
What am I suppose to see? Is there something in particular I am looking for?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!