Busybox is just the shell/utility bundle for userland on embedded devices. Ubiquiti is built on OpenWRT and OpenWRT has had multi-SSID for ages. UniFi has multi-SSID so their toolchain has it/hardware supports it. My guess would be they see AirX as part of the AirMax development process and there's something in their custom drivers for AirMax that makes them not want to do it.
On Wed, Dec 31, 2014 at 4:30 PM, timothy steele via Af <af@afmug.com> wrote: > somthing newer then busybox linux had?> > > On Wed, Dec 31, 2014 at 4:24 PM, Mike Hammett via Af <af@afmug.com> wrote: > >> What kernel was Mikrotik using 10 years ago? >> >> >> >> ----- >> Mike Hammett >> Intelligent Computing Solutions >> http://www.ics-il.com >> >> ------------------------------ >> *From: *"timothy steele via Af" <af@afmug.com> >> *To: *af@afmug.com >> *Sent: *Wednesday, December 31, 2014 3:12:00 PM >> >> *Subject: *Re: [AFMUG] It's time for a second SSID on the Air Routers >> and Air Gateways. >> >> last I heard they needed to update the Kernal to get multi SSID's to work >> & I think they did not in 5.6Beta but I'm sure they want to get 5.6 Final >> out fast as they can Multi SSID's i'm sure will get more antenntion after >> 5.6 final is out its on beta6 right now.. >> >> On Wed, Dec 31, 2014 at 10:42 AM, That One Guy via Af <af@afmug.com> >> wrote: >> >>> UBNT amazes me with this, Im pretty sure the multi ESSID thread is the >>> longest running active thread on their forum, yet they cant do it. >>> Users have found ways to somewhat get it to happen, but not cleanly, but >>> they dont have programmatic access to the device >>> >>> I know this is not a complicated thing, almost every single wireless >>> product on the market these days supports it in some form or another. >>> >>> I could see hiding behind the "well, it wont work with our proprietary >>> wireless algorithm" I can see that on the commercial side, but the home >>> devices? I doubt anyone on this list is turning that on on airrouters or >>> gateways for customers since most customers end devices arent ubiquiti >>> products. >>> >>> I think they dont do it strictly out of spite now >>> >>> On Wed, Dec 31, 2014 at 7:55 AM, Mike Hammett via Af <af@afmug.com> >>> wrote: >>> >>>> They'll say, "We weren't aware anyone wanted that." That's what the >>>> vendors say when they don't want to actually tell us why they haven't done >>>> something. >>>> >>>> I haven't been too excited about multi-SSID in the macro network, but >>>> auto-associated and provisioned CPE would be nice. >>>> >>>> >>>> >>>> ----- >>>> Mike Hammett >>>> Intelligent Computing Solutions >>>> http://www.ics-il.com >>>> >>>> ------------------------------ >>>> *From: *"Mark Radabaugh via Af" <af@afmug.com> >>>> *To: *af@afmug.com >>>> *Sent: *Wednesday, December 31, 2014 7:53:17 AM >>>> *Subject: *Re: [AFMUG] It's time for a second SSID on the Air Routers >>>> and Air Gateways. >>>> >>>> >>>> Make that on all of the products. Two SSID’s on the AP - a ‘install’ >>>> SSID that the CPE can associate to by default, and a ‘sector’ SSID that we >>>> use to lock the CPE to the sector once it’s installed. >>>> >>>> What is so hard about this? Cisco Aironet AP's could do this 15 years >>>> ago. >>>> >>>> Mark >>>> >>>> On Dec 31, 2014, at 8:48 AM, joseph marsh via Af <af@afmug.com> wrote: >>>> >>>> +1 >>>> On Dec 30, 2014 11:29 PM, "Rory Conaway via Af" <af@afmug.com> wrote: >>>> >>>>> As much as I’d like to stay with those devices, lack of a second SSID >>>>> for guests for example, is becoming a problem. I had 3 people in the last >>>>> 2 weeks ask for this feature and I don’t disagree with them. Come on >>>>> guys, >>>>> we’ve been asking for this for 5 years. It’s time. >>>>> >>>>> >>>>> >>>>> Rory Conaway >>>>> Triad Wireless >>>>> 4226 S. 37th Street >>>>> Phoenix, Az. 85040 >>>>> 602-426-0542 >>>>> r...@triadwireless.net >>>>> www.triadwireless.net >>>>> >>>>> >>>>> >>>>> “Mediocrity finds safety in standardization. -- Frederick Crane” >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> All parts should go together without forcing. You must remember that the >>> parts you are reassembling were disassembled by you. Therefore, if you >>> can't get them together again, there must be a reason. By all means, do not >>> use a hammer. -- IBM maintenance manual, 1925 >>> >> >> >> >
