Hello Robert:
Sorry you're having difficulties. I tested your server config below
with 4.3.5 and locally connected clients and the server issues leases
without issue as you can see from the log output later on. So there is
nothing inherent in your server config that is causing an issue. Can you
email me, directly, a pcap file so I can see exactly what your clients
are sending? I would also suggest you (if you haven't already) try
running dhcpd in the foreground so you can capture all of the logging
down to the debug level to stdout. It is possible the solicits are being
dropped and we're not seeing why. Alternatively you can open a ticket
here:
https://www.isc.org/community/report-bug/ By default new tickets
are confidential as are any attachments emailed to the bug ticket. We
are keenly aware of the sensitivity of user system information and we
never make public such information unless we have explicit permission
from users to do so. Certainly with issues such as yours the more data
you can supply us with the easier it will be for us to resolve your
issue. Regards, Thomas Markwalder ISC Software Engineering Log output
from 4.3.5 with your config: tmark@cserver isc_dhcp $ sudo bin/t.sh
4.3.5 etc/v6/spotswood.conf enp0s10 -6 wipe wiping lease file
output/spotswood.leases sbin/dhcpd enp0s10 -6 -d -cf
/labspace/var/isc_dhcp/etc/v6/spotswood.conf -pf output/spotswood.pid
-lf output/spotswood.leases Internet Systems Consortium DHCP Server
4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights
reserved. For info, please visit
https://www.isc.org/software/dhcp/
Config file: /labspace/var/isc_dhcp/etc/v6/spotswood.conf Database file:
output/spotswood.leases PID file: output/spotswood.pid Wrote 0 NA, 0 TA,
0 PD leases to lease file. Bound to *:547 Listening on
Socket/5/enp0s10/fd00:220:0:1::/64 Sending on
Socket/5/enp0s10/fd00:220:0:1::/64 Server starting service. wiping lease
file output/spotswood.leases sbin/dhcpd enp0s10 -6 -d -cf
/labspace/var/isc_dhcp/etc/v6/spotswood.conf -pf output/spotswood.pid
-lf output/spotswood.leases Internet Systems Consortium DHCP Server
4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights
reserved. For info, please visit
https://www.isc.org/software/dhcp/
Config file: /labspace/var/isc_dhcp/etc/v6/spotswood.conf Database file:
output/spotswood.leases PID file: output/spotswood.pid Wrote 0 NA, 0 TA,
0 PD leases to lease file. Bound to *:547 Listening on
Socket/5/enp0s10/fd00:220:0:1::/64 Sending on
Socket/5/enp0s10/fd00:220:0:1::/64 Server starting service. Solicit
message from 3002::35 port 546, transaction ID 0x000000 Picking pool
address fd00:220:0:1::800 Advertise NA: address fd00:220:0:1::800 to
client with duid 00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:04 iaid = 1
valid for 6048 seconds Sending Advertise to 3002::35 port 546 Request
message from 3002::35 port 546, transaction ID 0x1000000 Reply NA:
address fd00:220:0:1::800 to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:04 iaid = 1 valid for 6048
seconds Sending Reply to 3002::35 port 546 Solicit message from 3002::35
port 546, transaction ID 0x2000000 Picking pool address
fd00:220:0:1::789 Advertise NA: address fd00:220:0:1::789 to client with
duid 00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:05 iaid = 1 valid for 6048
seconds Sending Advertise to 3002::35 port 546 Request message from
3002::35 port 546, transaction ID 0x3000000 Reply NA: address
fd00:220:0:1::789 to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:05 iaid = 1 valid for 6048
seconds Sending Reply to 3002::35 port 546 Solicit message from 3002::35
port 546, transaction ID 0x4000000 Picking pool address
fd00:220:0:1::7da Advertise NA: address fd00:220:0:1::7da to client with
duid 00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:06 iaid = 1 valid for 6048
seconds Sending Advertise to 3002::35 port 546 Request message from
3002::35 port 546, transaction ID 0x5000000 Reply NA: address
fd00:220:0:1::7da to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:06 iaid = 1 valid for 6048
seconds Sending Reply to 3002::35 port 546 Solicit message from 3002::35
port 546, transaction ID 0x6000000 Picking pool address
fd00:220:0:1::717 Advertise NA: address fd00:220:0:1::717 to client with
duid 00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:07 iaid = 1 valid for 6048
seconds Sending Advertise to 3002::35 port 546 Request message from
3002::35 port 546, transaction ID 0x7000000 Reply NA: address
fd00:220:0:1::717 to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:07 iaid = 1 valid for 6048
seconds Sending Reply to 3002::35 port 546 Solicit message from 3002::35
port 546, transaction ID 0x8000000 Advertise NA: address
fd00:220:0:1::800 to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:04 iaid = 1 valid for 6048
seconds Sending Advertise to 3002::35 port 546 Request message from
3002::35 port 546, transaction ID 0x9000000 Reply NA: address
fd00:220:0:1::800 to client with duid
00:01:00:01:21:a1:8f:ab:00:0c:01:02:03:04 iaid = 1 valid for 6048
seconds Sending Reply to 3002::35 port 546
On 11/16/2017 05:35 PM,
[hidden email] wrote:
> You might be on to something, but the pool6 idea didn't work either. In
> between posts, I installed the kea dhcp6 server. Got a minimal config file
> cobbled together (man, it's a mess edit the config compared to the
> isc-dhcp-server) and fired it up. Clients got a lease no problem (the
> ipconfig /release6, ipconfig /renew6 dance). So 100% it's a server issue,
> and 100% not a firewall issue.
>
> That leaves two possibilities:
>
> (1) Something has changed from 4.2.2 to 4.3.5 that requires updating my
> config file.
> or
> (2) There is a bug in 4.3.5. I noticed you didn't use 4.3.5. Possibly some
> regression that was fixed in 4.3.6??? I looked at the release notes and
> didn't see anything.
>
> Unless someone spots an error in my config file (and the original works
> fine on 4.2.2), I guess I'll have to look at 4.3.6 to see if that fixes
> the issue.
>
> == current config ==
> efault-lease-time 6048;
> max-lease-time 6048;
> log-facility local7;
> ddns-updates on;
> ddns-update-style interim;
> update-static-leases on;
> authoritative;
> #log-facility debug;
>
> subnet6 fd00:220:0:1::/64 {
> pool6 {
> #Range for clients
> range6 fd00:220:0:1::601 fd00:220:0:1::800;
> allow unknown clients;
> allow known clients;
> }
> #Additional options
> option dhcp6.name-servers fd00:220:0:1::40, fd00:220:0:1::50;
> option dhcp6.domain-search "redacted.name";
> }
>
>>> On Nov 16, 2017, at 12:00 PM,
[hidden email] wrote:
>>>
>>> Since no one can find anything obvious, maybe the version I've got has a
>>> bug? Anyone using 4.3.5 for ipv6 successfully?
>> We used 4.3.4 successfully and now we're using 4.3.6 successfully. Our
>> config is different in a couple ways - we use classes and ranges are
>> inside pool6 blocks, e.g.
>>
>> shared-network Pine-B-net.stanford.edu {
>> subnet6 2607:f6d0:0:13af::/64 {
>> pool6 {
>> allow members of "dhcpv6test";
>> range6 2607:f6d0:0:13af:bad:c0ff:ee:1
>> 2607:f6d0:0:13af:bad:c0ff:ee:6e;
>> }
>> }
>> }
>>
>> Recommend you try pool6.
>>
>
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
