Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Only allow pool range nothing else (Marc Roos)
2. Re: Only allow pool range nothing else (Bill Shirley)
----------------------------------------------------------------------
Message: 1
Date: Wed, 21 Aug 2019 00:12:13 +0200
From: "Marc Roos" <m.r...@f1-outsourcing.eu>
To: dhcp-users <dhcp-users@lists.isc.org>
Subject: Only allow pool range nothing else
Message-ID: <"H00000710014cad4.1566339133.sx.f1-outsourcing.eu*"@MHS>
Content-Type: text/plain; charset="US-ASCII"
With this configuration a "testing" client can get an ip address
192.168.11.44. How can I make sure the clients identifying with
"testing" are only getting the ip addresses reserved in the pool (eg
192.168.11.43) and nothing else. So no ip adress should be issued when
the all ip addresses of the range have been already assigned.
subnet 192.168.11.0 netmask 255.255.255.0 {
#option routers 192.168.11.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.11.10,212.19.193.130;
#range 192.168.11.9 192.168.11.11;
pool { allow members of "testing"; range 192.168.11.43
192.168.11.43; }
deny unknown-clients;
}
------------------------------
Message: 2
Date: Tue, 20 Aug 2019 20:32:25 -0400
From: Bill Shirley <b...@c3po.polymerindustries.biz>
To: dhcp-users@lists.isc.org
Subject: Re: Only allow pool range nothing else
Message-ID:
<c1bb7ed8-c6a2-d394-e729-227d104fb...@c3po.polymerindustries.biz>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
You've only shown us one pool.? The other pools should have a line:
deny members of "testing";
Bill
On 8/20/2019 6:12 PM, Marc Roos wrote:
>
> With this configuration a "testing" client can get an ip address
> 192.168.11.44. How can I make sure the clients identifying with
> "testing" are only getting the ip addresses reserved in the pool (eg
> 192.168.11.43) and nothing else. So no ip adress should be issued when
> the all ip addresses of the range have been already assigned.
>
>
> subnet 192.168.11.0 netmask 255.255.255.0 {
> #option routers 192.168.11.1;
> option subnet-mask 255.255.255.0;
> option domain-name-servers 192.168.11.10,212.19.193.130;
>
> #range 192.168.11.9 192.168.11.11;
> pool { allow members of "testing"; range 192.168.11.43
> 192.168.11.43; }
> deny unknown-clients;
> }
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20190820/24467de7/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 130, Issue 17
*******************************************
