• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Unifi Question

J

jtr8178

Limp Gawd
Joined
Jun 21, 2008
Messages
266
I'm looking to deploy my first Unifi wireless network here at work... Probably looking at 5 devices. My question is this: Does the software on these devices allow you to specify an IP range for clients connecting to it, or am I tied into the IP address range of the wifi access point?

My problem is that I've pretty much exhausted our current IP range for wired devices, and we're under contract with a vendor until the fall for our main networking equipment... So I'd like to avoid getting them involved, since it takes them 4-6 weeks to get around to network configuration changes.

I downloaded the unifi software, plus browsed some of the manuals, but I can't find this info. Thank you in advance!
 
Generally speaking your router, or rather your DHCP server does your DHCP range, whether that`s on your router or not, I dunno....
 
Sounds like you would need to setup a DHCP server then for your wireless devices. Unifi doesn't do this but if you build out a VM or physical machine to run the controller service then you could load a DHCP client onto it. You should use VLAN's to separate the traffic of your wired static clients and your wireless dhcp clients.
 
It doesn't block out-of-subnet IP addresses, if that's what you're asking.

If you're out of IP addresses in your current range, and can't open it up any further, sounds like you'll need a router to connect to a new subnet. You can't just start assigning 192.168.1/24 addresses if the rest of your network is 192.168.0/24 unless you have a router between those subnets.
 
Any reason why you use static IP's.. sounds like a management nightmare if your a company.

DHCP server makes life so much easier for managing a network, you could still do static IP's but why bother when you can just reserve IP's in your DHCP server and never have to touch a computers NIC properties again.
 
Yes, it is a management nightmare that I inherited ... All will be changed once this stupid contract is up .. Hard to work around it in the meantime.

I was hoping these things work work like a home-brew version where they create their own 192.168.0.xxx range ... guess now, ah well. I'll have to get with our vendor and create a new VLAN for PCs.
 
Just get a home router and set it up between your wireless and wired networks and either let it NAT or route, and let it do the DHCP until your contract is up
 
Look at a Unifi or most APs as being a switch. It's like taking a switch and plugging it into your existing switch and plugging other devices into it, except it's done through wireless (and it's actually more like a hub). Basically the AP will not do any DHCP or any such protocol, it's basically working at the ethernet level, more or less.

You'll need to setup a DHCP server, or make the wireless devices static too. DHCP would be better. In fact you are better off having DHCP across the board, if you want a static, you do it by mac.
 
You must log in or register to reply here.
Back
Top