To beta or not to beta - that is the question... Currently there are two versions on FreeNATS doing the rounds; the "current" (v0) and the "future" (v1). Most people are running the recommended current v0 system and so consequently this is the version that the most effort on quick-bug-fixes goes into, it also doesn't get new danger-code added to it and stays pretty static.

All good.

But... v1 is actually nothing more than a genetically-enhanced Frankenstein 0.04.2x-vintage package with appendages crudely bolted on. It's rotten heart therefore continues to have the same defects as v0 but now additionally wrapped and disguised amongst the extra frilly bits.

So... every v0 bug fix also means remembering to fix the same bug in v1 (and in at least one instance vice-versa) except a one line change on line 272 in v0 is often a four-line headache at line 389 in v1.

So... I really want to consolidate everyone onto v1 and concentrate on a single version

But... although v1's core functionality is pretty solid at least for the same type of server-based testing v0 supported the newer functionality may be a different story once it's exposed to the bizarre range of Unicies and Uniclone OSs that FreeNATTERS seem to use.

So... as the man said "the times, they are a changing". I feel the dangerous take-no-prisoners step of releasing v1 as a beta and the recommended version (as well as the VM version) could be just a few nervous sweaty keystrokes away at any moment.

You will of course be able to stick to v0 if you're a "a'int broke why fix it" type and I will continue to offer my lacklustre best-endeavour get-what-you-pay for support levels but the focus would switch to v1.

Yeah I just fear for users being baffled or having working monitoring systems broken but... you're probably right.

In the meantime VM users are able to upgrade to v1 but the automated script won't do it so it's a bit more intensive. You need to visit the download page to find the latest version number/filename and then follow these instructions to download it.

I think I just hate building VM images. They take an age to upload via my broadband and then I'll always have forgotten some tiny thing and so have to do it all over again. It's the main reason the VM is always so out of date, I only rebuild it for major releases.

The solution would be of course to make my distribution server capable of running VM images and I could make changes live... I just don't see this being an easy sell from a security/performance point of view (even to myself).

Don't get me wrong though - I think virtualisation in general and the VMWare products in specific are simply fantastic, it's just the sitting around waiting for it to upload before the stinging realisation I'd forgotten to put a 1 somewhere.

Soon though... v1 goes mainstream and I will build a shiny new v1-pre-installed VM. As soon as I crack, which won't be long.

On a seperate note I have just noticed you're earlier request for backup/restore functionality. Well... in v1 you have it. Backing up data (historic records and logs) is not so sharp as the script keeps timing out but for config (what is selected by default in the tool) it works quite well. In testing I backed up, restored and migrated configuration from one system to the other.

Thanks for your suggestion - I'd totally forgotten to credit you for that one.