@Jason said:

@Dashrender said:

@Jason said:

@Dashrender said:

the problem with moving it is that the APs only want to talk to the device that activated them. At least by DNS name if not by IP. So if you restore to a new machine with a different IP, you'll have to change DNS at least, if not manually reset all APs and import them again.

I'm pretty sure you can telnet or SSH into them and change it. Pretty sure I've done it before.

Yeah I suppose, I tried today but it would not accept my password. I should try again when I'm not under the gun.

Jason, do you understand that it is the same password you use for the controller?

No, It's been a while since I've used them but it was under settings on the controller you set a device password. otherwise it's likely just ubnt/ubnt for the user/pass of the AP.

Yeah I saw that are, on phone now, and I recall seeing my username in there, but the password was started out.

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

hell, forget windows. Let's look at phones! Android phones rare ever get patched. A hardware firewall in front of them seems very smart!

If you are concerned with security to the point that you are carrying hardware to put in front of your phone, wouldn't you more likely just get an iPhone?

The article implied that iPhones were just as easy to force to his AP as Windows or Android devices.

The point was that they are patched regularly. The carriers can't block it and Apple really annoys people who hold back. Apple takes security seriously in a way that Google cannot because of how they treat the ecosystem and carriers.

Google capitualated, Apple didn't. Apple said - you want our phone, you'll do it our way.

The carriers told Samnsung, LG, HTC, etc (I'm sure Google wasn't even part of it) you want us to carry your phones, you'll do it our way, or we'll find someone who will.

Yup, leaving Apple with a stronger security hand.

@coliver said:

@DustinB3403 said:

Gone are the days when you could go into CompUSA and pick up a part like this, unless you guys have a few cards around the office or have a few connections to get equipment to set this up...

Seems like a few more days before this'll be up.

Especially since it is a holiday week.

Nahh, Just order them off Amazon with Prime.

Everything that you are doing sounds logical and makes sense to me. I'm pretty confident you are not going to hurt anything here. Will it help dramatically? No idea there. But I think it is likely to help without much risk. Seems like a good idea.

If you have the dough to spend, Aerohive is really good stuff. Maybe I just like the platform better, but I see now that UBNT has upgraded UniFi, so I might need to thoroughly check it out before I commit to that statement. I just installed the new UniFi tonight because I saw this topic and wanted to check my config before commenting at all. If you want to do it on a budget, but not compromise the quality of the hardware then id go with the UBNT AP like @scottalanmiller suggested. Also I dont really bother with AC at this point because hardly any of my devices support it anyway, and I don't need those transfer speeds.

Keep in mind however ( not that this is a problem on my home network ) I think I recall reading some restrictions on those UBNT AP's. There was and may still be a hard limit of 127 devices per radio ( 127 @ 2.4 and 127 @ 5). In the forums people commented on a soft limit of 32 devices per AP, but I cannot attest to that having any accuracy. I don't know if you still need to configure wLAN groups for ZH (Zero Hand-off) to work, but it used to be that way for sure. Also there was a bug if you had the heartbeat checkbox enabled on the AP, MAC computers would randomly disconnect.

As far as switches go I really dont mind using inline adapters and barrel plugs with ac adapters. Id rather see one inline adapter fail than an entire POE switch, personally. This is really something you need to evaluate yourself.

I dont particularly like using Out-of-the-Box guest network configuration on UBNT equipment. My preference is to configure my own vLAN's and firewall rules. Last I knew you could have 4 SSID per AP, so I configure three. One for the managed network devices, one of personal devices and one for guests. Each SSID can be tied to a vLAN ID and you can introduce bandwidth policing at the SSID level. In my case, the managed network would be uncapped, the personal devices would have a minor cap, and guest networking would be "usable for general purposes". In the firewall I would isolate all three networks and block communication between them.

Anyway... that is my experience with these things. Hope at least one thing I mentioned helps you.

thx
-d

@Jason said:

Nevermind. #faceplam. forgot to go into configure mode first..

I may or may not have done that more than once.

@Dashrender said:

If they are all on the same controller, why does rebooting affect the others? Isn't the controller suppose to managing that?

The point of auto is to have the AP detect what channels are in use around it and pick the best one. That will obviously be different each time any AP reboots. When the first one reboots, it will immediately affect the ones next to it as the signal drops and the unit around it detect a difference. Then once it powers back on, it has to detect what is around it and then determine what channel to use.

High density deployments are much different beasts than an office building with 3 or 4 AP scattered around for coverage.

Connected again after defaulting the NVR again.

I have the cameras 'adopted' but they are showing disconnected still....

@johnhooks said:

@JasonNM @JaredBusch I wasn't saying I had one or wanted one. I just wondered how the new AP's compared to the old ones in terms of range.

Range is just important to consider in different context. The range of the AP isn't the same as the useful range, which is determined by the AP, the client and the environment together.

MPLS capable - that will be interesting!

If it is a very specific ad that is an issue, you might want to consider blocking it manually either via IP at the router or via DNS or something similar.

Tryin arping it.

http://www.netscantools.com/nstpro_arpping.html

@JaredBusch said:

Requires DD-WRT professional subscription if I understand how DD-WRT works..

Ahhh too bad

Good night.

@Dashrender said:

@JaredBusch - What do you think of the USG? What size deployments have you seen it in? have you setup VPN between two or more USG's?

I have never used the USG yet.

@g.jacobse said:

For giggles I watch my UBNT router Traffic Analysis during the day.

Mine is boring since the upstream is going through a traffic shaper and thus not offloaded, which makes the new traffic analysis less fun.

Giggles and Spice - Could be a issue with the firmware
https://community.ubnt.com/t5/UniFi-Wireless/clients-complain-about-dropping-from-connecting-to-unifi-ap-lr/m-p/480623#U480623

and that is what my vendor said - but then there is this vendor
http://www.balticnetworks.com/ubiquiti-unifi-switch-48-port-poe-switch-750w.html

who indicates on their site that it does support Layer 3.

@art_of_shred said:

Thanks for the help, especially Chad. I doesn't seem very intuitive that you can take a brand new device out of the box, install it, connect it to the (very basic) network, download the controller, see that the controller sees it on the network, see the solid LED display on the device that says it's working properly on the network, and then be required to reset it to factory settings to get it to automatically work perfectly. What about the settings was not "factory" when I took it out of the box 5 minutes ago???

Likely a returned unit.. Maybe a QC unit that didn't get reset after testing.