Send dhcp-users mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: IPv6 DHCP Routing (Brice Abba)
2. Removing incorrect ddns info from lease (Frank Price)
3. Re: IPv6 DHCP Routing (spaceman)
4. RE: Using custom variable to assign value to bootfile-name
([email protected])
----------------------------------------------------------------------
Message: 1
Date: Tue, 17 Nov 2015 20:36:01 +0400
From: Brice Abba <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: IPv6 DHCP Routing
Message-ID:
<cabyy8cy1ooianqsezdumjw0mbl0hblhqtcuntfjscsue2jo...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
This seems to be a normal behaviors, because we dont have possibility to
specify the prefix length in DHCPv6, so every simgle machine will have
/128, then even if they are all on the same link we'll have routing, to
avoid this,
You can ask your router sending RA, to set the "L" flag to tell nodes to
consider that they are on the same link, this way you could avoid all
trafic to pass through the GW. And set manegement flag as well
Regards,
2015-11-17 1:07 GMT+04:00 spaceman <[email protected]>:
> Hi,
>
> I have the following IPv6 subnet 2001:470:1f09:800::/64 and these
> addresses are handed out correctly by dhcpd. However a single windows
> machine I have insists on send all traffic destined for a
> 2001:470:1f09:800::/64 address to the gateway when it should be sent
> straight to the device on the network.
>
> For example it should be:
> 2001:470:1f09:800::10 --> 2001:470:1f09:800::5
> but with this machine its:
> 2001:470:1f09:800::10 --> 2001:470:1f09:800::1 --> 2001:470:1f09:800::5
>
> The IP of the gateway is 2001:470:1f09:800::1.
>
> How do I avoid this?
>
> Regards,
> spaceman
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
--
------------------------------
Brice ABBA
www.afrinic.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20151117/6cff0e7f/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 17 Nov 2015 11:47:21 -0500
From: Frank Price <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Removing incorrect ddns info from lease
Message-ID:
<cakqznuebk_z-v5mk61rbc8rzhnueawxnas4hwxb7lh2p2st...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi dhcp-users,
Internet Systems Consortium DHCP Server 4.2.5
IND 9.9.4-RedHat-9.9.4-18.el7_1.1 (Extended Support Version)
dhcpd failover
I'm struggling with some of my clients occasionally losing their ddns
entries, or not having them updated. In an effort to fix things up, I want
to remove DHCID info from the lease. The dhcpd.conf man page tells me
"data can be removed from the lease through operator intervention," but is
light on details:
In addition to these differences, the server also does not update very
> aggressively. Because each DNS update involves a round trip to the DNS
> server, there is a cost associated with doing updates even if they do not
> actually modify the DNS database. So the DHCP server tracks whether or not
> it has updated the record in the past (this information is stored on the
> lease) and does not attempt to update records that it thinks it has
> already updated.
>
> This can lead to cases where the DHCP server adds a record, and then the
> record is deleted through some other mechanism, but the server never again
> updates the DNS because it thinks the data is already there. In this case
> the data can be removed from the lease through operator intervention, and
> once this has been done, the DNS will be updated the next time the client
> renews.
Here's one of the leases in question:
lease 10.199.128.49 {
starts 1 2015/11/16 21:31:22;
ends 2 2015/11/17 21:31:22;
tstp 3 2015/11/18 09:31:22;
tsfp 3 2015/11/18 09:31:22;
atsfp 3 2015/11/18 09:31:22;
cltt 1 2015/11/16 21:31:22;
binding state active;
next binding state expired;
hardware ethernet f8:bc:12:3f:69:90;
uid "\001\370\274\022?i\220";
set ddns-rev-name = "49.128.999.10.in-addr.arpa.";
set ddns-txt = "31cce6d6ea09aa5603b3d319af3022007a";
set ddns-fwd-name = "yocto023.yocto.rds.bigco.com";
client-hostname "yocto023";
}
Intuition says it's one of the ddns-* options, but my intuition often
sucks.
1. What information should I remove from the lease?
2. Is there a recommended way to do this that doesn't involve manually
editing the leases file?
Thanks as always for any help you can provide,
-Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20151117/61c59a39/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 17 Nov 2015 17:31:53 +0000
From: spaceman <[email protected]>
To: [email protected]
Subject: Re: IPv6 DHCP Routing
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Brice,
>This seems to be a normal behaviors, because we dont have possibility to
>specify the prefix length in DHCPv6, so every simgle machine will have
>/128, then even if they are all on the same link we'll have routing, to
>avoid this,
>You can ask your router sending RA, to set the "L" flag to tell nodes to
>consider that they are on the same link, this way you could avoid all
>trafic to pass through the GW. And set manegement flag as well
I figured this out now. The reason for it was that the routing advertisement
was set for the network used by ip6 to ip4 tunnel. Thus all traffic went to
the router to be routed to the internal network. The reason why this only
happened on the windows machine is probably due to way the DHCP client works.
Internal: 2001:470:1f09:800::1/64
External: 2001:470:1f08:800::1/64
Anyway don't I feel stupid.
Thanks,
spaceman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20151117/a5bf6a1c/attachment-0001.bin>
------------------------------
Message: 4
Date: Tue, 17 Nov 2015 18:20:16 +0000
From: <[email protected]>
To: <[email protected]>
Subject: RE: Using custom variable to assign value to bootfile-name
Message-ID:
<hk2pr03mb0675d1d6d13c9a02894e1b5c84...@hk2pr03mb0675.apcprd03.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi Niall and Simon,
Thanks a ton for your inputs.
I have created the config files with only entry with the software version for
each target and included them in the actual dhcp file. And gave full permission
to these config files and only r&x permission to actual dhcp file.
I have one more query!
How can I calculate the string length in the dhcp file.
For example:
Option software-version "soft_v1_g2333.tar"
I want to know the length of "soft_v1_g2333.tar" in the dhcp conf file.
Is it possible? Is there any function similar to substring()?
BR,
Karteek
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Simon Hobson
Sent: den 11 november 2015 23:43
To: Users of ISC DHCP
Subject: Re: Using custom variable to assign value to bootfile-name
Niall O'Reilly <[email protected]> wrote:
> Variables don't do what you need.
>
> I'ld suggest something like this, repeated for the other groups:
>
> group target_1 {
> option boot-filename = "soft_1.tar";
> }
I think the problem he has is that if he allows the devs to edit that
themselves, they screw up the rest of the config. I'm wondering if some include
files (and perhaps some scripts) might work.
group target_1 {
$INCLUDE soft1.cfg
}
Then generate a number of config files that you can use with the include
statements. Either let the devs edit them directly, or let them work through a
script that does some sanity checking.
Or put placeholders in the config, and have a script that replaces them with
the desired values to generate a config file for the server to use.
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email. www.wipro.com
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 85, Issue 19
******************************************
