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. Re: dns setting for client (Simon Hobson)
   2. Re: strange behavior of shared network (Sten Carlsen)
   3. Re: strange behavior of shared network (Simon Hobson)
   4. Re: strange behavior of shared network (Sten Carlsen)


----------------------------------------------------------------------

Message: 1
Date: Fri, 04 Oct 2019 13:29:48 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: dns setting for client
Message-ID: <53e14fde-0110-4a0d-a0a7-453b6b251...@thehobsons.co.uk>
Content-Type: text/plain; charset=utf-8

Julie Xu <j...@westernsydney.edu.au> wrote:

>We have changed DNS server, and on dhcpd.conf I did change the dns to
>new server, but, on the client site, if you do ipconfig/all, you can
>see the dns is still pointed older dns server, if there is possible to
>on dhcpd.conf to force dns server change?

As soon as you have updated the server, it will start serving the new 
information. However, it's a pull transfer and relies on the client to ask for 
it. By the end of your max-lease-time setting, you can guarantee that there are 
no active leases that we're given with the old settings.

However, I vaguely recall some discussion in the past related to clients that 
didn't update settings when renewing an active lease. I don't know whether your 
clients fall into that group.

As already said, manually releasing and then renewing the lease at the client 
end should do it. Or just wait...

A brute force method would be to change your IP range and force clients to get 
a new lease. Add a new range, set the old one to "deny booting", and then tne 
server will Nack any renewal requests for the old addresses.  This will break 
all existing connections.


------------------------------

Message: 2
Date: Fri, 4 Oct 2019 16:18:59 +0200
From: Sten Carlsen <st...@s-carlsen.dk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: strange behavior of shared network
Message-ID: <e1fd3729-552f-4300-a344-6cf846e02...@s-carlsen.dk>
Content-Type: text/plain; charset="utf-8"


-- 
Best regards 
Sten Carlsen


"No trees were killed in the making of this e-mail... however,
a large number of electrons were terribly inconvenienced."

> On 4 Oct 2019, at 13.04, Milan Kovac <kova...@gmail.com> wrote:
> 
> I think I found the problem.
> 
> There can not be defined range in subnet which is for static clients.
Well, no.

My shared network has:
192.168.16.0/24 - one single network segment
192.168.16.1 - 192.168.16.30 - static and fixed allocations
192.168.16.31 - 192.168.16.49 - static allocations
192.168.16.50 - 192.168.16.150 - class based allocation - NO router given, no 
internet access
192.168.16.160 - 192.168.16.195 - class based allocation - router given
192.168.16.200 - 192.168.16.254 - static and fixed allocations

192.168.161.0/24 - for unknown clients until they get a fixed address or are 
put into a class
192.168.161.100 - 192.168.161.150 - only unknown clients

This works fine.

Looking at the data you give, I see no conflict. Can you be more specific about 
the problem?

> 
> I will test it more deeply and will give results.
> 
> In any case, thanks a lot for ideas.
> 
> Milan
> 
> D?a 2. 10. 2019 o 21:50 Simon Hobson nap?sal(a):
>> Milan Kovac <kova...@gmail.com> wrote:
>> 
>>> I have a few routed networks each with 2 subnets ( public and private )
>> ...
>> 
>> 
>>> Here is dhcpd.conf
>> ...
>>> shared-network 001 {
>>> default-lease-time 43200;
>>> max-lease-time 43200;
>>> # divina-private
>>> subnet 10.64.0.0 netmask 255.255.240.0 {
>>>         option broadcast-address 10.64.15.255;
>>>         option subnet-mask 255.255.240.0;
>>>         option routers 10.64.0.1;
>>>         range 10.64.0.2 10.64.15.254;
>>>         }
>>> 
>>> # divina-public
>>> subnet 157.157.56.128 netmask 255.255.255.240 {
>>>         option broadcast-address 157.157.56.143;
>>>         option subnet-mask 255.255.255.240;
>>>         option routers 157.157.56.129;
>>>         deny unknown-clients;
>>>         range 157.157.56.130 157.157.56.142;
>>>     host Divinka-Uhliarik {
>>>                         hardware ethernet cc:2d:e0:3f:fa:42;
>>>                         fixed-address 157.157.56.130;
>>>                         }
>>>     host Divinka-Obecny-Urad {
>>>                         hardware ethernet 00:4f:74:31:b4:03;
>>>                         fixed-address 157.157.56.131;
>>>                         }
>>>                 }
>>> }
>> You need to fix this to start with.
>> Host statements must always be defined in the global scope - they cannot be 
>> defined in a lower scope as you have done here. Wherever you define them, 
>> they are always global in scope - but they can inherit options from where 
>> there are defined. This is almost certainly not what you want.
>> 
>> So I suggest you fix this first and if the problem persists, then we can try 
>> and diagnose it.
>> 
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users@lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> 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/20191004/99361815/attachment-0001.html>

