starv3-1.5.5b-3660 *beta* released - all platforms

[tony]

There is a new firmware available for all platforms.

This is a refresh of 1.5.4b, and resolves the issues people were seeing. No other features or enhancements have been added.

What has changed since 1.5.3b:
1. Working support for all our platforms (war-1, war-1a, war-2, war-4, x2000, x4000, metro, wrap, pc, server)
2. high and low signal filter support
3. new: noise buster mode. (use with caution, see notes below).
4. ssh desktop now shows the proper rate at all times, and not a '*'.
5. many atheros tweaks and improvements.

Please use auto rate until you are sure you need manual control. The new rate control has worked very well for us.

Noise Buster mode notes:
This mode is to be used in extreme conditions where you have heavy interference. This mode will greatly improve performance but will likewise cause interference (sometimes complete blackouts) to neighboring wifi systems on the same channel. Do not use this in highly wifi populated areas, especially when your own equipment can be affected.

Useful for tight beam PtP shots, or sparsely populated PtMP areas.

This affects the CSMA/CA, among many other hardware characteristics, and may violate regulations in some regions. Please use with planning, caution, and care.

Before upgrading your systems, please note:
This IS a beta, so please upgrade ONE of your easy to access systems before doing any mass upgrades.

Also, please read past release notes, specifically ones relating to DFS as they will affect the CA, and US country codes in 1.5.x.

With world mode '##' compatibility, please read past release notes, but also keep this in mind:
5.x GHz extended frequencies should be compatible between all major releases.
2.4 GHz extended frequencies are not compatible between major releases, however channels 1 - 14 are. We are still working on the 2.4 GHz extended frequency mode in the hopes to make it compatible with the 1.4.x series.

Please keep note of these 1.4.x features that are not implemented yet:
1. WDS (Priority: very high)
2. Full Duplex (iPriority: high)
3. MAC / Radius ACL (Priority: high)
4. Managed Mode (Priority: medium)
5. Channel ACL (Priority: low)

This release does support WPA/WPA2, WEP, and the rest of the features you would expect.

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

Please report your results as it will help us improve things. If you have a problem, and keep quiet about it, there is a good chance it will not get resolved.

Please keep this thread on topic, and professional. Posts with profanity, name calling, or bashing can, and will be deleted.

Thanks, and good luck. We are looking forward to hearing your results. The rest of the 1.4.x features are being worked on, as are many new ones.

As a precaution, reboot your system before doing an upgrade.

[timotei]

Haven't got time for proper testing right now, but I can confirm that yesterdays M1208a now boots with wpci and seems to work as expected with 1.5.5.
Very satisfied with the priority list of features to come.

[lonnie]

Thanks for the feedback.

[c.davis]

I put this on a small microcell (GW WAR-4) and its CPE's (mix of WAR1's and GW WAR-2's) this morning and it seems to work quite nicely.

The AP has 2 WLM54G's and 1 XR9, the WLM's signals/noise/Q didn't really seem to differ between 4.22 and 3.23 but felt much more responsive and starutil throughput tests were certainly higher, running a fairly aggressive ping 'ping -i 0.001 -c 5000' to our core router a few times from each upgraded unit all completed without dropped packets.

The XR9, as has been noted previously, was degraded as compared to 4.22 and 3.23 but still ran through the quick tests mentioned above. The received signal on the CPE was no different but the received signal on the AP was as much as 15db less but it still performed very well.

The only thing holding me back from testing in more places is that ip addresses are not being displayed on the association list, not a big deal for this small scenario but would become quite an adventure at more populated places.

As a small request, would it be possible to add starutil to the available bins in the console?

Overall, a nice upgrade.

[ninedd]

The XR9, as has been noted previously, was degraded as compared to 4.22 and 3.23 but still ran through the quick tests mentioned above. The received signal on the CPE was no different but the received signal on the AP was as much as 15db less but it still performed very well.Hi. Can you elaborate on the XR9 experience with 1.5.5b? One of the primary reasons we didn't upgrade our network to 1.4.22r everywhere was because where we run XR9's, performance went right out the window with 1.4.22r - even though in other places (2.4 and 5g) we found 1.4.22r better.

