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: Documentation clarification about unsigned/signed integer
      (Simon)
   2. Re: Some devices randomly losing their IPv4 address (Simon)


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

Message: 1
Date: Sat, 16 Apr 2022 17:04:57 +0100
From: Simon <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Documentation clarification about unsigned/signed integer
Message-ID: <8e946443-c5e3-40ac-ae92-7b520d327...@thehobsons.co.uk>
Content-Type: text/plain;       charset=utf-8

Alex Duzsardi <alex.duzsa...@prodigy-it-solutions.com> wrote:

> So basically the server just decodes bytes in whatever format they might be 
> provided be it integer, hex, text and it expects the decoded data to make 
> sense for the type of the option set, integer in the case of option code 93

Indeed. Though in practical terms, internally everything is binary and all 
config options will be converted to binary for use in comparisons.

> Is this behavior the same for other option types  
> (string,ip-address,text,flag) ?

As far as I know, yes.


> Guessing providing an integer for a string type option doesn't really make 
> sense , will the server ignore the option in this case or just crash or log 
> an error ?  (i'll test it on a lab server later)

I think it?ll just convert whatever you provide into a binary value internally. 
The option type is more to do with how it is packed into the packet, and the 
size.

You can even do mixed types - have a look in the leases file and you see things 
like client-IDs saved as text items, but with non-printable characters hex 
encoded.

Simon



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

Message: 2
Date: Sat, 16 Apr 2022 17:05:40 +0100
From: Simon <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Some devices randomly losing their IPv4 address
Message-ID: <ba2196d9-38d3-4fd6-967f-0037eb7b9...@thehobsons.co.uk>
Content-Type: text/plain;       charset=utf-8

Glenn Satchell <glenn.satch...@uniq.com.au> wrote:

> My guess about losing an address is that you have a race between dhcp 
> servers, and the client gets to pick which response to use, usually the first 
> it receives. So if your router gets the response in first, the the client 
> gets a message about no free addresses. If your dhcp server system wins, then 
> the client gets the IP address. I can't see an easy to way to solve this 
> other than the workaround you tried.

That was my first thought.

A couple of other workarounds did come to mind :

1) If the OP can find a suitable switch with the right speed interfaces and 
which also has DHCP filtering (a.k.a. rogue DHCP server protection) then that 
could filter the ISPs router responses.

2) Rather than trying to build a single router that does 1.<whatever> gig - 
would it work to segregate the network (it?s was suggested that this was wanted 
anyway) so that a number of 1G capable routers connected the different segments 
?

Simon

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

Subject: Digest Footer

_______________________________________________
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


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

End of dhcp-users Digest, Vol 162, Issue 7
******************************************

Reply via email to