Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
4.8.0.0-9028
#1
I am pleased to add the following releases, Version 4.8.0.0-9028. for the WAR-1B, Ventana and APU. Others will follow in the coming weeks.

It is available now for download at https://cp.sync.com/dl/4bd9ff300#5imn6u3...r-rfcrd8vi

Please test on an easy to access system and make sure it is stable for your situation. The firmware has been stress tested for general function and throughput in an indoor environment. Your outdoor and long term use "might" not be the same. I have NOT had any issues with upgrading and absolutely NO BRICKS have been created. I have, however, noticed that clients may NOT reboot after an upgrade, BUT a power cycle brings them right up. I am investigating why. I will say this is a safe release to test and your long term use will determine its reliability.

PLEASE post any reports, good or bad, of your testing and use. Your feedback is important and helps me to make repairs.

Main Features of the 4.8.0.0-9028 Release
- fixed my throughput at distance issue
- FULL Licensed Frequency support.
- FULL Bridging support.
- Hidden ESSID.
- Full Duplex.
- Basic SYNC support.
- OLSR has been upgraded to 0.9.0.3
- APU ethernet performance has doubled.
- units seem more responsive.

- make sure you do NOT use u-APSD on the clients

- This is the latest driver AND and a kernel update to 3.18.45 so I need to have the core functionality tested for reliability and to see if the AP stall issue is gone. PLEASE give this a test in a spot that has problems. I am fairly sure the AP issue is gone but my tests are indoors and less than 100 feet, but mostly non line of sight. There are typically 20+ competing stations on a site survey.

The following versions have been added and tested

- WAR-1B
- Ventana
- APU
Reply
#2
We have this on one of our AP's which often does the FUBAR thing (throughput drops to clients, some clients are un-reachable/un-pingable, some customer's report no internet, everyone eventually is unpingable and idle time on everyone counts up to 5 minutes and then they are de-authed due to inactivity). As per usual - we might not have any results for 6 days, since a new firmware requires a reboot, and most versions behave well after a reboot or power-cycle for a while.

NOTE: The RX rates on the AP on any idle connections still drop to 1 Mbit. This is a deal breaker for us. It's unacceptable to look at an AP and see half the clients with 1 Mbit rates. No previous version up to 4.7 ever did this. A 'band aid' solution is to keep some data flowing - so if we have Command Prompts pinging every client in our network they will show the correct rates, but that's obviously also a deal breaker.
Reply
#3
Be aware that this is an all new driver and does not have yet have the gui tweaks. They will come, as will the missing features like sync.

For now I REALLY want to get feedback regarding the throughput and reliability. That is what I have been working on for months and hopefully, this will fix that AP issue that has been dogging us for years.

Thanks for testing this so quickly. Am I safe to assume that my distance fix was good and the throughput was acceptable?

Note I have not looked at the report that 5 GHz ## channels do not work. That is next on the list.

ninedd Wrote:We have this on one of our AP's which often does the FUBAR thing (throughput drops to clients, some clients are un-reachable/un-pingable, some customer's report no internet, everyone eventually is unpingable and idle time on everyone counts up to 5 minutes and then they are de-authed due to inactivity). As per usual - we might not have any results for 6 days, since a new firmware requires a reboot, and most versions behave well after a reboot or power-cycle for a while.

NOTE: The RX rates on the AP on any idle connections still drop to 1 Mbit. This is a deal breaker for us. It's unacceptable to look at an AP and see half the clients with 1 Mbit rates. No previous version up to 4.7 ever did this. A 'band aid' solution is to keep some data flowing - so if we have Command Prompts pinging every client in our network they will show the correct rates, but that's obviously also a deal breaker.
Reply
#4
lonnie Wrote:Am I safe to assume that my distance fix was good and the throughput was acceptable?
I think so. Throughput is better (than build 8991 was) and I think I can leave it on to test.

I only have this on the AP side (our 'NORTH' AP) for now, since the CPE's are tricky to reboot. Throughput seems about the same as 4.7.1.0-8747 I think, but I'm not certain yet. As I'd previously mentioned, that version (4.7.1.0-8747) was the version that we had rolled back to everywhere, since all the later 4.7.x builds, and the 4.8's and 4.9's didn't really work for us.

I did also put it on our AP#86 (SOUTH) and on the CPE (that Access Point only has 1 CPE left on it) and I've had to call the client twice to power cycle it. Ping watchdog isn't apparently able to reboot the CPE either. As well, when it was connected - I tried to Putty into it and I was able to a few times, and then when I changed the distance setting to auto on the CPE, I wasn't able to log in anymore, even through i could still test throughput from the AP to the CPE, still ping the CPE and still 'starutil -reboot' the CPE... so I'm not sure what the variable there is. BUT, for today, I'll just run it on the AP and see how it performs for the slowdown/signal degrading/unable to ping/communicate with clients, deauth-due-to-inactivity issue. Again, as I've mentioned, when we reboot or power cycle a WAR1B Access Point, it's not uncommon for it to run quite well for a couple/few days sometimes. But sometimes it's only a few hours - so we will wait and see.
Reply
#5
Don't use auto for distance. Please set it manually.