So, you say ''as has been noted previously, XR9 was degraded compared to 4.22" - what specifically does that mean? We're ANXIOUS to move up to 1.5 across the whole network (~1300 units) but want to be very careful about our 1.3.23b AP's that are running XR9's. Thank you.

[c.davis]

Hi. Can you elaborate on the XR9 experience with 1.5.5b? One of the primary reasons we didn't upgrade our network to 1.4.22r everywhere was because where we run XR9's, performance went right out the window with 1.4.22r - even though in other places (2.4 and 5g) we found 1.4.22r better.

So, you say ''as has been noted previously, XR9 was degraded compared to 4.22" - what specifically does that mean? We're ANXIOUS to move up to 1.5 across the whole network (~1300 units) but want to be very careful about our 1.3.23b AP's that are running XR9's. Thank you.

I just meant that it has been noted that the XR9's require special handling in the driver which hasn't been added to the 1.5 series yet so the results were expected. Oddly enough, and happily, even the one XR9 client that had the 15db drop in signal still connected at 48Mb on both tx and rx and quality stayed at 100 on both ends.. performance was great so I'm not going to make a rush to downgrade firmware but rather let it ride out for a bit and see how things go.

Where many were having issues with XR9's while running 4.22 we did not, they just ran and ran and did very well. I think that this is primarily due to our location and the absence of competition in that frequency range.

Perhaps the new 'Noise Buster' feature will be of great use to you, it certainly would be interesting to see how it performs in the presence of Canopy gear.

[lonnie]

Tony has added all sorts of XR9 mods but the 1.3.x driver does not do well with the 1.5 driver.

My only advice is take a small workgroup and convert them and see how it all performs. I will stress that you really want to do them all, since mixed firmware would be expected to have problems.

Even if everyone reported great results, you might see terrible results, so at the end of the day you have to give a go, and see how it works.

The base seems solid now, and we will start to flesh it out AND add in 11n card support.

[greg]

All right ya wusses, I flashed a stock wp188 with this version. Note: I did wait until after lunch so as not to ruin my Chinese cuisine! It was running 1.3.23 and has 26 clients, about 2/3's of which are alien CPE. A very vanilla 2.4 1x AP. All quickly came back and associated which greatly pleases me after the reboot. Sure would be nice to have IP addresses in the association list. I've pinged at least half the radios and all have replied. Signals are very close to the b4 and after. I have tried 1.4.x on this same AP numerous times and usually never get close to the # of associations after the flash v. before it. 1.4.22 would not work on this at all and I'd have to flash it back to 1.3.23 pronto before the natives got restless.

Note: This AP is usually one of my early guinea pigs as it is standalone board connected to the backbone AP via ethernet. I don't have to fret (much) about a truck roll if I lose the backbone link because it is a separate unit.

I'm pleasantly shocked! It's been up for 25 mins and zilcho calls so far.

[Stratolinks]

I haven't installed this on anything just yet, but hopefuly will roll it out to one or 2 APs in the wee hours tonight.

Just a quick question, did you manage to squeeze ISC DHCP server into the old WAR1 version?

[rbolduc]

did something happen to 2402 and 2407mhz? Had an ap on 2407 updated one of the clients and it never came back, till I happened to try a channel switch then it came online, I looked at the client and 2402 and 2407 are not in the list, it goes from 2372 to 2412..

War1
## country code
cloaking 2x
wlm54 card

Reed

[tog]

You'll find that 2407 isn't even compatible across staros versions (or vendors), though 2467 and 2472 are.

So it's not even there in 1.5.x

[Stratolinks]

You'll find that 2407 isn't even compatible across staros versions (or vendors), though 2467 and 2472 are.

So it's not even there in 1.5.x

