StarV3 v1.3.1 build 2567 has been released.

[tony]

The new release is available for download from files.star-os.com.

NOTE: There is a configuration error on the Atheros dialog that shifts the meaning of the checkbox groups up by one. The Enhanced ANI checkbox actually controls "Hide SSID", and the SuperA/G checkbox actually controls the "Enhanced ANI" option, etc.

There is a new release planned for early next week that will address this.

Changes since v1.3.0 build 2446
*) WP188A 4-port platform is now fully supported (XSCALE-WP188)
*) Added Atheros 802.11 full-duplex support (makes use of two cards).
*) Added a 'Fixed' checkbox that will allow the use of a fixed rate, rather than a max rate.
*) Added an 'Enhanced ANI' checkbox (client use only).
*) Much improved support for 802.11b clients.
*) Turbo mode should now work properly.
*) Cloaked clients will now scan all supported channels. Previously, they skipped turbo channels.
*) The Custom Scan list (Channel ACL) is now supported when operating as an Access Point.
*) 802.11H (DFS) now honors channel ACLs when switching to a new channel due to radar detection.
*) WPA/RSN now supports Compression with CCMP (AES) ciphers.
*) Atheros Radius ACL would disconnect all clients after 5 minutes, even if configured not to.
*) Static routes with Atheros APs in WPA mode are no longer cleared on activate.
*) Site Survey will now show essids with spaces.
*) Added a refresh button to the Site Survey, and other report based dialogs.
*) Fixed an issue where some clients would display odd rates in the association window.
*) Firewall and NAT are now processed before the network is brought up, as to avoid connections being established before NAT is in place.
*) SNMP memory leak in the 802.11 mib has been corrected.
*) starutil -a now activates the system changes properly, including DHCP.
*) TLS and Association List menu items no longer share a common hot key.

Problems found in this release include
*) Association window will still sometimes show odd rates.. Investigation is afoot.

NOTE: The X86-WRAP edition is fully compatible with the Geode-based RB220 & RB230.

Full Duplex setup example
To make use of a Full Duplex PtP connection, follow these simple steps:

• System A
  • wpci1:
    • FD Role: FD-TX
    • FD Grp#: 1
    • Network Type: Station
    • Essid: A
  • wpci2:
    • FD Role: FD-RX
    • FD Grp#: 1
    • Network Type: Access Point
    • Essid: B
• System B
  • wpci1:
    • FD Role: FD-RX
    • FD Grp#: 1
    • Network Type: Access Point
    • Essid: A
  • wpci2:
    • FD Role: FD-TX
    • FD Grp#: 1
    • Network Type: Station
    • Essid: B

After that is complete, add an IP to one of the Atheros interfaces (wpci1 or wpci2, doesn't matter), and you will now be able to ping between the two systems.

You can also secure your connection by enabling WPA or WEP, and using ACLs.

The Full Duplex device to monitor via SNMP, and configure via iptables is wfd0.

[ripv]

OMG - you guys must have been working your fingers to the bone designing and coding over the last few weeks !
Congratulations on the update which could easily be considered a new version, given the feature list
and I thought you were flat out giving us all support on the forums

[tony]

It is a lengthy list indeed, and hopefully will resolve many issues people have had in the past. (and undoubtedly, introduce a few new ones too)

[go.fast]

What is :

*) Added an 'Enhanced ANI' checkbox (client use only).

[tony]

Adaptive Noise Immunity - If your client is operating poorly, try this option and see if things improve.

In general, this option is disabled unless needed.

[go.fast]

I just did 3 of my pops that have less than a dozen subs with mixed wars and generic B clients. (TT EZ Bridges)

I just noticed that on one of my pops the tx and rx rates fluctuate to unseen of before rates. 26.5, 51.55, 42.5, 31.5

Is this expected?

[tony]

Are you using the new release on the system exhibiting the funny rates?

[go.fast]

Yes 1.3.1 on a war2

[tony]

Can you PM me login instructions?

[Stratolinks]

I just upgraded 24 WRAPs, 2 WAR4 Metros, 1 War4, 1 WAR2. (All our active POPs). Correction, tried upograding. Had to downgrade them all again. Detais follow...

Just a few minutes after finishing we started getting calls. When I started reconnecting to some of the POPs, most didn't have much more than half the customers connecting. One that I took closer notice of, a WAR1 client had been associated at -68 with 1.3.0, after the upgrade it was coming in at -90 under 1.3.1, and when I downgraded back to 1.3.0 it was back at -68 again. Two sites that are cloaked G only only had half the clients connecting, but all them came right back after downgrading.

I will have to do a little more comparative testing in the wee hours some night to narrow this down much further, but it certainly looks like there might be a wee bit if an issue there.

I put this on 2 of our backhaul units X-86 PC with 5GHz only and they seemed to be working just fine.

Just a bit of heads up to anyone else before they deploy this one. Do a bit of testing on a site or two before you go pour it out onto the entire network.

Edit: Even when the one WAR1 client was coming in at -90, some of the old Hermes and Realtek clients were connecting at their normal signal levels while others were not even there. There wasn't any particular pattern to who was not connecting. Some that were nearby and normally have very good signals were not associating, while others that are a distance away and have much lower signal levels (-78) were connecting fine.