Okay, at least two*
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com ----- Original Message ----- From: "Josh Reynolds" <[email protected]> To: "ubnt users" <[email protected]> Sent: Tuesday, October 28, 2014 11:33:33 AM Subject: Re: [Ubnt_users] PSA: Ubnt XM v5.5.10 major bug -- recommend using v5.5.8 -- STA scan-list empty, cannot connect to AP the re was an rc3 before 5.5.10 final :P Josh Reynolds, Chief Information Officer SPITwSPOTS, www.spitwspots.com On 10/28/2014 05:02 AM, Mike Hammett wrote: Do you even firmware alerts, bro? Yeah, there were two RC versions published. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com ----- Original Message ----- From: "Josh Luthman" <[email protected]> To: "Ubiquiti Users Group" <[email protected]> Sent: Tuesday, October 28, 2014 7:55:38 AM Subject: Re: [Ubnt_users] PSA: Ubnt XM v5.5.10 major bug -- recommend using v5.5.8 -- STA scan-list empty, cannot connect to AP Wasn't it in beta? Someone said there were two RC. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Oct 28, 2014 3:06 AM, "Colin Zwiebel" < [email protected] > wrote: <blockquote> It occurs to me an alternative model would be to redo Ubnt beta testing. Buggy firmware is making it out of beta and I believe more issues could be caught in Beta if Ubnt could help WISPs test. Have staff that work specifically with partner wisps. Run advanced diagnostics on our network, help us migrate devices to new firmware (in the middle of the night during off hours), diagnose problem devices, run performance metrics. We all have networks, we just don't have resources to test your firmware for you. I feel there are a lot of issues that Ubnt would catch en-vivo this ways. For example, the ToughSwitch-pro fiasco, or the Edgemax hardware acceleration reboots. Whatever field testing you are doing its not enough. Help us out, and you can more fields than you can imagine. Colin On Oct 27, 2014 9:02 PM, "Colin Zwiebel" < [email protected] > wrote: <blockquote> <rant> Ubnt now has a market cap of 3.04 Billion USD. You have the resources, it seems test engineers should be finding these problems, not me. Same applies to ToughSwitch-Pro microburst performance problems and EdgeMax Lite IP offload (that crashes all Edgemax that touch vlans, even if VLAN acceleration is disabled). </rant> Colin net Blazr - free your broadband! The wireless telegraph is not difficult to understand. The ordinary telegraph is like a very long cat. You pull the tail in New York, and it meows in Los Angeles. The wireless is the same, only without the cat. On Mon, Oct 27, 2014 at 8:57 PM, Colin Zwiebel < [email protected] > wrote: <blockquote> We are having serious problems with v5.5.10 with 5GHz XM hardware and have decided this firmware is not production ready. We using v5.5.10 only for links that require UNII-1 frequencies and avoiding in all other situations. There is some sort of a bug with scanning for available networks, so if your area has few networks, you might observe different behavior. http://community.ubnt.com/t5/Installation-Troubleshooting/v5-5-10-major-bug-no-SSIDs-in-scan-print-scanning-info-buffer/m-p/1072997#U1072997 AirOS v5.5.10 is not production ready! Ubiquiti, it appears you have a major bug and need to revoke the release, remove from website, until you get this fixed. We have now had 3 clients -- 2 Nanobridges and 1 Rocket M5 -- disconnect from their AP with the same behavior: NO SSIDs appear in scan list. Downgrade to v5.5.8, no changes to config, radio once against sees SSID and connects perfectly. Workaround: Frequency Scan List I cannot fully confirm this, but it appears, v5.5.10 plus frequency scan list has this problem less. It also might be that this pares down the amount of data coming from the atheros driver (by not scanning all frequencies), and scan list doesn't actually fix the issue, just reduces the scan data to something that doesn't break the radio. iwlist ath0 scan -- print_scanning_info: buffer too large(65535) for realocating In our most recent incident, I was able to SSH into the failed v5.5.10 STA XM.v5.5.10# iwlist ath0 scan print_scanning_info: buffer too large(65535) for realocating XM.v5.5.10# wlanconfig ath0 list scan ioctl[unknown???]: Argument list too long wlanconfig: unable to get scan results We are running now with a frequency scan list (cannot downgrade this radio) and both iwlist and wlanconfig commands are working properly. More details: APs: Problem happens with both Nanostation M5 APs and PowerBridge-M5 APs - Seen with AP on v5.5.10 - Seen with AP on v5.5.8 STAs: Problem observed with NB-22-M5 and Rocket-M5 DFS: Problem observed on both DFS and non-DFS frequencies (5805) Most recent incident, Rocket was working fine for a few days, suddenly died. It rebooted in the process (only 2min uptime when I got to it). Let sit 10min, rebooted, made no difference, gave buffer too larger error no matter how many reboots. Only enabling scan list patched it. Colin net Blazr - free your broadband! The wireless telegraph is not difficult to understand. The ordinary telegraph is like a very long cat. You pull the tail in New York, and it meows in Los Angeles. The wireless is the same, only without the cat. </blockquote> _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users </blockquote> _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users </blockquote> _______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
