fixed-address problem

[Bernard Fay]

I just stopped banging my head against the wall..  Yes, a ..... typo!  It
should have been "fixed-address 192.168.99.101;"

Damn!

Thanks Sherman


On Tue, Jan 26, 2016 at 4:34 PM, Sherman Lilly <Sherman.Lilly at knoxcounty.org
> wrote:

> No problem. Typos are the root of all evil.
>
> Sherman Lilly
> (865) 215-3536
> Senior Systems Administrator
> Knox County
> ------------------------------
> *From:* dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org]
> on behalf of Patrick Trapp [ptrapp at nex-tech.com]
> *Sent:* Tuesday, January 26, 2016 4:30 PM
>
> *To:* Users of ISC DHCP
> *Subject:* RE: fixed-address problem
>
> Ah, since you called out the subnet, I looked at the subnet. Not the host
> address where the error appears to be. My apologies.
>
> ------------------------------
> *From:* dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org]
> on behalf of Sherman Lilly [Sherman.Lilly at knoxcounty.org]
> *Sent:* Tuesday, January 26, 2016 3:27 PM
> *To:* Users of ISC DHCP
> *Subject:* RE: fixed-address problem
>
> Your subnet clause is
>
> subnet 192.168.*99*.0 netmask 255.255.255.0 {
>
> Your fixed address is
>
> fixed-address 192.168.*98*.101;
>
> You can't service a subnet out side of the subnet in your declaration
>
>
> Sherman Lilly
> (865) 215-3536
> Senior Systems Administrator
> Knox County
> ------------------------------
> *From:* dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org]
> on behalf of Patrick Trapp [ptrapp at nex-tech.com]
> *Sent:* Tuesday, January 26, 2016 4:24 PM
> *To:* Users of ISC DHCP
> *Subject:* RE: fixed-address problem
>
> I don't see a problem with the subnet. OP just isn't using the entire
> pool, right?
>
> I'm not sure what the effect of the "group" declaration is. I believe on
> my configurations where I'm assigning a static address, I'm just using a
> "host" declaration. I don't declare these hosts within the subnet
> declaration, either. I would be inclined to try the host declaration
> outside the subnet first.
>
> ------------------------------
> *From:* dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org]
> on behalf of Sherman Lilly [Sherman.Lilly at knoxcounty.org]
> *Sent:* Tuesday, January 26, 2016 1:35 PM
> *To:* Users of ISC DHCP
> *Subject:* RE: fixed-address problem
>
> Your subnet is wrong
>
> Sherman Lilly
> (865) 215-3536
> Senior Systems Administrator
> Knox County
> ------------------------------
> *From:* dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org]
> on behalf of Bernard Fay [bernard.fay at gmail.com]
> *Sent:* Tuesday, January 26, 2016 2:30 PM
> *To:* dhcp-users at lists.isc.org
> *Subject:* fixed-address problem
>
> Hello everyonw,
>
> I am unable to assign fixed IP addresses to host.
>
> I have the following configuration:
>
> option domain-name "cts.org";
> option domain-name-servers ns1.cts.org;
>
> default-lease-time 300;
> max-lease-time 1500;
>
>
> subnet 192.168.99.0 netmask 255.255.255.0 {
>
> #  range 192.168.99.201 192.168.99.250;
>     option broadcast-address 192.168.99.255;
>     option routers 192.168.99.1;
>     option domain-name "cts.org";
>
>   group {
>     host vault {
>       option host-name "vault.cts.org";
>       hardware ethernet 52:af:12:cf:87:c5;
>       fixed-address 192.168.98.101;
>     }
>   }
> }
>
>
> With "range 192.168.99.201 192.168.99.250;"  the host is assigned the
> first available IP address. If I disable "range" like in the shown
> configuration, the log says: "dhcpd: DHCPDISCOVER from 52:af:12:cf:87:c5
> via eth1: network 192.168.99.0/24: no free leases".
>
> This ISC DHCP 4.2.5.
>
> What am I doing wrong?
>
> Thanks,
> Bernard
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at 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/20160126/73302b1a/attachment-0001.html>