Let me check on this :). Let me get update from SW team. Thanks, Ben
> On Jan 31, 2017, at 8:03 AM, Steve Barnes <st...@pcswin.com> wrote: > > They may monitor the list but Multiple SSID is not something they even hear > the need for when you talk to them in person. I personally have asked the > staff for this feature on and off for 6 years. Even watch Matt Hardy write > it down with an explanation as to how it could be helpful. He either lost > the paper or he threw it away when he left UBNT. > > Steve Barnes > Wireless Operations Manager > New Lisbon Broadband > NLBC.COM > PCSWIN.COM > 765-584-2288 ext:1101 > > -----Original Message----- > From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On > Behalf Of Kees H > Sent: Tuesday, January 31, 2017 9:58 AM > To: Ubiquiti Users Group <ubnt_users@wispa.org> > Subject: Re: [Ubnt_users] replacing rocket w/sector antenna AP > > Not in my book. We use frequency scan list to prevent any undesired > connection to the wrong AP. > Now dual SSID would be of great advantage. > The one thing I miss that the ole Alvarion equipment had. > You think UBNT is monitoring this list? > > > -----Original Message----- > From: Jay Weekley > Sent: Monday, January 30, 2017 8:11 PM > To: Ubiquiti Users Group > Subject: Re: [Ubnt_users] replacing rocket w/sector antenna AP > > Is there ever any advantage to using the "Lock to AP MAC" feature? > > Darin Steffl wrote: >> Don't ever use lock to ap Mac. Seen too many wisps roll trucks when >> they replace the ap. Every ssid should be different for every sector. >> >> Also for the client connecting to a weaker signal. That would be fixed >> as well if you connected to a specific ssid. >> On Mon, Jan 30, 2017 at 6:21 PM Jan-OOLLC <j.vank...@oregononline.net >> <mailto:j.vank...@oregononline.net>> wrote: >> >> Update, trying to balance the Rx dbm's at the AP first, by >> decreasing transmit power at the CPE. Noticed that one of the >> trouble CPEs was connecting to another tower with same name SSID >> even the the signal was 10 dbm weaker. So I figured if all the >> CPEs were configured to lock to the AP mac, they would transfer >> over to a new name for SSID. Ended up doing a lot of driving for >> orphans. Not one of them accepted the new name, all were set to >> "lock to AP" mac. I'm pretty sure with older firmware this used >> to work, is this a bug? >> >> Have tried airControl2 in the past, could not figure out how to >> add new CPEs after initial install. Dude is much easier to use. >> >> Jan >> >>> On 01/30/2017 12:03 PM, Nick Bright wrote: >>>> On 1/28/2017 11:43 AM, Chris Soiles wrote: >>>> I have replaced APs and just named them the same with same >>>> security and they just connect >>>> >>>> I.E.: had rocket with Omni named SSID: radio WPA2: 1234 >>>> >>>> Added a new section, installed 4 APs at New top, named all APs >>>> SSID: radio same WPA2 >>>> >>>> Turned off Omni AP >>>> >>>> As each CPE connected to new AP >>>> Login to CPE change SSID to New name for the radio >>>> >>>> Once all CPEs gone, change name of AP to New name, they all >>>> reconnect >>> That's what I do too. If things are working well, you could also >>> use airControl2 to do it by batch, but you need to ensure that >>> all the CPE have reliable connections and are responding properly >>> first, or they'll get orphaned. >>> >>> -- >>> ----------------------------------------------- >>> - Nick Bright - >>> - Vice President of Technology - >>> - Valnet -=- We Connect You -=- - >>> - Tel 888-332-1616 x 315 / Fax 620-331-0789 - >>> - Webhttp://www.valnet.net/ - >>> ----------------------------------------------- >>> - Are your files safe? - >>> - Valnet Vault - Secure Cloud Backup - >>> - More information & 30 day free trial at - >>> -http://www.valnet.net/services/valnet-vault - >>> ----------------------------------------------- >>> >>> This email message and any attachments are intended solely for the >>> use of the addressees hereof. This message and any attachments may >>> contain information that is confidential, privileged and exempt from >>> disclosure under applicable law. If you are not the intended recipient of >>> this message, you are prohibited from reading, disclosing, reproducing, >>> distributing, disseminating or otherwise using this transmission. If you >>> have received this message in error, please promptly notify the sender by >>> reply E-mail and immediately delete this message from your system. >>> >>> >>> _______________________________________________ >>> Ubnt_users mailing list >>> Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org> >>> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> _______________________________________________ >> Ubnt_users mailing list >> Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org> >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> -- >> Darin Steffl >> Minnesota WiFi >> www.mnwifi.com <http://www.mnwifi.com/> >> 507-634-WiFi >> <http://www.facebook.com/minnesotawifi> Like us on Facebook >> <http://www.facebook.com/minnesotawifi> >> >> >> _______________________________________________ >> Ubnt_users mailing list >> Ubnt_users@wispa.org >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> >> No virus found in this message. >> Checked by AVG - www.avg.com <http://www.avg.com/email-signature> >> Version: 2016.0.7998 / Virus Database: 4756/13866 - Release Date: 01/30/17 >> > > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org > http://lists.wispa.org/mailman/listinfo/ubnt_users > > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org > http://lists.wispa.org/mailman/listinfo/ubnt_users > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org > http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org http://lists.wispa.org/mailman/listinfo/ubnt_users
