V3 Changelog

Change Log V-1.1.12 Build 2063

• StarV3 Common Changes
  • Introduction of 3 new platforms:
    • MIPS-COMPEX (WAR-1 platform)
    • XSCALE-METRO (WAR-4 METRO platform)
    • XSCALE-WDR800 (WAR-4 WDR800 platform)
  • StarV3 has undergone a subsystem rewrite, to increase scalability between small CPE device and robust enterprise class platforms.
  • Quagga has been back-ported to 0.99.5 due to reported issues with RIP and OSPF.
  • Many bug fixes, large and small (far to many to list)

WAR-1 Platform:

The initial shipment of WAR-1 systems contain a pre-release version for 1.1.12. Please update to this release, if needed. (LED support as listed below is only available in build 2063 or newer)

The WAR-1 contains two ethernet ports, which act as a small 2-port switch. The software will use these two ports as a single interface.

LED lights: (Blue power light = LED 1, LAN1 = LED 5, LAN2 = LED 6)

LED 2: Status / Diagnostic light

This will blink quickly during bootup, then settle to a constant one second 'heartbeat' blink once every second.

Updating the flash (such as saving settings, or doing firmware updates) will cause the LED to blink rapidly.

This LED is also used with the button (see below)

LED 3: VDS Status light

This will turn on when a VDS tunnel has been successfully created, otherwise it is off.

LED 4: Atheros signal level indicator

This will flash to indicate current signal level of the client connection. Solid light indicates a signal of -67dbm or lower, and if the light is off, it the client is not associated.

Button:

While pressed, LED 2 will turn off for roughly one second. If you release the button in this timeframe, the CPE will be rebooted.

If you continue to hold the button, LED 2 will start flashing, slowly at first but will quickly gain pace. Once it reaches a solid state (roughly 10 seconds), the system will reboot, and restore to factory settings (including generating new SSH keys).

If you release the button after the LED starts blinking, but before it turns solid, the system will perform no actions. (will not reboot, or perform a factory restore).

Feature set:

The WAR-1 contains the following feature set:

• Full Atheros capabilities, including AP mode, Cloaking and long distance.
• Full Firewall, CBQ and NAT support.
• Static routing, RIPv1/2 and Policy Routing.
• 802.1b bridging, and WDS for client-mode Atheros.
• DHCP client and server support.
• VDS support (minus link encryption).
• 802.1q vlan support
• Uses the familliar SSH interface.
• And other items such as NTP, syslog, static ARP, ping watchdog, etc.

• Caveats
  • During an activate, all Atheros cards will be reset even if their settings were not modified. This has been resolved for the next release.
  • please read past release notes.

Change Log V-1.1.11 Build 1741

• StarV3 Common Changes
  • Net-SNMP has been updated to v5.4
  • Quagga has been updated to v0.99.6
  • SNMP is now disabled by default with new StarV3 installs.
  • Watchdog has been added to restart MaraDNS if it quits.
  • Several small updates and fixes.

• Caveats
  • please read past release notes.

Change Log V-1.1.10 Build 1734

• StarV3 Common Changes
  • Resolved an issue with VDS that could cause your SSH session to terminate after creating a new VDS profile.
  • maradns has been updated to v1.2.12.04
  • quagga has been updated to v0.99.5
  • uploading configuration from one platform (X86->XSCALE, and vice virsa) would sometimes fail.
  • If a dhcp client is running on an Atheros card, the lease will be renewed each time the Atheros card reconnects to an AP.
  • Several other general updates and fixes.
  • Starutil client has been updated to support a -p parameter to override the port number it connects too. This allows site administrators to set up a series of port forward rules to access internal systems via Starutil.
  • Starutil client has been updated to support interactive passwords. If you do not provide a password on the command-line, you will be prompted for one.

• X86-PC Specific Changes
  • DNS server now uses ISC bind v9.3.2-P1 in place of maradns.

• XSCALE-WAR Specific Changes
  • avila-starv3.pdf has been updated to provide a missing step for installing StarV3 on a Gateworks Avila GW2348 system.
  • redboot_RAM.srec has been updated to better support the Avila GW2348 hardware, which is needed during the StarV3 install process.
  • jtag instructions and s19-based firmware is now included with the release.

• Caveats
  • please read past release notes.

Change Log V-1.1.9 Build 1713

• StarV3 Common Changes
  • Resolved a problem that was introduced in 1.1.6 that quoted PPPoE "Access Concentrator" and "Service Name" parameters. This problem also has the rare chance of rendering a system unable to bootup properly, even if PPPoE services are not used. It is highly recommended to upgrade your 1.1.6 - 1.1.8 systems to 1.1.9, or downgrade to 1.1.4 to resolve the problem.

VDS has been updated to support group (multiple) connections per interface, and automatic CBQ shaping per instance. Fixed VDS issue where it could lose it's IP address after an activate changes.

• Caveats
  • VDS groups allow multiple connections per VDS interface, however there is no method to see which systems are connected outside of looking in the system log for connect / disconnect messages.

please read past release notes.

Change Log V-1.1.8 Build 1704

• StarV3 Common Changes
  • Added support for "ip" and "iptables" commands under the command prompt. (power users)

• X86-PC Specific Changes
  • Added support for the Realtek 8169 PCI Gigabit cards.

• XSCALE-WAR Specific Changes
  • Added support for installing on stock Gateworks Avila GW2348 series of hardware. Read starv3-avila.pdf for instructions (provided with firmware download). Licenses can be obtained from the www.license-keys.com website much like the X86 releases.

• Caveats
  • PPPoE "Access Concentrator" and "Service Name" entries will get a pair of quotes whenever you start a new SSH session, and will remain there if you save your configuration without first removing them. This will be resolved in the upcoming 1.1.9 release. (problem occurs in v1.1.6-v1.1.8). Please read past release notes.

Copyright (c) 2006, Valemount Networks Corporation, reproduced with permission.