Clients getting dynamic leases instead of fixed addresses.
Sten Carlsen
stenc at s-carlsen.dk
Tue Sep 23 18:44:38 UTC 2014
On 23/09/14 15:06, Eugène Ngontang wrote:
> Hi,
>
> My dhcod.conf file :
>
> /*
> */
> /*# DHCP Server Configuration file.*/
> /*# see /usr/share/doc/dhcp*/dhcpd.conf.sample */
> /*#*/
> /*ddns-update-style interim;*/
> /*ignore client-updates;*/
> /*subnet X.X.X.0 netmask 255.255.255.0 {*/
> /*option routers X.X.X.1;*/
> /*option subnet-mask 255.255.255.0;*/
> /*option nis-domain "jcd.priv";*/
> /*option domain-name "fr.jcdecaux.org
> <http://fr.jcdecaux.org>";*/
> /*option domain-name-servers X.X.X.11, X.X.X.10, 10.231.2.3,
> 10.232.2.3;*/
> /*range X.X.X.100 X.X.X.200;*/
> /**/
> /*default-lease-time 21600;*/
> /*max-lease-time 43200;*/
> /*}*/
> /*
> */
> /*# create as hosts as players*/
> /*
> */
> /*host CN-SHT-LX001 { hardware ethernet 00:01:80:81:d2:e1;
Apart from the commenting out of the lines, the HW address must start
with an additional 1: when they are ethernet addresses like this:
host CN-SHT-LX001 { hardware ethernet 1:00:01:80:81:d2:e1;
fixed-address X.X.X.15; }
> fixed-address X.X.X.15; }*/
> /*host CN-SHT-LX002 { hardware ethernet 00:01:80:81:d2:ad;
> fixed-address X.X.X.16; }*/
> /*host CN-SHT-LX003 { hardware ethernet 00:01:80:81:d2:da;
> fixed-address X.X.X.17; }*/
> /*host CN-SHT-LX004 { hardware ethernet 00:01:80:81:d2:36;
> fixed-address X.X.X.18; }*/
> /*host CN-SHT-LX005 { hardware ethernet 00:01:80:81:d2:de;
> fixed-address X.X.X.19; }*/
> /*host CN-SHT-LX006 { hardware ethernet 00:01:80:81:d2:d5;
> fixed-address X.X.X.20; }*/
> /*host CN-SHT-LX007 { hardware ethernet 00:01:80:81:d2:d0;
> fixed-address X.X.X.21; }*/
> /*host CN-SHT-LX008 { hardware ethernet 00:01:80:81:d2:5b;
> fixed-address X.X.X.22; }*/
> /*host CN-SHT-LX009 { hardware ethernet 00:01:80:81:d2:00;
> fixed-address X.X.X.23; }*/
> /*host CN-SHT-LX010 { hardware ethernet 00:01:80:81:d2:cc;
> fixed-address X.X.X.24; }*/
> /*host CN-SHT-LX011 { hardware ethernet 00:01:80:82:4d:66;
> fixed-address X.X.X.25; }*/
> /*host CN-SHT-LX012 { hardware ethernet 00:01:80:81:89:05;
> fixed-address X.X.X.26; }*/
> /*host CN-SHT-LX013 { hardware ethernet 00:01:80:81:d2:57;
> fixed-address X.X.X.27; }*/
> /*host CN-SHT-LX014 { hardware ethernet 00:01:80:81:d2:bc;
> fixed-address X.X.X.28; }*/
> /*host CN-SHT-LX015 { hardware ethernet 00:01:80:81:d2:a6;
> fixed-address X.X.X.29; }*/
> /*host CN-SHT-LX016 { hardware ethernet 00:01:80:81:d2:2e;
> fixed-address X.X.X.30; }*/
> /*host CN-SHT-LX017 { hardware ethernet 00:01:80:81:d2:ac;
> fixed-address X.X.X.31; }*/
> /*host CN-SHT-LX018 { hardware ethernet 00:01:80:81:d2:5e;
> fixed-address X.X.X.32; }*/
> /*host CN-SHT-LX019 { hardware ethernet 00:01:80:81:d1:fb;
> fixed-address X.X.X.33; }*/
> /*host CN-SHT-LX020 { hardware ethernet 00:01:80:81:d2:e2;
> fixed-address X.X.X.34; }*/
> /*host CN-SHT-LX021 { hardware ethernet 00:01:80:81:d2:d9;
> fixed-address X.X.X.35; }*/
> /*host CN-SHT-LX022 { hardware ethernet 00:01:80:81:4c:de;
> fixed-address X.X.X.36; }*/
> /*host CN-SHT-LX023 { hardware ethernet 00:01:80:81:d2:d4;
> fixed-address X.X.X.37; }*/
> /*host CN-SHT-LX024 { hardware ethernet 00:01:80:81:d2:52;
> fixed-address X.X.X.38; }*/
> /*host CN-SHT-LX025 { hardware ethernet 00:01:80:81:d2:b7;
> fixed-address X.X.X.39; }*/
> /*host CN-SHT-LX026 { hardware ethernet 00:01:80:81:d2:a7;
> fixed-address X.X.X.40; }*/
> /*host CN-SHT-LX027 { hardware ethernet 00:01:80:81:ac:47;
> fixed-address X.X.X.41; }*/
> /*host CN-SHT-LX028 { hardware ethernet 00:01:80:81:d2:58;
> fixed-address X.X.X.42; }*/
> /*host CN-SHT-LX029 { hardware ethernet 00:01:80:81:d2:53;
> fixed-address X.X.X.43; }*/
> /*host CN-SHA-LX030 { hardware ethernet 00:01:80:81:d2:ba;
> fixed-address X.X.X.44; }*/
> /*host CN-SHA-LX031 { hardware ethernet 00:01:80:81:d2:5a;
> fixed-address X.X.X.45; }*/
> /*host CN-SHA-LX032 { hardware ethernet 00:01:80:81:d2:35;
> fixed-address X.X.X.46; }*/
> /*host CN-SHA-LX033 { hardware ethernet 00:01:80:81:d2:db;
> fixed-address X.X.X.47; }*/
> /*host CN-SHA-LX034 { hardware ethernet 00:01:80:81:d2:87;
> fixed-address X.X.X.48; }*/
> /*host CN-SHA-LX035 { hardware ethernet 00:01:80:81:d2:0b;
> fixed-address X.X.X.49; }*/
> /*host CN-SHA-LX036 { hardware ethernet 00:01:80:81:d2:77;
> fixed-address X.X.X.50; }*/
> /*host CN-SHA-LX037 { hardware ethernet 00:01:80:81:d2:03;
> fixed-address X.X.X.51; }*/
> /*host CN-SHA-LX038 { hardware ethernet 00:01:80:82:4d:13;
> fixed-address X.X.X.52; }*/
> /*host CN-SHA-LX039 { hardware ethernet 00:01:80:82:4d:17;
> fixed-address X.X.X.53; }*/
> /*host CN-SHA-LX040 { hardware ethernet 00:01:80:82:4d:76;
> fixed-address X.X.X.54; }*/
> /*host CN-SHA-LX041 { hardware ethernet 00:01:80:82:4d:50;
> fixed-address X.X.X.55; }*/
> /*host CN-SHA-LX042 { hardware ethernet 00:01:80:82:4d:65;
> fixed-address X.X.X.56; }*/
> /*host CN-SHA-LX043 { hardware ethernet 00:01:80:82:4d:a8;
> fixed-address X.X.X.57; }*/
>
>
> Thanks.
>
> Regards,
> Eugène NG
>
> 2014-09-23 11:34 GMT+02:00 Sten Carlsen <stenc at s-carlsen.dk
> <mailto:stenc at s-carlsen.dk>>:
>
> I have this setup working, I only have to restart the server to get it
> to use the new configuration, I have never had any of those problems you
> describe.
>
> I agree it must be a configuration mistake.
>
>
> On 23/09/14 10:13, Niall O'Reilly wrote:
> > At Tue, 23 Sep 2014 09:25:04 +0200,
> > Eugène Ngontang wrote:
> >>
> >> In fact in my dhcp server configuration I have a dynamic range and
> >> fixed addresses.
> >>
> >> When I add a new fixed host with MAC address and the associates IP
> >> address, and start the client, it picks an ip address from the
> dynamic
> >> range instead of the ip address I have fixed.
> >>
> >> To fixe that, I have to comment the dynamic range in the server
> >> configuration file, suppress the lease file in the client side and
> >> restart dhclient or reboot the client.
> >>
> >> Why it works like this? I thought the static leases wins dynamics
> one.
> >>
> >> How to avoid my news clients picking addresses from the dynamic range
> >> addresses?
> >
> > This is most likely due to a configuration error.
> >
> > If you post your dhcpd.conf file, I or someone else on the list
> > may be able to find what's wrong and explain.
> >
> > Best regards,
> > Niall O'Reilly
> > _______________________________________________
> > dhcp-users mailing list
> > dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
> > https://lists.isc.org/mailman/listinfo/dhcp-users
> >
>
> --
> Best regards
>
> Sten Carlsen
>
> No improvements come from shouting:
>
> "MALE BOVINE MANURE!!!"
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
>
>
>
> --
> ngonta_e at epitech.net <mailto:ngonta_e at epitech.net>
> sympavali at gmail.com <mailto:sympavali at gmail.com>
> ------------------------------------------------------------
> /*Aux hommes il faut un chef, et au*//* chef il faut des hommes!
> L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!
> */
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
More information about the dhcp-users
mailing list