Ack. I have a copy of V1.00(AAJZ.14)C0.bin for my VMG1312-B10A but I am reluctant to update the firmware at present.

(My VMG1312-B10D has had a serious "funny-fit" and is currently opened up, awaiting for the moment to be ripe when I connect to the serial port header pins on the PCB in an attempt to recover it. As a consequence, I am currently using my backup VMG1312-B10A.)

Sorry to hear your B10D has had a funny-fit. I have done my main in use B10A and two spares without problem to V14. All seem to be running fine although only tested the spares for a couple of minutes but main B10A has been up for 4 hours 50 minutes without problem.

Sorry to hear your B10D has had a funny-fit. I have done my main in use B10A and two spares without problem to V14. All seem to be running fine although only tested the spares for a couple of minutes but main B10A has been up for 4 hours 50 minutes without problem.

Contemplating updating my VMG1312-B10A to latest firmware, V.14, I'am still running V.12, question, am I likely to loose my supervisor PW with the FW update, I bought my router S/H from a forum member and had to obtain the supervisor PW by using the stat's file dump and examination method as described on the forum, if I need to repeat this procedure is it likely to still work ?

Should I perform a fresh configuration backup before FW update and restore after ?

Do I need to do anything with the ROM-D setup having already "cleaned" & "saved" on my present configuration.

Contemplating updating my VMG1312-B10A to latest firmware, V.14, I'am still running V.12, question, am I likely to loose my supervisor PW with the FW update, I bought my router S/H from a forum member and had to obtain the supervisor PW by using the stat's file dump and examination method as described on the forum, if I need to repeat this procedure is it likely to still work ?

Should I perform a fresh configuration backup before FW update and restore after ?

Do I need to do anything with the ROM-D setup having already "cleaned" & "saved" on my present configuration.

My supervisor password stayed the same as I was able to login from a script with same password. Always worth backing up configuration before firmware upgrade. ROM-D should not need any attention if already cleared.

Well, that's the 1312-B10A's firmware updated from V.12 to the current V.14, all very painless without any requirement to restore any of my parameters (Wi-Fi MAC filters, static I/P address listings etc.) also glad to note that my "supervisor" login password did not change.

Absolutely no change in line connection speeds, SNRM, interleaving, INP etc., probably to be expected in my case as I'am currently imposing modem synch limits as a noise limiting experiment.

However, I did experience a very strange bi-product with my WD "My Cloud" NAS drive which is connected to a router LAN port, this refused to connect after the router re-boot, my normal desktop link to the NAS actually brought up the router GUI login page !!The static I/P address on the NAS had for some reason changed ?

After quite a bit of messing about and finally performing a NAS reset, managed to get everything back to the original configuration with original, static I/P address, no data loss experienced on the NAS.Previous router re-boots have never caused any NAS access issues so can only attribute this incident to the F/W upgrade process strange as it may seem.

Next time, will shut down the NAS before performing any router F/W updates.

Well, that's the 1312-B10A's firmware updated from V.12 to the current V.14, all very painless without any requirement to restore any of my parameters (Wi-Fi MAC filters, static I/P address listings etc.) also glad to note that my "supervisor" login password did not change.

Having read of your success, I shall have to find the time to update my VMG1312-B10A's firmware from the current V1.00(AAJZ.13)C0 to V1.00(AAJZ.14)C0.

Yes, it was surprisingly painless, a pleasant anti-climax apart from the strange occurance with my WD NAS, really can't explain that, still, no harm done and no data loss, will certainly shut the NAS down first for future F/W updates.

. . . the strange occurance with my WD NAS, really can't explain that, still, no harm done and no data loss, will certainly shut the NAS down first for future F/W updates.

I wonder . . . I guess you have a DNCP server on your LAN and you probably also make use of UPnP ? Both functions could, if the timing was right, combine to cause confusion when LAN devices are in receipt dynamically assigned IP addresses.

Every device on my LAN has its own static address, including the wireless devices, and so I do not have a DHCP server active. Even so, at modem/router firmware update time I always --