It has always worked fine for me with previous versions of Star-OS. It can only legally be used with 2x cloaking so it doesn't matter if it will talk to other vendor's stuff anyway. Whenever I use 2407, 2467, or 2472, it is always pure Star-OS anyway so I don't have an issue. I always put a custom scan list into my CPEs set to 2400-2483 to reduce the scan time for a client to associate, and it scans the entire legal band anyway. I use 2407 and 2472 in 2x a lot of places.

2402 cannot be used legally unless you could come up with a 4 MHz wide channel somehow. In North America (FCC and Industry Canada) it is illegal to transmit below 2400MHz.

[rbolduc]

It has always worked fine for me with previous versions of Star-OS. It can only legally be used with 2x cloaking so it doesn't matter if it will talk to other vendor's stuff anyway. Whenever I use 2407, 2467, or 2472, it is always pure Star-OS anyway so I don't have an issue. I always put a custom scan list into my CPEs set to 2400-2483 to reduce the scan time for a client to associate, and it scans the entire legal band anyway. I use 2407 and 2472 in 2x a lot of places.

2402 cannot be used legally unless you could come up with a 4 MHz wide channel somehow. In North America (FCC and Industry Canada) it is illegal to transmit below 2400MHz.

Yep me also, there are a few places where it works great..

[tog]

2407 doesn't work between 1.3.x and 1.4.x.

[Stratolinks]

OK, I have had a chance to try this version in a couple spots.

1st Location (at my house):
WAR2 with 2CM9 cards (both are disabled). 2 Ethernet ports for routing purposes. Upgraded to 1.5.5 and it would not come back up. Power cycled several times without success. Removed mPCI cards and power cycled it again and it came up OK.

2nd Location (top of the tower at my house):
WAR4-METRO with 4 WLM54AGP23 cards (3 are currently disabled). 2 Ethernet ports for different connections to it. Upgraded to 1.5.5 but it wouldn't connect to the AP at the other end (1.4.22, X86 PC, 5320MHz, AP, CA country code, 11a, Dist 4 - actual distance .3 Miles). The site survey won't even show the AP.


So, I guess the question is, Do we have to upgrade from the AP end first so the old version client can connect to the new version AP?

I will try this from another location this evening to verify results.

[Stratolinks]

2407 doesn't work between 1.3.x and 1.4.x.


I was using 2407 on 1.3.13 and migrated to 1.4.22 without any issues. Or at least I don't recall having any issues. However I upgrade all the clients, then then the AP, then reboot all the clients and the AP so maybe I just never saw the issue.

[keith.yoder]

I also tried this on a WAR2 (WP188 version) with two cards. It would not boot with both cards. I removed one and it booted. Even tried replacing the "bad" card with another and it still didn't boot. Had to go back to 1.4.22.

Keith

[Stratolinks]

Next Try: old WRAP board, that I have Ethernet access to.

License expired, bought new license and pasted it in. The unit then rebooted and came back up running 1.4.22 OK. Then I used starutil to send it the 1.5.5 version. When it rebooted it came up in free mode. I tried the key that I had just purchased, but it wouldn't work. I purchased another key using the new key request and pasted it in. It rebooted OK and the wireless clients came back on at pretty much the same signal levels as before. Then I realized that the Radius ACL isn't implemented yet because a couple extra devices were trying to connect that shouldn't be. Then I thought DOH the release notes did say the ACL wasn't functional yet. I then downgraded back to 1.4.22 for now, but it came up in free mode and I had to put the first key request back into it to bring it up licensed again.

Just so you know...

[mickeym]

Yep me also, there are a few places where it works great..

We also have spots where we use 2407/2x - a couple where that's the only channel that works - this creates a real problem moving to this version if 2407 isn't included yet.

[tony]

I also tried this on a WAR2 (WP188 version) with two cards. It would not boot with both cards. I removed one and it booted. Even tried replacing the "bad" card with another and it still didn't boot. Had to go back to 1.4.22.

Keith

What services do you have running in the system, and what does the free memory say when you have 1 card in it, with 1.5.5., or 2 cards in it with 1.4.22?

