VM201 ignoring NTP setting

Modules VM201
1

I seem to have found a bug in the VM201 firmware. It does not matter what you put in the NTP server field of the web GUI, the VM201 still uses pool.ntp.org.

This creates a problem for us, as the planned location for the VM201 does not have Internet access. However there is an internal NTP server the rest of the location uses.

The About-page of the VM201 says:
Build: 1236
Build date: Sep 07 2012 08:56:42
TCPIP Stack: v5.42

Packet dump from gateway
VM201 has 10.0.99.60, Internal NTP server has 192.176.6.138.

Standard setting: pool.ntp.org
1: 15:12:43.374721 802.1Q vlan#1 P0 10.0.99.60.4664 > 130.236.254.17.123: udp 48
Changed to internal NTP server by name. Save, reboot.
2: 15:22:43.849260 802.1Q vlan#1 P0 10.0.99.60.4666 > 46.253.203.104.123: udp 48
Changed to internal NTP server by IP address. Save, reboot.
3: 15:32:44.628950 802.1Q vlan#1 P0 10.0.99.60.4668 > 130.236.254.102.123: udp 48
4: 15:40:47.470327 802.1Q vlan#1 P0 10.0.99.60.4096 > 194.71.144.71.123: udp 48
5: 15:50:47.522586 802.1Q vlan#1 P0 10.0.99.60.4098 > 130.236.254.17.123: udp 48
6: 16:00:48.148918 802.1Q vlan#1 P0 10.0.99.60.4100 > 89.107.213.125.123: udp 48
7: 16:10:48.933453 802.1Q vlan#1 P0 10.0.99.60.4102 > 89.107.213.125.123: udp 48
8: 16:20:49.408975 802.1Q vlan#1 P0 10.0.99.60.4104 > 94.254.34.221.123: udp 48
9: 16:30:50.037824 802.1Q vlan#1 P0 10.0.99.60.4106 > 193.228.143.13.123: udp 48
10: 16:40:50.824282 802.1Q vlan#1 P0 10.0.99.60.4108 > 193.228.143.13.123: udp 48
11: 16:50:51.301543 802.1Q vlan#1 P0 10.0.99.60.4110 > 83.177.160.188.123: udp 48
12: 17:00:51.925077 802.1Q vlan#1 P0 10.0.99.60.4112 > 89.107.213.125.123: udp 48
13: 17:10:52.707223 802.1Q vlan#1 P0 10.0.99.60.4114 > 193.228.143.13.123: udp 48
14: 17:20:53.182317 802.1Q vlan#1 P0 10.0.99.60.4116 > 213.100.93.246.123: udp 48
15: 17:30:53.811420 802.1Q vlan#1 P0 10.0.99.60.4118 > 94.254.34.221.123: udp 48
16: 17:40:54.598205 802.1Q vlan#1 P0 10.0.99.60.4120 > 193.228.143.13.123: udp 48
17: 17:50:55.069927 802.1Q vlan#1 P0 10.0.99.60.4122 > 194.71.144.71.123: udp 48
18: 18:00:55.699167 802.1Q vlan#1 P0 10.0.99.60.4124 > 193.228.143.13.123: udp 48
19: 18:10:56.483617 802.1Q vlan#1 P0 10.0.99.60.4126 > 130.236.254.17.123: udp 48
20: 18:20:56.956798 802.1Q vlan#1 P0 10.0.99.60.4128 > 193.228.143.12.123: udp 48
21: 18:30:57.585220 802.1Q vlan#1 P0 10.0.99.60.4130 > 193.228.143.12.123: udp 48
22: 18:40:58.369686 802.1Q vlan#1 P0 10.0.99.60.4132 > 81.234.134.160.123: udp 48
23: 18:50:59.001693 802.1Q vlan#1 P0 10.0.99.60.4134 > 194.71.144.71.123: udp 48
24: 19:00:59.475439 802.1Q vlan#1 P0 10.0.99.60.4136 > 46.253.203.104.123: udp 48

2

Please allow us some time to look into this.
We’ll post a reply once we have sorted this out.

3

Thank you for the reply.

I have upgraded the firmware to version 1315 as instucted in viewtopic.php?f=37&t=9923

