ntp issue again with 1.0.3.4

[linksysinfo]

ok i just upgraded to 1.0.3.4 however my custom ntp server settings changed from

uk.pool.ntp.org

to

uk.pool.config.ntp.org

upon reboot.

[ddiep]

Thanks Simon! This is just .... embarassing . Although this is a beta version but we'll fix this and come up w/ another fw release.

[Te-Kai Liu]

Simon,

I wonder if the Web GUI will allow you to reconfigure the Cutom NTP Server to the correct value, and if the correct value will stick after another reboot? Basically I am trying to determine if the issue has a valid workaround.

Thanks.

[ddiep]

Tekai, We'd tried this in the lab. After corrected the value, it'll change again after every reboot.

[linksysinfo]

Oh that's not good!

Sent from Cisco Technical Support iPad App

[linksysinfo]

Tekai, I changed it back but have not rebooted so far. I will do this sometime this morning from work. The only reason I noticed was the date/time in the logs again start to log at jan 01.

I had Bonjour enabled but Bonjour entries still insist on reporting Jan 01 in the default log even though date is correct. I disabled bonjour and still bonjour logs entries????

Btw I have set my default log to report everything possible so that I can see what is failing etc. If you guys need a copy of my config again let me know.

Sent from Cisco Technical Support iPad App

[linksysinfo]

is there any update on the ntp issue? possibly a fix? this is so annoying that it re-adds the ".config." to the ntp host name on reboot.

[ddiep]

For this issue, we 're actively working on it. Dev team indicated that this only happen to your specific ntp server name of "uk.pool.ntp.org". If possible, please try w/ another ntp server (*temporary* until we came out w/ another fw).

[linksysinfo]

i picked another UK ntp server

uk.ntp.f-box.org

oh and guess what!

uk.config.ntp.f-box.org after a reboot! lol

[ddiep]

LOL! You've done enough damage for today. I think you deserve to go to bed. Sweet dream!

[ddiep]

Simon,

I was told that you will see this problem occurred when configured ntp server that named with "ntp" characters included. So please try again w/ another ntp server that excluded "ntp".

Don

[linksysinfo]

lol you can't have an ntp server name with ntp in it? Someone's pulling your leg. Guess we better change about 90% of ntp server names then to fix that issue

Sent from Cisco Technical Support iPad App