I'm obviously not understanding how DHCP v4 Pools work.
Subnet: 192.168.0.0
Subnet Mask: 255.255.0.0
Range: 192.168.1.50 to 192.168.1.254
Additional Pools:
- 192.168.240.0 192.168.254.0 Home Automation Devices
- 192.168.0.100 192.168.0.254 Network Devices
The main range does not have any MAC address control.
Within the additional pools, I've checked
Deny unknown clients, and set up a list of partial MAC addresses (e.g. A8:BB:50,6C:29:90,CC:A7:C1) to allow particular types of devices to be allocated to those pools.
I had assumed this would mean that any device with a matching MAC prefix would be allocated from the appropriate pool, and that anything else would be allocated from the main range. But everything is being allocated from the main range and nothing from the pools.
Am I misunderstanding how this is supposed to work? Am I doing something wrong?
This was happening on 23.1 and is still occurring after upgrade to 23.7.
Thank you for any assistance.
You need Subnet Mask: 255.255.255.0
For additional pools modify the 3rd octet, you can keep the same mask there
Home Automation Device -- 192.168.2.0 subnet mask /24 ( 255.255.255.0 )
Another VLAN -- 192.168.3.0 subnet mask /24 ( 255.255.255.0 )
For LAN you can keep the default 192.168.1.0 subnet mask /24 and specify the range or the pool from 192.168.1.50 to 192.168.1.254
What do you mean by "Pool"? The entries of additional ranges follow the same logic as the initial address range.
Either you start using different VLANs to obtain different IP ranges for different devices - or you may want to have a look at static IP leases. However, make sure those static leases are not part of any defined DHCP range.
Thank you. I didn't realise how closely tied the LAN/VLAN definitions are with the DHCP server.
When I tried this I ended up not giving out any DHCP leases. I want to experiment more before asking for further help, so I can provide a clear example of what I tried to do.
Quote from: newsense on August 20, 2023, 08:23:11 PM
You need Subnet Mask: 255.255.255.0
For additional pools modify the 3rd octet, you can keep the same mask there
Home Automation Device -- 192.168.2.0 subnet mask /24 ( 255.255.255.0 )
Another VLAN -- 192.168.3.0 subnet mask /24 ( 255.255.255.0 )
For LAN you can keep the default 192.168.1.0 subnet mask /24 and specify the range or the pool from 192.168.1.50 to 192.168.1.254
By "Pool" I meant the additional Pools under the DHCP server. However, I'm seeing they don't work as I had assumed. It seems like defining VLANs is the way to go. Now I just need to get that to work.
Thank you.
Quote from: tron80 on August 21, 2023, 10:07:52 AM
What do you mean by "Pool"? The entries of additional ranges follow the same logic as the initial address range.
Either you start using different VLANs to obtain different IP ranges for different devices - or you may want to have a look at static IP leases. However, make sure those static leases are not part of any defined DHCP range.