But I still see the same behaviour. The internal NTP server is still in the NTP server field.

Regards.

102 packets captured
1: 15:19:29.689585 802.1Q vlan#1 P0 10.0.99.60.4096 > 91.231.153.3.123: udp 48
2: 15:29:30.005950 802.1Q vlan#1 P0 10.0.99.60.4098 > 193.228.143.13.123: udp 48
3: 15:39:30.991113 802.1Q vlan#1 P0 10.0.99.60.4100 > 130.236.254.102.123: udp 48
4: 15:49:31.621992 802.1Q vlan#1 P0 10.0.99.60.4102 > 81.234.134.160.123: udp 48
5: 15:59:32.361141 802.1Q vlan#1 P0 10.0.99.60.4104 > 130.236.254.17.123: udp 48
6: 16:09:33.195302 802.1Q vlan#1 P0 10.0.99.60.4106 > 194.71.144.71.123: udp 48
7: 16:19:33.973460 802.1Q vlan#1 P0 10.0.99.60.4108 > 46.253.203.104.123: udp 48
8: 16:29:34.720421 802.1Q vlan#1 P0 10.0.99.60.4110 > 94.247.173.154.123: udp 48
9: 16:39:35.547579 802.1Q vlan#1 P0 10.0.99.60.4112 > 130.236.254.17.123: udp 48
10: 16:49:36.402048 802.1Q vlan#1 P0 10.0.99.60.4114 > 193.228.143.13.123: udp 48
11: 16:59:37.074962 802.1Q vlan#1 P0 10.0.99.60.4116 > 130.236.254.17.123: udp 48
12: 17:09:37.900420 802.1Q vlan#1 P0 10.0.99.60.4118 > 193.228.143.12.123: udp 48
13: 17:19:38.691263 802.1Q vlan#1 P0 10.0.99.60.4120 > 46.253.203.104.123: udp 48
14: 17:29:39.432152 802.1Q vlan#1 P0 10.0.99.60.4122 > 194.71.144.71.123: udp 48
15: 17:39:40.262895 802.1Q vlan#1 P0 10.0.99.60.4124 > 46.253.203.104.123: udp 48

4

Our IT department is verifying this issue. We will let you know asap when we have an update or new firmware.

5

This bug is confirmed. The NTP server is always ntp.pool.org, no matter what you enter under settings. The VM201 wil receive updated firmware as soon as possible.

6

I’m struggling to fix the NTP issues but no result;
Is there a way to do it manually?

7

If you want to enter an NTP server other than ntp.pool.org, you will need to wait for the new firmware. This will probably be available in the coming days.

8

Thanks,
I’m waitting…

best Regards.

9

Good work! Looking forward to the updated firmware.

10

The NTP feature has been fixed; new firmware is available:
velleman.eu/downloads/files/ … ld1342.zip

Please update the same way you did before, but with this new bin file.

11

I have now updated to Build 1342, and the VM201 is now using the internal NTP server from the NTP server field!

I will monitor the connections from the VM201, and post an update tomorrow, but I see no reason to doubt the results.

Good work!

12

I’m sory but may be i miss the post describing how to update the VM201 with the new firmware.
Can you please remember me the steps to follow?
Please help.

Best Regards,
Justin.

13

Download the zip file and extract it. You should have a bin file.

Go to the Windows command prompt and upload the image with tftp:
tftp put “VM201Build1342.bin”

You may need to install tftp via the Add/Remove Windows Features

14

Thank you very very much!!!
I succed to upload the image with tftp.
This fix automaticaly the NTP issues.
Thaks a lot.

Best Regards,
Justin.

15

I can also confirm that the updated firmware fixes the NTP problems. The packet capture only shows requests to our internal NTP server.

Good work!

16

Hello,

Something went wrong during upgrade.
In commandprompt I received a timeout, after a while I went to the VM201 and on the display I could read: Bootloader Reset.
I removed the power and connected again and now the top row of the display if filled with black boxes…

17

“Bootloader Reset” indicates that the firmware is being overwritten. If you unplug the device while this is on screen, it will be aborted halfway.

Please try again, and if you do not succeed, return the device to us and we will reprogram it for you.

Velleman Repair Dpt.
Legen Heirweg 33
9890 Gavere
Belgium