View Full Version : StarV3 WAR Edition v1.0.2 build 1220 has been released.
The new release can be downloaded from the http://www.star-os.com/starv3 downloads page.
The X86 development is almost complete. Expect the X86 WRAP version to be available soon.
Looking at the release notes, looks nice. Moving along at a nice pace making things better and better. 1.0.1 (1115) has been pretty good, I've been pretty damn happy with my network full of WARs running 1115.
bminish
06-24-2006, 08:50 AM
The new release can be downloaded from the http://www.star-os.com/starv3 downloads page.
The X86 development is almost complete. Expect the X86 WRAP version to be available soon.
Just flashed a couple of boards and came across a few possible bugs
1/ Rate is reporting on my client end of an 802.11a link as 16 or 17 which equate to rates of 12 Mbs and 18Mbs respectively
I also saw an 802.11b link reporting with a rate of 10
2/ Bridging, there seems to be some weirdness in the area of bridging
I bridged a Wireless interface (in Client mode) to an ethernet interface but could not ping the client at the other end of the wireless link over the bridge. I was also unable to ping the other end of the Wireless link on it's same subnet, i had to remove the bridge before I could access the other end of the link on the interface subnet
config something like this
Client end
ether1 10.0.0.5/24 (BRIDGE 1)
wpci1 192.168.3.2/24 (BRIDGE 1)
AP end wpci1 192.168.3.1/24 and 10.0.0.6/24
I'll be testing OSPF in the coming days
.brendan
bminish
06-24-2006, 09:01 AM
One other bug?
the noise reports seem to be pessimistic and related to received strength
link1 5805 Mhz -65 noise -84
kink2 5180Mhz -75 noise -88
link3 2462Mhz -76 noise -81
links 1 and 2 are on channels that are completely clean, even adjacent channels are completely clean
Link 3 has some noise, the true noise floor on this link is about -90 the last time I measured it with a proper analyser
.brendan
I upgraded all my war units last evening. Some strange results with Compex WLM54G radios in AP's. One came back up after the flash with associations, no IP's and all N's in the one column. I rebooted and it cleared them. This morning, I looked and had 29 associations and all N's again, different AP. Got a call this morning from a client on a third AP with this radio, never hear from him, and said service was very slow. Rebooting seems to clear but it slowly seems to tarpit the clients. These are all with Compex WLM54G radios.
The new rates shown on the client represents the sliding-scale rate, and not the fixed 12, 24, 36, etc. This is a symptom of our new client-side rate handling, and will be changed in a future release.
Bridging has been fully tested in this release (using it right now). What does the AP show in the association screen? Are you showing up as a WDS connection?
Thanks!
Just flashed a couple of boards and came across a few possible bugs
1/ Rate is reporting on my client end of an 802.11a link as 16 or 17 which equate to rates of 12 Mbs and 18Mbs respectively
I also saw an 802.11b link reporting with a rate of 10
2/ Bridging, there seems to be some weirdness in the area of bridging
I bridged a Wireless interface (in Client mode) to an ethernet interface but could not ping the client at the other end of the wireless link over the bridge. I was also unable to ping the other end of the Wireless link on it's same subnet, i had to remove the bridge before I could access the other end of the link on the interface subnet
config something like this
Client end
ether1 10.0.0.5/24 (BRIDGE 1)
wpci1 192.168.3.2/24 (BRIDGE 1)
AP end wpci1 192.168.3.1/24 and 10.0.0.6/24
I'll be testing OSPF in the coming days
.brendan
Can you provide me a screen capture of one of your systems?
'N' readings are not uncommon, and will show up on occasion, especially if it's a heavily populated area. These can result from active scans, or other clients (not necessarily your customers) trying to roam to your AP, but having the wrong WEP, or security status.
In the future, we will be adding an option to filter out the 'N' associations, as to prevent confusion.
I upgraded all my war units last evening. Some strange results with Compex WLM54G radios in AP's. One came back up after the flash with associations, no IP's and all N's in the one column. I rebooted and it cleared them. This morning, I looked and had 29 associations and all N's again, different AP. Got a call this morning from a client on a third AP with this radio, never hear from him, and said service was very slow. Rebooting seems to clear but it slowly seems to tarpit the clients. These are all with Compex WLM54G radios.
This is not a bug, however the noise reading is calculated based on the assumption that one channel in your scan list is clean. (using it as a -95 noise floor).
The noise readings are not tied to the signal, and will change (if needed) every 30 seconds or so, when the card does a calibration.
One other bug?
the noise reports seem to be pessimistic and related to received strength
link1 5805 Mhz -65 noise -84
kink2 5180Mhz -75 noise -88
link3 2462Mhz -76 noise -81
links 1 and 2 are on channels that are completely clean, even adjacent channels are completely clean
Link 3 has some noise, the true noise floor on this link is about -90 the last time I measured it with a proper analyser
.brendan
I flashed all three AP's with that radio back to the earlier ver an hour ago. The one with 29 assoc had not passed data to a client the entire night. I got complaints from customers on 2 of the 3 units. The third one only has 4 clients.
lonnie
06-24-2006, 03:20 PM
The client bridge is a special WDS mode and thus requires that the AP also be in a bridge group. It can be its own group but it requires the bridge group to be non zero to enable WDS connections from clients. The rates are an average of the system rates and in time will settle to a comfortable and consistent value. Just flashed a couple of boards and came across a few possible bugs
1/ Rate is reporting on my client end of an 802.11a link as 16 or 17 which equate to rates of 12 Mbs and 18Mbs respectively
I also saw an 802.11b link reporting with a rate of 10
2/ Bridging, there seems to be some weirdness in the area of bridging
I bridged a Wireless interface (in Client mode) to an ethernet interface but could not ping the client at the other end of the wireless link over the bridge. I was also unable to ping the other end of the Wireless link on it's same subnet, i had to remove the bridge before I could access the other end of the link on the interface subnet
config something like this
Client end
ether1 10.0.0.5/24 (BRIDGE 1)
wpci1 192.168.3.2/24 (BRIDGE 1)
AP end wpci1 192.168.3.1/24 and 10.0.0.6/24
I'll be testing OSPF in the coming days
.brendan
lonnie
06-24-2006, 03:23 PM
The noise readings are what the card is seeing. Ignore it if you have better equipment, but your analyzer might be too fancy and only looka at the noise for that channel, whereas a radio sees everything, and even signals on another channel can represent noise to the radio. One other bug?
the noise reports seem to be pessimistic and related to received strength
link1 5805 Mhz -65 noise -84
kink2 5180Mhz -75 noise -88
link3 2462Mhz -76 noise -81
links 1 and 2 are on channels that are completely clean, even adjacent channels are completely clean
Link 3 has some noise, the true noise floor on this link is about -90 the last time I measured it with a proper analyser
.brendan
gregclemmons
06-24-2006, 08:59 PM
The new release can be downloaded from the http://www.star-os.com/starv3 downloads page.
The X86 development is almost complete. Expect the X86 WRAP version to be available soon.
Close enough to know the upgrade price?
I put the new ver on an AP this morning and it pretty much followed the same pattern. Flashed and reboot, 25 associations but all N's except 2 after 5 mins. No data moved that I saw.
Second pic is after rebooting a second time. No N's, more associations and data moving. This is with an AP with a CM9 with 5.x link to backbone and WLM54G for 2.4 clients.
It won't let me attach the screen shots I have of the two screens. Got an address I can send them? .bmp files are too big and some error about being over my quota when I upload .jpg format
Thank you.
What types of clients are showing up as 'N' ?, and what are showing up normally?
What mode is the AP operating in? (802.11b, or 802.11g) ?
If you switch from 802.11b to 802.1g, or vice-virsa, does that help?
Are you using WEP at all?
Thanks!
The clients are Tranzeo, wet11 and cb3's for the most part. Most are tranzeo. I had it set to b only and the only box checked is to hide the ssid. Not using wep. Tried b/g combo with almost the same results. Fewer associations, all N's but two and no data moving. Flashed it back to 1.0.1 and all is well right away.
I have sent you a PM.
Thanks!
butchkemper
06-25-2006, 12:29 PM
In versions 1.0.0-1090 and 1.0.1-1115, the size of the ROM file is 5570KB.
In version 1.0.2-1220, the size of the ROM file is 4873KB.
Is the difference in file size anything to be concerned about?
Butch
The size is correct, and nothing to be concerned about.
The clients are Tranzeo, wet11 and cb3's for the most part. Most are tranzeo. I had it set to b only and the only box checked is to hide the ssid. Not using wep. Tried b/g combo with almost the same results. Fewer associations, all N's but two and no data moving. Flashed it back to 1.0.1 and all is well right away.
Are you saying that you have had this issue in previous realeases as well? Any version of V3?
We just put these Compex radios up in the last 1-2 weeks and they worked fine with earlier vers. Tony furnished me a copy of a newer beta to try and at first blush, it looks good. Just flashed the 30 customer AP about 15 mins ago and everything came back up looking much better. No N's and data is moving.
Thank you for the update. I am very pleased to hear the new beta works as expected.
Thanks!
bobbyc
06-26-2006, 10:13 AM
How can I get this beta? I have a few busy APs that are WLM54G running on build 1115. If there is now a known issue with 1220, I'd like to skip it. 1115 has been very stable, however 1220 has so many other new great features.
Thanks,
Bob C
We will be providing a new release later today.
lonnie
06-26-2006, 10:52 AM
Don't panic. We were using that release with zero problems and all of our AP units are WLM-54G cards. I upgraded to the new beta to make sure it got some burn in and it also has no issues.
If you have not had any issues then you have nothing to worry about, but I would still advise to upgrade at some convenient time.
How can I get this beta? I have a few busy APs that are WLM54G running on build 1115. If there is now a known issue with 1220, I'd like to skip it. 1115 has been very stable, however 1220 has so many other new great features.
Thanks,
Bob C