Next Try: old WRAP board, that I have Ethernet access to.

License expired, bought new license and pasted it in. The unit then rebooted and came back up running 1.4.22 OK. Then I used starutil to send it the 1.5.5 version. When it rebooted it came up in free mode. I tried the key that I had just purchased, but it wouldn't work. I purchased another key using the new key request and pasted it in. It rebooted OK and the wireless clients came back on at pretty much the same signal levels as before. Then I realized that the Radius ACL isn't implemented yet because a couple extra devices were trying to connect that shouldn't be. Then I thought DOH the release notes did say the ACL wasn't functional yet. I then downgraded back to 1.4.22 for now, but it came up in free mode and I had to put the first key request back into it to bring it up licensed again.

Just so you know...

This is something I have heard in other threads to, and have dedicated a week to try and replicate, however I have been unsuccessful, All my test WRAPs have no issues between 1.1,x, 1.3.x, 1.4.x, all the way to 1.5.5 with the license. Can you verify that your system's MAC address for both ethernets are the same between releases? This should never change. Also, what brand of CF are you using? (if you know off the top of your head).

Thanks again.

[tony]

OK, I have had a chance to try this version in a couple spots.

1st Location (at my house):
WAR2 with 2CM9 cards (both are disabled). 2 Ethernet ports for routing purposes. Upgraded to 1.5.5 and it would not come back up. Power cycled several times without success. Removed mPCI cards and power cycled it again and it came up OK.


What does the system report for ram when using 1.5.5, and also what services do you have enabled? The 1.5.5 is packed with many up and coming things for the soon-to-be-available 11n, amongst other things and consumes more ram than previous releases, though should work just fine in a stock WAR-2 (GW or WP188) with a normal number of services enabled. (ie. RIP or OSPF, ISC DHCP, etc.).


2nd Location (top of the tower at my house):
WAR4-METRO with 4 WLM54AGP23 cards (3 are currently disabled). 2 Ethernet ports for different connections to it. Upgraded to 1.5.5 but it wouldn't connect to the AP at the other end (1.4.22, X86 PC, 5320MHz, AP, CA country code, 11a, Dist 4 - actual distance .3 Miles). The site survey won't even show the AP.


So, I guess the question is, Do we have to upgrade from the AP end first so the old version client can connect to the new version AP?

I will try this from another location this evening to verify results.

What channel are you using on the AP?
Would it be possible to get me Ethernet login access to this system, if possible? Normally when you do sight surveys, how many systems do you see?

[Stratolinks]

What services do you have running in the system, and what does the free memory say when you have 1 card in it, with 1.5.5., or 2 cards in it with 1.4.22?

I will add my 2 cents here too just in case it helps. I left it running on 1.5.5 since it is just using the Ethernet to do routing anyway.
http://stratolinks.com/forums/houserouter.gif

This is something I have heard in other threads to, and have dedicated a week to try and replicate, however I have been unsuccessful, All my test WRAPs have no issues between 1.1,x, 1.3.x, 1.4.x, all the way to 1.5.5 with the license. Can you verify that your system's MAC address for both ethernets are the same between releases? This should never change. Also, what brand of CF are you using? (if you know off the top of your head).

I assume the MAC is encoded in the license request key somewhere, right. The ether1 MAC under 1.4.22 is 00:0d:b9:01:db:54 and ether 2 ends in 55. I will try it again in the wee hours overnight to see if it is different under 1.5.5. As to the CF brand in this location, from the logfile: hda: SanDisk SDCFB-64, CFA DISK drive.

I will try this in a few other locations where the WRAP is connected to another router by Ethernet overnight to see if we can get anything consistent between them.

[lonnie]

Not a chance for ISC DHCP. The new driver is larger than the old one and Tony spent two hair pulling days squeezing space to make it fit, with the same services as before.

I haven't installed this on anything just yet, but hopefuly will roll it out to one or 2 APs in the wee hours tonight.