------------------------------

Message: 3
Date: Fri, 4 Oct 2019 20:42:04 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: strange behavior of shared network
Message-ID: <adf0555a-2b8a-4db7-bf9e-d2152c0b9...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii

Sten Carlsen <st...@s-carlsen.dk> wrote:

> Looking at the data you give, I see no conflict. Can you be more specific 
> about the problem?

You can't see it when it's been pointed out ?

>>>> subnet 157.157.56.128 netmask 255.255.255.240 {
>>>>         option broadcast-address 157.157.56.143;
>>>>         option subnet-mask 255.255.255.240;
>>>>         option routers 157.157.56.129;
>>>>         deny unknown-clients;
>>>>         range 157.157.56.130 157.157.56.142;
                    ^^^^^^^^^^^^^^
>>>>     host Divinka-Uhliarik {
>>>>                         hardware ethernet cc:2d:e0:3f:fa:42;
>>>>                         fixed-address 157.157.56.130;
                                            ^^^^^^^^^^^^^^
>>>>                         }
>>>>     host Divinka-Obecny-Urad {
>>>>                         hardware ethernet 00:4f:74:31:b4:03;
>>>>                         fixed-address 157.157.56.131;
                                            ^^^^^^^^^^^^^^

Hosts with fixed addresses that are within a dynamic range. Recipe for problems.



------------------------------

Message: 4
Date: Sat, 5 Oct 2019 02:49:46 +0200
From: Sten Carlsen <st...@s-carlsen.dk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: strange behavior of shared network
Message-ID: <4c67d8fe-dd5e-4bca-857e-7627ba03e...@s-carlsen.dk>
Content-Type: text/plain;       charset=us-ascii




-- 
Best regards

Sten Carlsen

No improvements come from shouting:

      "MALE BOVINE MANURE!!!"

> On 4 Oct 2019, at 21.42, Simon Hobson <dh...@thehobsons.co.uk> wrote:
> 
> Sten Carlsen <st...@s-carlsen.dk> wrote:
> 
>> Looking at the data you give, I see no conflict. Can you be more specific 
>> about the problem?
> 
> You can't see it when it's been pointed out ?
Right, simple. Lost in detail. My fault.
> 
>>>>> subnet 157.157.56.128 netmask 255.255.255.240 {
>>>>>        option broadcast-address 157.157.56.143;
>>>>>        option subnet-mask 255.255.255.240;
>>>>>        option routers 157.157.56.129;
>>>>>        deny unknown-clients;
>>>>>        range 157.157.56.130 157.157.56.142;
>                    ^^^^^^^^^^^^^^
>>>>>    host Divinka-Uhliarik {
>>>>>                        hardware ethernet cc:2d:e0:3f:fa:42;
>>>>>                        fixed-address 157.157.56.130;
>                                            ^^^^^^^^^^^^^^
>>>>>                        }
>>>>>    host Divinka-Obecny-Urad {
>>>>>                        hardware ethernet 00:4f:74:31:b4:03;
>>>>>                        fixed-address 157.157.56.131;
>                                            ^^^^^^^^^^^^^^
> 
> Hosts with fixed addresses that are within a dynamic range. Recipe for 
> problems.
> 
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users



------------------------------

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 132, Issue 4
******************************************

Reply via email to