PDA

View Full Version : StarV3 1.0.0 build 663 (WAR Edition) is ready for testing


tony
02-20-2006, 05:38 PM
The new release is on-line and ready for public testing. Please download it from the www.star-os.com/starvx (http://www.star-os.com/starvx) website.

There are release notes in the firmware archive which will list the steps needed to upgrade.

Most settings are preserved during the upgrade. For the list of ones that are not, please refer to the release notes.

Any and all comments are welcome.

Some common Q&A answers regarding the new release:
Q: Is cloaking supported in this BETA?
A: No, cloaking will be available once the new atheros configuration dialog is completed. Ensure your system does not use cloaking before you upgrade, or wait until this feature is available.

Q: What kind of performance should we expect?
A: If you disable connection tracking, the performance while routed should be roughly the same, if not better than a bridged StarVX system.

Q: Does this beta contain WEP?
A: No, the first release does not as we are currently investigating some StarVX / StarOS WEP incompatibilities that have recently been reported.

Q: What interface will StarV3 use?
A: It will use SSH, much like StarOS. The current interface borrows much from StarOS, but enhanced for the WAR platform.

Q: Will the same StarVX atheros features be present in StarV3 beta?
A: Most of the basic settings are present, however once we complete the new Atheros configuration dialog, the rest will follow.

Q: Will there be firewall support?
A: Yes, firewall, NAT and CBQ are all available in this release.

Q: Is there WDS support?
A: The first BETA does not have WDS support, so you need to convert your StarVX network to a routed design before upgrading, or wait until this feature is available.

Q: Is there any way to secure a wireless connection in the first BETA?
A: Yes, we have included VDS support which supports AES encryption and can be used to secure your connection, or act as a WDS alternative.

Q: Will there be tcpdump, or some other way to see system traffic?
A: Yes, we have included beacon, a real-time traffic monitor which can be used to see the active connections in your system.

Q: Will the system be field upgradeable?
A: Quite definitely, the system is fully field upgradable.

Please feel free to post any additional questions you may have.

lonnie
02-20-2006, 06:46 PM
I have had one report of the unit requiring a power cycle to get a reboot after upgrading. Please be prepared for that. We have not seen it, but it is better to be ready to have someone ready to power cycle the unit than to scramble if it does not reboot properly.

Bossman
02-20-2006, 07:00 PM
A few other things that are not carried over...

Wireless settings:
- Country reverts to Unspecified
- Antennas switch to diversity
- Distance goes to 30 miles

I should have read the Forum before upgrading.... I had everything set up for cloaking and upgraded one box (on the bench of course). The lack of cloaking is not in the readme... maybe it should be.

Don't panic on re-boot after the flash to the beta... it takes 2 -3 times longer than the old reboots.

Question:

Is RIP2 set up like the Star-VX & the Windows gui where you turn it on and it works, or do we have to go into the config and turn it on like we did in Star-OS?

-----
Looks good. If I can make my two +15 mile links with these boxes I'll have these running this week. :)

Speeds on the bench are impressive... 20 Mbps in regular G mode. 30+ Mbps with all the toys turned on and the connection tracking off on the AP side.

I'll miss the windows GUI, but I'll live. ;)

Arthur

tony
02-20-2006, 08:09 PM
Thank you for the update.

The first boot will take a little longer, as it has to generate SSH keys. Each subsequent reboot will be quicker.

I have updated the website changelog with mention of the cloaking and country code options. The country code should have been carried over, and will be corrected in the next release.

The rip and ospf options work much like they do in StarOS, and are enabled via the advanced routing menu.

Thanks again for the feedback.

ianek
02-21-2006, 05:13 AM
Hello,
please can you add ping-watchdog to the release ? I think it is very needed option.

Ian

lonnie
02-21-2006, 05:59 AM
It is on the list. How did the conversion go?

billr
02-21-2006, 09:12 AM
Q: What interface will StarV3 use?
A: It will use SSH, much like StarOS. The current interface borrows much from StarOS, but enhanced for the WAR platform.

------------------------------------------------------------------------

A slightly silly question but best to ask first then upgrade.
Based on the above I assume we use (say) PuTTY to get into the new upgraded WAR units, as opposed to the apConfig program - or am I misunderstanding you?

Cheers and thanks for all the work..

------------------------------------------------------------------------
OK I have downloaded it, and RTFM...
The readme says it all.
Use the supplied PuTTY !

kbldawg
02-21-2006, 09:56 AM
My upgrade went pretty good. Some thing I found while upgrading...

1.) Upgrade Instructions refer to the wrong step-up release...

" Using apConfig, upgrade your WAR system to the latest step-up release 1.0.7 (vncOs-1.0.7-2914.rom) which will allow you to continue with the upgrade procedure. "

(vncOs-1.0.7-2914.rom) should be (vncOs-1.0.7-2916.rom)

Not a big deal, just thought I'd let you know.

2.) Since this board was still in it's default settings, I can't report anything on setting preservation.

3.) I confirm that it did take a lot longer on the initial reboot from VX to V3. I waited about 5 minutes, after that I powered cycled it and it came back up, eventually. As Tony reported, any reboot following the intial upgrade was back to normal speed.

Great job Valemount!! Thank You!!!!

--
Chad

billr
02-21-2006, 10:20 AM
Thanks for the information, we will have to bite the bullet in the next week or two ;-))