Just a quick question, did you manage to squeeze ISC DHCP server into the old WAR1 version?

[Stratolinks]

What channel are you using on the AP?
Would it be possible to get me Ethernet login access to this system, if possible? Normally when you do sight surveys, how many systems do you see?

That was in the first message, 5320MHz. Yes I can get you access if you can PM me a IP address you let me know the IP that you will be coming in from, I'll punch a hole to let ssh and starutil in. The handy part is this IP has 2 different routes to it one over a HSA (Ethernet over DSL) and the other over my wireless backbone. Thus is is reachable even when the wireless side is down. I can't do the upgrade on the AP it is pointed at just yet since there are 2 other links on it. Normally all I see in the site survey is the link it is supposed to connect to.

[Stratolinks]

Not a chance for ISC DHCP. The new driver is larger than the old one and Tony spent two hair pulling days squeezing space to make it fit, with the same services as before.

OK, I would have figured out once we try it on a WAR1, but it is nice to know ahead. I would have preferred that all dynamic routing protocols be left out in favor of ISC-DHCP, but I am sure that would have ticked off others. Personally, I just don't see any need for any dynamic routing support in the low end CPE device.

[rbolduc]

Now if I have a ap/client that has a interference problem (Before I raise HELL) are you supposed to enable the "noise buster" at the AP or just the client or both? The ap is near ( within 2000') of 3 motels all having wifi and a home depot with 10ap's UGH, and this is the one we were running 2407 successfully but with no 2407 I was going to try the new toys.. I have a BH to this AP on 2457 so I am planning to be as FAR away from that channel as I can..


Thanks
Reed

[tony]

This noise buster mode can be applied to either the Client or AP (or both).

[Stratolinks]

Had another one of those DOH! moments again. I put the AP in Station mode and the WAR4-Metro in AP mode (otherwise all the same settings) and then installed 1.5.5 on the Metro. It came up and the remote end connected. Seems to be working now. I'll run it through the paces overnight and let you know in the morning.

[lonnie]

How about --> whichever site is affected by the noise. The site with poor tx throughput will benefit.

Now if I have a ap/client that has a interference problem (Before I raise HELL) are you supposed to enable the "noise buster" at the AP or just the client or both? The ap is near ( within 2000') of 3 motels all having wifi and a home depot with 10ap's UGH, and this is the one we were running 2407 successfully but with no 2407 I was going to try the new toys.. I have a BH to this AP on 2457 so I am planning to be as FAR away from that channel as I can..


Thanks
Reed

[Stratolinks]

OK, I tried this on another WRAP AP. This one has 2 radios. WPCI1 is in B only ode and has 3 clients left on it. The other is in 2x G-only Pure G on 2472MHz. It has 29 clients on it. The WRAP takes the 1.5.5 update without going to free edition this time (looks like the other one may be just a quirk). When it reboots, all 3 of the 11B clients reconnect, but none of the 2x 11G clients reconnect at all. I tried changing down to 2462MHz, but it didn't help Once I put 1.4.22 back on everybody came back on again.

I can't really go upgrading my APs until the radius ACL is included anyway. But, I hope to be able to upgrade some of the backbone to give it a fair shake.

[tony]

What settings do you have on the 11G clients? Do you have pure-g selected on them as well? If so, if you disable that option, do they then connect?

Thanks

[Stratolinks]

What settings do you have on the 11G clients? Do you have pure-g selected on them as well? If so, if you disable that option, do they then connect?

Thanks


I will try that next time I give it a whirl, probably tomorrow evening.


Possible CM9 Major Issue:
One more thing. And I have reproduced this on 2 different locations on X86. On 1.5.5 with CM9 radio cards set to 11a turbo station mode. They come up at 2412 and won't connect to a 5GHz AP or even show it in the scan list. (2312 if the country code is ##) I have not had a chance to test if this is true of normal 11a mode yet. I had to drive 140k round trip to go fix this one by plugging into the Ethernet port to bring it back online by eventually downgrading to 1.4.22.

[tony]

Thank you. I have verified this behavior and will get it fixed for the upcoming release.

[rbolduc]

I tried to upgrade a ap with 3 clients on it with little success, in trying to re-flash the clients back to 1.4.22 I noticed the transmit was stuck at 36, these are clients with poor signal ( -78) and I had them locked to a max of 36 and rate aggressiveness to -2 which worked great, is the rate locking feature the same in 1.5.x series? or do we have to set the clients to auto because now "rate 36" locks it there? might be the issue where I have 1 client that had good signal upgraded with no issue and the other 2 were a nightmare after the upgrade..

Thanks
Reed

[tony]

You should chose auto rate with the new version, and let us know how it performs compared to the previous releases.

[rbolduc]

You should chose auto rate with the new version, and let us know how it performs compared to the previous releases.


Ahhhh that would make a difference then... Ill try that this afternoon, might want to add that to the notes section because if you are running a client at a rate and it locks there in a new version its a PITA to get back into it ;) most of my ap's and clients are set for 36 aggressiveness -2


Thanks
Reed

[rbolduc]

Ok here are my list of caveat's for the beta if you are upgrading from 1.4.22

1. make sure everything is set to AUTO no locked rates, no locked max, otherwise your new upgraded AP/CPE will be LOCKED to that # you had entered

2. if you upgrade the AP 1st make sure clients have "pure-g" mode off or they won't connect back to your nice new upgraded AP, but an AP that has "pure-g" mode selected can have clients with 1.5.5 connect just fine and work.

3. be sure you are not using 2402 or 2407 as these are not in this release (maybe later?)

Finer points that might keep you from spending 4 hours troubleshooting, lucky this was an AP with 3 clients and later at night, the plus side is I don't need a hair cut now after I pulled most of it out ;)

Reed

[lonnie]

Thanks Reed. Hair is so over rated anyway.

This driver is trying to maintain a standard for 11n to 11abg interop, thus some "extensions" got broken. We are doing our best to "fix" the extension yet still make sure we do not break the 11n compatibility.

[DrLove73]

Tony, will the new release take more then 3 days or will it be just a quick fix like 1.5.5b? I was planing time to test this new release, and I am traveling in a few days 400km to the location of the "other" network I maintain, so I need to make arrangements.

If you are not sure feel free to say more and I will leave testing and upgrade for another time.

[lonnie]

There will be a new release in the morning to fix the turbo mode issue. Expect a release with a few more additions by mid next week. We are getting more confident all the time with this new driver. Pretty much settled down to a stable base. Soon it is time to work on adding rather than building.

[greg]

The WP188 2.4 AP is working fine for almost 24 hours. It had 1.3.23 and I'm pleased to upgrade it without issues. Many alien clients on it. It does have a WLM AG23 as a radio so I didn't get bit by the cm9 bug. None of the 1.4.x versions ever worked successfully on this AP.

[rbolduc]

Next Try: old WRAP board, that I have Ethernet access to.

License expired, bought new license and pasted it in. The unit then rebooted and came back up running 1.4.22 OK. Then I used starutil to send it the 1.5.5 version. When it rebooted it came up in free mode. I tried the key that I had just purchased, but it wouldn't work. I purchased another key using the new key request and pasted it in. It rebooted OK and the wireless clients came back on at pretty much the same signal levels as before. Then I realized that the Radius ACL isn't implemented yet because a couple extra devices were trying to connect that shouldn't be. Then I thought DOH the release notes did say the ACL wasn't functional yet. I then downgraded back to 1.4.22 for now, but it came up in free mode and I had to put the first key request back into it to bring it up licensed again.

Just so you know...

Ditto!!! Except for I kept the new license as this was a client and didn't care about ACL, but the steps were the same, install new key (was expired), reboot (works great), upgrade 1.5.5 (went smooth), reboot and into free mode it went(palm-forehead), drive to house log in Ethernet go to license-keys.com order a new key and BAM its back and running..

Reed

[lonnie]

It was an issue with turbo, and affected all cards in 5 GHz. CM9 was just the first card to find it.

The WP188 2.4 AP is working fine for almost 24 hours. It had 1.3.23 and I'm pleased to upgrade it without issues. Many alien clients on it. It does have a WLM AG23 as a radio so I didn't get bit by the cm9 bug. None of the 1.4.x versions ever worked successfully on this AP.

[tog]

OK, I have had a chance to try this version in a couple spots.

1st Location (at my house):
WAR2 with 2CM9 cards (both are disabled). 2 Ethernet ports for routing purposes. Upgraded to 1.5.5 and it would not come back up. Power cycled several times without success. Removed mPCI cards and power cycled it again and it came up OK.

Any update with this?

Was this a Gateworks WAR2 or Compex WP188 WAR2 that wouldn't boot with 1.5.5 when both radios were plugged in? Did you ever get it going with both radios? Based on your experience, I'm going to bench test the myriad of hardware platforms I have out there so I don't get any nasty surprises on production WAR2/WAR4s that are way up on towers.

I am going to do some bench testing myself today and/or tomorrow to figure out what does and doesn't work between 1.4.22 and 1.5.x, like pure-g on/off and other various settings. I will also be trying WP188s, Gateworks boards, WAR1 and WAR1a fully loaded with radios to ensure the platforms I have out there generally boot ok with 1.5.5.

My first goal is to be able to put 1.5.5 on a few troublesome clients out there and see if I can connect them up to 1.4.22 access points (even if I have to disable pure-g at the AP or something), so I need to bench test that combination. I really want the noise buster feature at some of my client ends. With 1.4.22 on the client unit and a moderate amount of noise nearby they tend to sputter out badly enough that the ping watchdog will start to show 1-3 dropped pings every 30-60s. That's when you know noise is causing it to run poorly enough to cause a swift customer complaint. Doesn't matter if you've got a -60 signal.

[Stratolinks]

Was this a Gateworks WAR2 or Compex WP188 WAR2 that wouldn't boot with 1.5.5 when both radios were plugged in? Did you ever get it going with both radios?

This is a Compex WAR2 (the only one I have anywhere on my network). I have tried it with a radio in either slot (the CM9 radios that were in it), and even with WLM54AG cards in either and both slots. If there are radios in it, it will not boot. The Power supply is a pair of batteries kept charged with a 2.5A DIN power supply, so I really doubt if it is a power issue.

[miles]

I tried to upgrade to 1.5.5 on a WP188 2 slot on the tower today and rendered it unreachable. I replaced the board and brought the upgraded board back to test.

The board was unreachable with complex cards in place. Remove the cards and poof, I could get into it. Replace the cards and it was unreachable again. Flashed back to 1.4.22 and the board worked fine.

It didn't matter the type of card. Any card inserted in a slot made the board unreachable.

[greg]

That reminds me of what happened when upgrading a wp188 with a version of 1.4.x Couldn't access it if any radios were installed. Pull them out, flash it back and it would work again. Turned out it was just the 128meg version of the board that had that issue. Tony released up update that fixed it.

[tony]

For those with Compex WAR-2 / X2000 systems that do not power with a radio put in. What power supplies are you using? Those using batteries, have you tried a normal power supply (if possible)? Also, has anybody experienced any issues with the Gateworks WAR-2, or WAR-4 systems?

Thanks again.

[c.davis]

We've got a few GW WAR-2 and GW WAR-4 units running 1.5.5 with WLM54G, two with a CM9 (one of each SBC).. all are running without issue, the ap feeding them is a Metro also running 1.5.5. We haven't tried this firmware with any of the WP boards as they are all running as hotspots so we stick with either 1.3.13 or 1.3.23 for that purpose.

[tony]

To help us troubleshoot the WAR-2 bootup issue, can you please send me a copy of your configuration? (change the password to 1234 first, but nothing else).

Please send it to toole.t [at] gmail [dot] com

Also please specify the name you use on the forums, and a link to this thread.

Thanks again.