SSH to the AP and add a secondary interface on 192.168.1.20 to the AP. (Or is that already there? I forget if we added that manually or not....) In any case you need a IP address at the AP on the UBNT default subnet.
Then SSH forward to the CPE: ssh admin@theap-name -L 8088:192.168.1.20:80 ssh admin@theap-name -L 8089:192.168.1.20:443 You can then reach a defaulted CPE at http://localhost:8088 <http://localhost:8088/> or https://localhost:8089 <https://localhost:8089/> in your web browser This method still requires sending the CPE out the door with the correct wifi settings and SSID. Multiple SSID support at the AP's would make this much easier but AFAIK UBNT has not gotten around to adding that. The ability to set a 'install' SSID on all of the AP's that the default CPE can connect to until we switch the CPE to the proper runtime SSID would have been helpful. Mark > On Dec 18, 2014, at 8:18 AM, Josh Luthman via Af <[email protected]> wrote: > > How are you doing it with Ubnt? Can't the same be done with epmp? > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Dec 18, 2014 8:06 AM, "Mark Radabaugh via Af" <[email protected] > <mailto:[email protected]>> wrote: > For our install method proxy access (or some means of remote access to a > minimally configured CPE) is a must have. The installers do NOT have to get > out a computer or otherwise access the device. Power it up, point it at the > tower, listen for signal, call the office for a signal quality check and go. > Everything regarding CPE programming can be done remotely. > > This can be done with Ubnt as well by SSH to the AP's and then to the CPE but > it's not as clean as Canopy. > > No way at all that I know of with ePMP. > > Mark > > >> On Dec 17, 2014, at 11:04 PM, Steve D via Af <[email protected] >> <mailto:[email protected]>> wrote: >> >> Use it all the time. Between it and installer color code field techs can't >> FUBAR an install. When our larger networks were vlan'd years ago that made >> the process super safe. >> >> One of the "best features" of the canopy platform in my book. It annoys me >> working on 802.11 crap when I see a tech has typo'd something like an IP or >> vlan. >> >> On Dec 17, 2014 7:30 PM, "Bill Prince via Af" <[email protected] >> <mailto:[email protected]>> wrote: >> Me too. >> >> I don't know how many times I've used it, but it's more than I have finger >> to count on. >> >> -- >> bp >> <part {dash} 15 {at} SkylineBroadbandService {dot} com> >> >> On 12/17/2014 7:08 PM, George Skorup (Cyber Broadcasting) via Af wrote: >>> No, rather just have it. >>> >>> On 12/17/2014 9:07 PM, Josh Luthman via Af wrote: >>>> Rather have it and not need it then need it and not have it. >>>> >>>> Josh Luthman >>>> Office: 937-552-2340 <tel:937-552-2340> >>>> Direct: 937-552-2343 <tel:937-552-2343> >>>> 1100 Wayne St >>>> Suite 1337 >>>> Troy, OH 45373 >>>> >>>> On Dec 17, 2014 9:55 PM, "Mike Hammett via Af" <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> I used it a couple times on my Canopy gear, but it was never a >>>> show-stopper to not have it. >>>> >>>> This brings me to a new post... >>>> >>>> >>>> >>>> ----- >>>> Mike Hammett >>>> Intelligent Computing Solutions >>>> http://www.ics-il.com <http://www.ics-il.com/> >>>> >>>> From: "George Skorup (Cyber Broadcasting) via Af" <[email protected] >>>> <mailto:[email protected]>> >>>> To: [email protected] <mailto:[email protected]> >>>> Sent: Wednesday, December 17, 2014 8:30:14 PM >>>> Subject: [AFMUG] ePMP proxy >>>> >>>> OK Cambium ePMP dudes and chicks, I am disappointed. I thought you guys >>>> had Canopy-like SM "click-thru" access, aka LUID proxy. But this is not >>>> the case on 2.3.3. All you give me is a URL with the IP of the SM. >>>> Informational helpful, yes, operationally helpful, no. >>>> >>>> I'm guessing you need an RF private network like exists on Canopy to >>>> make this work. Please do it. >>>> >>> >> >
