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: Using OMAPI to release a DHCP lease on a failover pair
(Bill Shirley)
2. Re: Ipv6 hostname in dhclient.conf (Anjali Krishna)
3. Re: dhcp-users Digest, Vol 141, Issue 26 (Kunal Chauhan)
----------------------------------------------------------------------
Message: 1
Date: Fri, 31 Jul 2020 08:13:57 -0400
From: Bill Shirley <b...@c3po.polymerindustries.biz>
To: dhcp-users@lists.isc.org
Subject: Re: Using OMAPI to release a DHCP lease on a failover pair
Message-ID:
<1948ef39-37a9-9469-ecc5-2a48ed65a...@c3po.polymerindustries.biz>
Content-Type: text/plain; charset=utf-8; format=flowed
https://en.wikipedia.org/wiki/IPv4#First_and_last_subnet_addresses
I'm speaking about the subnet assigned to the NIC.
Bill
On 7/30/2020 4:20 PM, sth...@nethelp.no wrote:
>> Interesting. You would only have two available addresses, right? The network
>> address and the broadcast address? Which one does the device answer to?
> When using IPv4 /31 there's really no "network address" or "broadcast
> address". There are simply two IP addresses. One is the router and the
> other is the client. Supported by lots of equipment, and also ISC
> DHCP.
>
> Example:
>
> # Router is at lowest address of the /31
> subnet 172.16.1.10 netmask 255.255.255.254
> {
> option routers 172.16.1.10;
> range 172.16.1.11 172.16.1.11;
> }
>
> but you could also do
>
> # Router is at highest address of the /31
> subnet 172.16.1.10 netmask 255.255.255.254
> {
> option routers 172.16.1.11;
> range 172.16.1.10 172.16.1.10;
> }
>
> There is no magic here.
>
> Steinar Haug, Nethelp consulting, sth...@nethelp.no
> _______________________________________________
> 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
------------------------------
Message: 2
Date: Fri, 31 Jul 2020 18:00:49 +0530
From: Anjali Krishna <krishnaanjal...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Ipv6 hostname in dhclient.conf
Message-ID:
<CAP6u7k-e9VrWaU6dz_=yat8uy4-+kkcvhh82+pb0ez4heoi...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Bill,
Thank you for the support
The hostname is updating in the lease file after updating this line in
dhclient
send fqdn.fqdn "hostname.example.com."
The dot after the com was missing after this change it did work.
On Tue, 28 Jul 2020, 4:28 pm Bill Shirley, <b...@c3po.polymerindustries.biz>
wrote:
> On the server, did you implement?:
> set my_given_hostname = option fqdn.hostname;
> It should be in the lease file even if it is blank.
>
> Run tcpdump on the dhcp server to see exactly what is sent/received:
> tcpdump -vv -e -n -i eth0 portrange 67-68
> For IPv6.
> tcpdump -X -l -vv -e -n -i eth0 portrange 546-547
>
> Bill
> On 7/28/2020 4:27 AM, Anjali Krishna wrote:
>
> Hi Bill Shirley,
>
> Thank you for the reply
>
> The code snippet which you have shared I tried under dhcpd.conf
>
> The my_duid_hex and my_duid variables are updating with the values
>
> I tried with "send fqdn.hostname "test_dut" " in dhclient.conf file.
>
> But the hostname is not still updating in the lease file
>
> What am I missing in client side?
>
> On Tue, 28 Jul 2020, 1:49 am Bill Shirley, <
> b...@c3po.polymerindustries.biz> wrote:
>
>> You can save your own variables in the leases file for non-static leases:
>> on commit {
>> if static {
>> # set is-static = " --> STATIC";
>> } else {
>> set is-static = "";
>> set my_duid = option dhcp6.client-id;
>> set my_duid_hex = pick-first-value(binary-to-ascii(16, 8, ":",
>> option dhcp6.client-id), "");
>> set my_given_hostname = option fqdn.hostname;
>> }
>> }
>>
>> Lease:
>> ia-na "mbl\022\000\001\000\001\025Yy\267lbm\207\267\370" {
>> cltt 0 2020/07/12 12:45:07;
>> iaaddr 2001:xxxx:yyyy:40:50f7::ee {
>> binding state active;
>> preferred-life 9000;
>> max-life 14400;
>> ends 0 2020/07/12 16:45:07;
>> set ddns-rev-name = "<redacted>";
>> set ddns-dhcid =
>> "\000\002\001\320F0\342\231\334\262\211\351u\023\260\207\200\240%\230\004ZD\035\370\221f\367E\225\245e\234\2154";
>> set ddns-fwd-name = "Karen-PC.example.com";
>> set my_MAC = "6c:62:6d:87:b7:f8";
>> set my_given_hostname = "Karen-PC";
>> set my_duid_hex = "0:1:0:1:15:59:79:b7:6c:62:6d:87:b7:f8";
>> set my_duid = "\000\001\000\001\025Yy\267lbm\207\267\370";
>> set member_of = "Microsoft";
>> set pool_type = "Microsoft";
>> }
>> }
>>
>> Hope this helps,
>> Bill
>> On 7/27/2020 8:04 AM, Anjali Krishna wrote:
>>
>>
>> Hi
>>
>> I am using an embedded board with hostname "test_dut"[same under
>> /etc/hostname]. I am testing ipv6 ans ipv4 using dhcpd on server side with
>> - 6, - 4 options and client side I am using dhclient with - 6 and - 4
>> option for ipv6 and ipv4 respectively.
>> Both the cases Ip assignment is happening without any trouble. But in
>> order to extend our application feature we are providing the information of
>> the connected devices to the user such as mac id, ip, hostname/client name
>> etc. In ipv4 these information are provided under dhcpd.leases file. In
>> case of ipv6 I am not able to find the hostname (test_dut) under the
>> dhcpd6.leases files
>>
>> I tried with adding various options under dhclient.conf such as send
>> host-name "test_dut" and edited the dhclient-script under /sbin and called
>> set_hostname call under bound-renew-reboot section of ipv6. Still the
>> server lease file is not updating the hostname for ipv6 . But hostname is
>> updating for ipv4 connection.
>>
>> How can I resolve this issue?
>>
>> Regards,
>> Anjali
>>
>> _______________________________________________
>> 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
>> listdhcp-us...@lists.isc.orghttps://lists.isc.org/mailman/listinfo/dhcp-users
>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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
> listdhcp-us...@lists.isc.orghttps://lists.isc.org/mailman/listinfo/dhcp-users
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20200731/df4d22d8/attachment-0001.htm>
------------------------------
Message: 3
Date: Fri, 31 Jul 2020 23:12:27 +0530
From: Kunal Chauhan <atkunalchau...@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Re: dhcp-users Digest, Vol 141, Issue 26
Message-ID:
<CACEFAc3r7YnzBfm1LOMz9=vafjqe1pzq-smbztts7-h7y2y...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
>I doubt you could implement it in hardware - there's just so much
involved. As both a primer and in-depth volume, I'd recommend you get hold
of "The DHCP >Handbook" by Ted Lemon and Ralph Droms. That will explain how
the protocol works, and hopefully give you an idea of just how much is
involved.
Hi My point was I have linux board basically which is act as an acces point
which will get some ips from server as it will boot up so want to
implement DHCP functionality to it.
>Apart from anything else, if you were to implement just DHCP in hardware,
what would you use the information for if there wasn't a software stack to
use it ?
>So in reality, you'd be needing to use a full software stack - even if it
was stripped down to the bare essentials. Once you are using software, then
all the >components are already written for you.
Yes I basically want DHCP over linux board
Message: 2
Date: Thu, 30 Jul 2020 21:22:03 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: [Help]: dhcp concept and code part
Message-ID: <d5bf814d-e065-4875-9a4f-42042a03e...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii
Kunal Chauhan <atkunalchau...@gmail.com> wrote:
> I am new to dhcp , I have read out dhcp docs at internet, but not clearly
understand in a practical way how dhcp works on a piece of harware.
>
> How it can be implemented on some harware or soc.
I doubt you could implement it in hardware - there's just so much involved.
As both a primer and in-depth volume, I'd recommend you get hold of "The
DHCP Handbook" by Ted Lemon and Ralph Droms. That will explain how the
protocol works, and hopefully give you an idea of just how much is involved.
Apart from anything else, if you were to implement just DHCP in hardware,
what would you use the information for if there wasn't a software stack to
use it ?
So in reality, you'd be needing to use a full software stack - even if it
was stripped down to the bare essentials. Once you are using software, then
all the components are already written for you.
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 141, Issue 26
*******************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20200731/77970194/attachment.htm>
------------------------------
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 141, Issue 27
*******************************************
