I've noticed an issue since the update to 8.173/8.174 involving wireless clients; if I have more than 1 wireless client (laptop) connected to my test ASG via an AP10, both clients suffer severe performance impact; even simple, low-bandwidth web browsing is intermittent, and even accessing webadmin is intermittent / slow. If I put one of the machines to sleep, or shut them off, performance returns to normal levels. It's not about bandwidth (very little traffic is involved). I've tried changing the encryption types (was set at WPA2 Personal before, tried WPA personal to no effect), etc... I think it may have something to do with the fact that I have client isolation enabled. The laptops are using different WLAN nics / chipsets, and work fine individually, so I don't think it's a NIC incompatibility. This all worked fine in 8.172, except for the fact I have to have spoof detection disabled to use my AP10 in my particular configuration (see my other bug report). Spoof detection is still disabled, btw. I see no drops in the packet filter logs, no IPS detections, etc. Network Awareness is disabled. I can send the wireless log from last night to whoever's interested via PM, just let me know.
I noticed some different behavior after upgrading to 8.200 concerning my AP10. I had the configuration for the wireless security set to WPA2/WPA1 for backward compatibility and noticed some devices that worked before did not work after. I had to change the wireless security to lock down to WPA2 using AES and that corrected the problem devices. Seems that the negotiation of security my be an issue now that was not an issue before. Also I noticed after upgrading that I was getting some poor performance also with movie streaming from amazon and netflix. Looked at the firewall logs and noticed a ton of spoofed packets being dropped. I was informed that there is a issue with the Protocol handler and I needed to turn off that option in the network security/firewall/advanced. with these two changes everything seems to be working now with no performance issues. I also noticed that the AP's seem to drop speed on the clients when they are inactive and have seen some connections to 1024Kbit at times. Seems however when you start to use that devices the speed goes back up to normal. I wounder is the new firmware on the AP's is doing load balancing of some sort. Can we get some information on what was changed in the AP's firmware as this does not seem to be documented anywhere that I can find.
I noticed some different behavior after upgrading to 8.200 concerning my AP10. I had the configuration for the wireless security set to WPA2/WPA1 for backward compatibility and noticed some devices that worked before did not work after. I had to change the wireless security to lock down to WPA2 using AES and that corrected the problem devices. Seems that the negotiation of security my be an issue now that was not an issue before.
There was a bug in versions
Also I noticed after upgrading that I was getting some poor performance also with movie streaming from amazon and netflix. Looked at the firewall logs and noticed a ton of spoofed packets being dropped. I was informed that there is a issue with the Protocol handler and I needed to turn off that option in the network security/firewall/advanced.
Ok, not sure what to do with this.
with these two changes everything seems to be working now with no performance issues. I also noticed that the AP's seem to drop speed on the clients when they are inactive and have seen some connections to 1024Kbit at times. Seems however when you start to use that devices the speed goes back up to normal. I wounder is the new firmware on the AP's is doing load balancing of some sort. Can we get some information on what was changed in the AP's firmware as this does not seem to be documented anywhere that I can find.
The firmware did not only add some new features, it basically swapped the whole 802.11 stack. Hence, it doesn't make sense to list a number of changes.
However, regarding the rate drop to 1Mbit sometimes: this only happened in earlier beta versions since the UI showed the rate of the last tx'ed frame but management frames are always send with 1Mbit. Hence, in times where no data frames are sent it was very likely that the rate of the last management frame was shown. Now only the tx rate of data frames should be used for the UI.
I noticed some different behavior after upgrading to 8.200 concerning my AP10. I had the configuration for the wireless security set to WPA2/WPA1 for backward compatibility and noticed some devices that worked before did not work after. I had to change the wireless security to lock down to WPA2 using AES and that corrected the problem devices. Seems that the negotiation of security my be an issue now that was not an issue before.
There was a bug in versions
Also I noticed after upgrading that I was getting some poor performance also with movie streaming from amazon and netflix. Looked at the firewall logs and noticed a ton of spoofed packets being dropped. I was informed that there is a issue with the Protocol handler and I needed to turn off that option in the network security/firewall/advanced.
Ok, not sure what to do with this.
with these two changes everything seems to be working now with no performance issues. I also noticed that the AP's seem to drop speed on the clients when they are inactive and have seen some connections to 1024Kbit at times. Seems however when you start to use that devices the speed goes back up to normal. I wounder is the new firmware on the AP's is doing load balancing of some sort. Can we get some information on what was changed in the AP's firmware as this does not seem to be documented anywhere that I can find.
The firmware did not only add some new features, it basically swapped the whole 802.11 stack. Hence, it doesn't make sense to list a number of changes.
However, regarding the rate drop to 1Mbit sometimes: this only happened in earlier beta versions since the UI showed the rate of the last tx'ed frame but management frames are always send with 1Mbit. Hence, in times where no data frames are sent it was very likely that the rate of the last management frame was shown. Now only the tx rate of data frames should be used for the UI.
