Distribute DHCP Leases Based on MAC Address
-
This post is deleted! -
How do you mean?
Centrally allocation a 1:1 IP to MAC via A DHCP server? Yes , I have used it that way and it works well (I didnt set it up though)
-
@JaredBusch does this for all his printers and other non server based devices.
Has the advantage of the ability to change settings on those devices remotely from DHCP if the need arises.
-
This is not a reservation, it assigns devices to a range based on the mac address of the device.
So, in my case I have 60 new grandsteam devices and I want them all in the 192.168.104.X range, I apply a filter (000B82*) and all grandsteam devices should go into that range.
Sadly, this range is not going to be router-able so I want only the grandsteam devices in that range
-
I would never do this because if you're going to go to the range just assigned a reservation
-
@JaredBusch Huh?
-
What do you mean by router-able?
Are you trying to apply security to these devices?
From the looks of it, you are looking to put multiple IP ranges all on the same VLAN (this might be the wrong term in this use, but I don't have a better one at the moment).
What is the goal with these devices?
-
@Dashrender We are a global company. 192.168.104.X is already used by another location. The power at be have decided to extend our range, however it will only work at this location. It will be unreachable, from other locations.
-
@aaronstuder said:
@Dashrender We are a global company. 192.168.104.X is already used by another location. The power at be have decided to extend our range, however it will only work at this location. It will be unreachable, from other locations.
Intentionally, you mean?
-
@scottalanmiller Correct.
-
This post is deleted! -
wow, hope no one on your network ever needs to reach the other 192.168.104.x network.
any reason you can't just add a completely new network to your local setup to prevent the overlap?
-
But back to the OP.
OK so it sounds like you need multiple subnets to exist on a single collision domain network (VLAN). I can see your using this DHCP method to assign those devices to that specific IP range.
It's no different than Network Access Control (NAC) using it to assign a machine to a specific IP range.
-
@Dashrender I wanted to just move to a completely new range... but it's not my call.
-
@aaronstuder said:
@Dashrender I wanted to just move to a completely new range... but it's not my call.
sure, but that's not always that easy. My question is, why are they overlapping with another pre-existing subnet?
As long as you have a router in house, and can connect whatever devices will be on the new range to that router, you can create any new subnet you want.
Heck, you're going to have to do that anyway, unless the new subnet isn't going to talk to the devices on your current subnet.
-
@aaronstuder said:
This is not a reservation, it assigns devices to a range based on the mac address of the device.
So, in my case I have 60 new grandsteam devices and I want them all in the 192.168.104.X range, I apply a filter (000B82*) and all grandsteam devices should go into that range.
Sadly, this range is not going to be router-able so I want only the grandsteam devices in that range
This really just allows them to get a dhcp address. For example we dump all company owned devices in the allow. And block some other stuff. But reservations are only for servers printers etc
-
@aaronstuder said:
@Dashrender We are a global company. 192.168.104.X is already used by another location.
Doesn't sound like much of a global company to me if they are overlapping subnets. Seems pretty careless. Bad idea incase something does need to talk, and also one routing BGP advertisement mistake away from causing a lot of issues.
And let's not get started on NAT translation for it, that's a bad idea too
