Project

General

Profile

Actions

Bug #13466

closed

dhcp server with static mapping and aditional pools with "mac allow" list , dont work as expected.

Added by Alex Werle Baule about 3 years ago. Updated almost 3 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Hello !

Let me explain what occours.

When i set a static mapping, and set 2 or more pools and put a macaddr in the "Mac Allow" list, to force the client to fit in the correct pool allocation, this list is not respected.
Looking to the generated config file (/var/dhcpd/etc/dhcpd.conf), the (allow members of "s_lan";) is inserted in every pool that has the (deny unknown-clients;) enabled, causing a lease to be offer to a client in the wrong pool.
Maybe the static mapping must be by pool, not "general", to put the configuration of "s_lan" in the correct pool.

You can reproduce this bug , following this:

1 - create 2 pools (can be in the same network)
  pool-1: 192.168.0.2 - 192.168.0.10, mark "Deny unknown clients" to be "Allow known clients from only this interface".
  pool-2: 192.168.0.11 - 192.168.0.20, mark "Deny unknown clients" to be "Allow known clients from only this interface".

2 - create a static mapping of a macaddr/hostname (don't give a IP, to stay inside the pool).
3 - inside pool-2, add a Macaddr in "MAC Allow" (the MAC that will be used in the test).
4 - Put the device with the Mac assigned in step 3 in the Network, with dhcpclient enabled.

The Pool associated will not be respected.

The only way that is respected, is doing a "MAC Deny" association in the inverse pool.
To this work in this test, you need to add the Macaddr in step 3, inside "MAC Deny" in pool-1.

Actions

Also available in: Atom PDF