One thing I did get from the research on distance timing is that all clients should be set the same, ie to the distance of the farthest one. The reason for this is that the distance timing is used as part of the carrier sense hold off timing. Thus, to be fair to the farther stations all close in units should have to wait as long as the more distant ones. Otherwise they will always get there first and could likely have some of their packets mangled by the farther ones who were not quite finished.

All testing to date has been done with an AP. I will not look at the Clients and see why you are not able to make changes and then lose your connection.
Reply
#6
Here are the Throughput Test Results. This is a 'batch' file on my desktop, testing from the shop to the AP (10.10.3.1) and then testing from my desktop to each CPE. The AP is a WAR1B at 2.4 Ghz and there are 23 clients. This is with 4.7.1.0-8747 first, and then with 4.8.0.0-9028. There is 4.7.1.0-8747 on mostly all of the CPE's (on 8 WAR1B's and on 12 WAR1A-SIAM, and then there are still 3 old WAR1 - MIPS running 4.1.12).

The results are similar - but keep in mind that I rebooted the AP between and also that some clients were using their connection, using a few 100 KB probably.


[TABLE="class: grid, width: 90%, align: left"]
[TR]
[TD]This is with 4.7.1.0-8747 on the WAR1B Access Point[/TD]
[TD]And then this is with 4.8.0.0-9028 on the WAR1B Access Point[/TD]
[/TR]
[TR]
[TD]C:\>starutil 10.10.3.1 PASSWORD -tx -duration 4
tx rate: 896 KB (17.3m) - Time left: 3 seconds
tx rate: 4864 KB (39.8m) - Time left: 2 seconds
tx rate: 5120 KB (41.9m) - Time left: 1 seconds
tx rate: 5248 KB (43.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.101 PASSWORD -tx -duration 3
tx rate: 2304 KB (18.9m) - Time left: 2 seconds
tx rate: 2176 KB (17.8m) - Time left: 1 seconds
tx rate: 2816 KB (23.1m) - Time left: 0 seconds

C:\>starutil 10.10.3.102 PASSWORD -tx -duration 3
tx rate: 640 KB (5.2m) - Time left: 2 seconds
tx rate: 640 KB (5.2m) - Time left: 1 seconds
tx rate: 512 KB (4.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.107 PASSWORD -tx -duration 3
tx rate: 384 KB (3.1m) - Time left: 2 seconds
tx rate: 512 KB (4.2m) - Time left: 1 seconds
tx rate: 512 KB (4.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.110 PASSWORD -tx -duration 3
tx rate: 2304 KB (18.9m) - Time left: 2 seconds
tx rate: 2560 KB (21.0m) - Time left: 1 seconds
tx rate: 2688 KB (22.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.112 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 1024 KB (8.4m) - Time left: 1 seconds
tx rate: 1408 KB (11.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.116 PASSWORD -tx -duration 3
tx rate: 1536 KB (12.6m) - Time left: 2 seconds
tx rate: 896 KB (7.3m) - Time left: 1 seconds
tx rate: 1792 KB (14.7m) - Time left: 0 seconds

C:\>starutil 10.10.3.120 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 1024 KB (8.4m) - Time left: 1 seconds
tx rate: 1152 KB (9.4m) - Time left: 0 seconds

C:\>starutil 10.10.3.122 PASSWORD -tx -duration 3
tx rate: 1152 KB (9.4m) - Time left: 2 seconds
tx rate: 1152 KB (9.4m) - Time left: 1 seconds
tx rate: 1152 KB (9.4m) - Time left: 0 seconds

C:\>starutil 10.10.3.125 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 1408 KB (11.5m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.129 PASSWORD -tx -duration 3
tx rate: 1792 KB (14.7m) - Time left: 2 seconds
tx rate: 2176 KB (17.8m) - Time left: 1 seconds
tx rate: 2304 KB (18.9m) - Time left: 0 seconds

C:\>starutil 10.10.3.131 PASSWORD -tx -duration 3
tx rate: 1536 KB (12.6m) - Time left: 2 seconds
tx rate: 1664 KB (13.6m) - Time left: 1 seconds
tx rate: 1792 KB (14.7m) - Time left: 0 seconds

C:\>starutil 10.10.3.132 PASSWORD -tx -duration 3
tx rate: 2176 KB (17.8m) - Time left: 2 seconds
tx rate: 2432 KB (19.9m) - Time left: 1 seconds
tx rate: 2560 KB (21.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.134 PASSWORD -tx -duration 3
tx rate: 1408 KB (11.5m) - Time left: 2 seconds
tx rate: 2048 KB (16.8m) - Time left: 1 seconds
tx rate: 1920 KB (15.7m) - Time left: 0 seconds

C:\>starutil 10.10.3.137 PASSWORD -tx -duration 3
tx rate: 1536 KB (12.6m) - Time left: 2 seconds
tx rate: 2176 KB (17.8m) - Time left: 1 seconds
tx rate: 2176 KB (17.8m) - Time left: 0 seconds

C:\>starutil 10.10.3.142 PASSWORD -tx -duration 3
tx rate: 1152 KB (9.4m) - Time left: 2 seconds
tx rate: 1280 KB (10.5m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.146 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 896 KB (7.3m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.149 PASSWORD -tx -duration 3
tx rate: 640 KB (5.2m) - Time left: 2 seconds
tx rate: 640 KB (5.2m) - Time left: 1 seconds
tx rate: 640 KB (5.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.150 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 1280 KB (10.5m) - Time left: 1 seconds
tx rate: 1152 KB (9.4m) - Time left: 0 seconds

C:\>starutil 10.10.3.151 PASSWORD -tx -duration 3
tx rate: 1920 KB (15.7m) - Time left: 2 seconds
tx rate: 2432 KB (19.9m) - Time left: 1 seconds
tx rate: 2560 KB (21.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.152 PASSWORD -tx -duration 3
tx rate: 1920 KB (15.7m) - Time left: 2 seconds
tx rate: 1920 KB (15.7m) - Time left: 1 seconds
tx rate: 1664 KB (13.6m) - Time left: 0 seconds

C:\>starutil 10.10.3.154 PASSWORD -tx -duration 3
tx rate: 2048 KB (16.8m) - Time left: 2 seconds
tx rate: 1792 KB (14.7m) - Time left: 1 seconds
tx rate: 2560 KB (21.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.156 PASSWORD -tx -duration 3
tx rate: 1792 KB (14.7m) - Time left: 2 seconds
tx rate: 1920 KB (15.7m) - Time left: 1 seconds
tx rate: 1664 KB (13.6m) - Time left: 0 seconds[/TD]
[TD]C:\>starutil 10.10.3.1 PASSWORD -tx -duration 4
tx rate: 1920 KB (15.7m) - Time left: 3 seconds
tx rate: 5504 KB (45.1m) - Time left: 2 seconds
tx rate: 5504 KB (45.1m) - Time left: 1 seconds
tx rate: 5632 KB (46.1m) - Time left: 0 seconds

C:\>starutil 10.10.3.101 PASSWORD -tx -duration 3
tx rate: 2304 KB (18.9m) - Time left: 2 seconds
tx rate: 2176 KB (17.8m) - Time left: 1 seconds
tx rate: 2688 KB (22.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.102 PASSWORD -tx -duration 3
tx rate: 640 KB (5.2m) - Time left: 2 seconds
tx rate: 512 KB (4.2m) - Time left: 1 seconds
tx rate: 640 KB (5.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.107 PASSWORD -tx -duration 3
tx rate: 512 KB (4.2m) - Time left: 2 seconds
tx rate: 384 KB (3.1m) - Time left: 1 seconds
tx rate: 512 KB (4.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.110 PASSWORD -tx -duration 3
tx rate: 2560 KB (21.0m) - Time left: 2 seconds
tx rate: 3072 KB (25.2m) - Time left: 1 seconds
tx rate: 2816 KB (23.1m) - Time left: 0 seconds

C:\>starutil 10.10.3.112 PASSWORD -tx -duration 3
tx rate: 1408 KB (11.5m) - Time left: 2 seconds
tx rate: 2048 KB (16.8m) - Time left: 1 seconds
tx rate: 1920 KB (15.7m) - Time left: 0 seconds

C:\>starutil 10.10.3.116 PASSWORD -tx -duration 3
tx rate: 1536 KB (12.6m) - Time left: 2 seconds
tx rate: 2304 KB (18.9m) - Time left: 1 seconds
tx rate: 2560 KB (21.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.120 PASSWORD -tx -duration 3
tx rate: 896 KB (7.3m) - Time left: 2 seconds
tx rate: 1024 KB (8.4m) - Time left: 1 seconds
tx rate: 896 KB (7.3m) - Time left: 0 seconds

C:\>starutil 10.10.3.122 PASSWORD -tx -duration 3
tx rate: 1024 KB (8.4m) - Time left: 2 seconds
tx rate: 1152 KB (9.4m) - Time left: 1 seconds
tx rate: 1152 KB (9.4m) - Time left: 0 seconds

C:\>starutil 10.10.3.125 PASSWORD -tx -duration 3
tx rate: 1152 KB (9.4m) - Time left: 2 seconds
tx rate: 1280 KB (10.5m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.129 PASSWORD -tx -duration 3
tx rate: 1664 KB (13.6m) - Time left: 2 seconds
tx rate: 2816 KB (23.1m) - Time left: 1 seconds
tx rate: 2816 KB (23.1m) - Time left: 0 seconds

C:\>starutil 10.10.3.131 PASSWORD -tx -duration 3
tx rate: 1280 KB (10.5m) - Time left: 2 seconds
tx rate: 1408 KB (11.5m) - Time left: 1 seconds
tx rate: 2048 KB (16.8m) - Time left: 0 seconds

C:\>starutil 10.10.3.132 PASSWORD -tx -duration 3
tx rate: 2432 KB (19.9m) - Time left: 2 seconds
tx rate: 3584 KB (29.4m) - Time left: 1 seconds
tx rate: 3584 KB (29.4m) - Time left: 0 seconds

C:\>starutil 10.10.3.134 PASSWORD -tx -duration 3
tx rate: 2048 KB (16.8m) - Time left: 2 seconds
tx rate: 2560 KB (21.0m) - Time left: 1 seconds
tx rate: 2560 KB (21.0m) - Time left: 0 seconds

C:\>starutil 10.10.3.137 PASSWORD -tx -duration 3
tx rate: 896 KB (7.3m) - Time left: 2 seconds
tx rate: 2688 KB (22.0m) - Time left: 1 seconds
tx rate: 2432 KB (19.9m) - Time left: 0 seconds

C:\>starutil 10.10.3.142 PASSWORD -tx -duration 3
tx rate: 1152 KB (9.4m) - Time left: 2 seconds
tx rate: 1280 KB (10.5m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.146 PASSWORD -tx -duration 3
tx rate: 1408 KB (11.5m) - Time left: 2 seconds
tx rate: 1664 KB (13.6m) - Time left: 1 seconds
tx rate: 1664 KB (13.6m) - Time left: 0 seconds

C:\>starutil 10.10.3.149 PASSWORD -tx -duration 3
tx rate: 768 KB (6.3m) - Time left: 2 seconds
tx rate: 768 KB (6.3m) - Time left: 1 seconds
tx rate: 640 KB (5.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.150 PASSWORD -tx -duration 3
tx rate: 1152 KB (9.4m) - Time left: 2 seconds
tx rate: 1152 KB (9.4m) - Time left: 1 seconds
tx rate: 1280 KB (10.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.151 PASSWORD -tx -duration 3
tx rate: 2560 KB (21.0m) - Time left: 2 seconds
tx rate: 2688 KB (22.0m) - Time left: 1 seconds
tx rate: 3200 KB (26.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.152 PASSWORD -tx -duration 3
tx rate: 1920 KB (15.7m) - Time left: 2 seconds
tx rate: 2560 KB (21.0m) - Time left: 1 seconds
tx rate: 3072 KB (25.2m) - Time left: 0 seconds

C:\>starutil 10.10.3.154 PASSWORD -tx -duration 3
tx rate: 3072 KB (25.2m) - Time left: 2 seconds
tx rate: 3456 KB (28.3m) - Time left: 1 seconds
tx rate: 3968 KB (32.5m) - Time left: 0 seconds

C:\>starutil 10.10.3.156 PASSWORD -tx -duration 3
tx rate: 2176 KB (17.8m) - Time left: 2 seconds
tx rate: 2304 KB (18.9m) - Time left: 1 seconds
tx rate: 2944 KB (24.1m) - Time left: 0 seconds[/TD]
[/TR]
[/TABLE]
Reply
#7
That makes me feel pretty good. I have the throughput as good as and maybe even a bit better. Now if it is just stable I can get after the enhancements.

BTW, I have "fixed" the lowest rate issue being displayed in the AP. I was simply setting a flag without actually saving the value. I think I also fixed the Client reboot on upgrade (at least on 2 clients tested so far). Once I do a bit of testing I'll generate a new release so you can have a more solid testing platform.
Reply
#8
Build 9030 is uploading and will be available shortly.

It fixes the 1 mbps last rate issue and I "think" the Client reboot after upgrade is fixed. Be careful and be prepared on the first few units to have someone available to power cycle them.
Reply
#9
Build 9028 seems to have the exact same results on the WAR1B Access Point as all previous WAR1B releases.
Reply
#10
Just to be sure --> it still has the AP stall and disconnect happening?

The only thing left is the 4.9 driver if that is the case. It is totally different. All the other drivers have evolved from the Linux kernel ath9K and there seems to be a common problem.

Would you still be able to provide me with that 2 km test lan? I will need to begin testing on the 4.9 firmware asap.

ninedd Wrote:Build 9028 seems to have the exact same results on the WAR1B Access Point as all previous WAR1B releases.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)