Issues configuring dhcp6s

David Beveridge dave at bevhost.com
Tue Feb 4 04:17:49 UTC 2014


Firstly, can I say...
Interesting place to send a question about wide-dhcp, since this is the ISC
mailling list for dhcp.

However, your config looks ok to me.
The error message indicates that the server cannot recognise the subnet to
which the request belongs.
Perhaps you might try using the wide-dhcp relay agent "dhcp6r" to first
prove your server works and can accept relayed packets.  Once you have that
working then you can try out other relay agents.

dave

On Tue, Feb 4, 2014 at 12:52 PM, Darren Ward (darrward)
<darrward at cisco.com>wrote:

>  Hi All
>
>
>
> I have been using dhcpd for IPv4 centralised management of pools in the
> lab and now have to do the same for IPv6
>
>
>
> I believe I have dhcp6s configured to run ok but I'm obviously doing
> something wrong
>
>
>
> Scenario is I have remote LAN's attached to Cisco routers configured with
> ipv6 dhcp relay to the remote dhcp6s device and I can see the icoming
> requests but it doens' match the pool and assign addresses for a start and
> I have unsupported options
>
>
>
> So I think the issue is my config is bad for remote LAN's so I'm not
> matching a pool properly in the config but I can't find an example online
> to follow.
>
>
>
> The dhcpc client is attached to the router which has an interface address
> of 2010:123::1/64 and relays towards the DHCPv6 server from the 2010:3::1
> address
>
>
>
> Hoping someone can point out my config error, here' is my dhcp6s.conf:
>
>
>
> #
>
> # See dhcp6s.conf(5) man page for details.
>
> #
>
>
>
> interface eth0 {
>
>     server-preference 255;
>
>     renew-time 60;
>
>     rebind-time 90;
>
>     prefer-life-time 130;
>
>     valid-life-time 200;
>
>     allow rapid-commit;
>
>     option dns_servers 2010:110::10 spc.cisco.com;
>
>
>
>     link AAA {
>
>         pool {
>
>             range 2010:110::100 to 2010:110::200/64;
>
>             prefix 2010:110::/64;
>
>         };
>
>     };
>
>     link WIFI {
>
>         pool {
>
>             range 2010:123::100 to 2010:123::1000/64;
>
>             prefix 2010:123::/64;
>
>         };
>
>     };
>
>
>
> };
>
>
>
> And the router is relaying packets as here's the debug:
>
>
>
> asr1k-top#
>
> Feb  4 13:42:40.358 AEDT: IPv6 DHCP_RELAY: Relaying SOLICIT from
> FE80::250:56FF:FE80:2541 on GigabitEthernet0/0/2.123
>
> Feb  4 13:42:40.359 AEDT: IPv6 DHCP_RELAY: SAS Input: Relay linkaddr
> 2010:123::1 src :: msg 12
>
> Feb  4 13:42:40.359 AEDT: IPv6 DHCP_RELAY: Replaced user src-addr :: with
> SAS addr 2010:123::1 idb GigabitEthernet0/0/2.123.
>
> Feb  4 13:42:40.359 AEDT: IPv6 DHCP_RELAY: Override linkaddr with addr of
> 2010:123::1 on idb GigabitEthernet0/0/2.123
>
> *Feb  4 13:42:40.359 AEDT: IPv6 DHCP_RELAY: Packet forwarded to
> 2010:110::10 (vrf default)*
>
> *Feb  4 13:42:40.360 AEDT: IPv6 DHCP_RELAY: Relaying RELAY-REPLY from
> 2010:110::10 on GigabitEthernet0/0/3*
>
> Feb  4 13:42:40.360 AEDT: IPv6 DHCP_RELAY: Packet forwarded to
> FE80::250:56FF:FE80:2541 (vrf default) via GigabitEthernet0/0/2.123
>
> asr1k-top#
>
>
>
> This is from the server (dhcp6s -d -D):
>
>
>
> *Feb/04/2014 13:38:26 received message packet info addr is 2010:110::10,
> scope id (2)*
>
> *Feb/04/2014 13:38:26 received relay forwarding from 2010:3::1*
>
> Feb/04/2014 13:38:26 Unsupported option opt_79 found in RELAY-FORW message
>
> Feb/04/2014 13:38:26 Unsupported option opt_37 found in RELAY-FORW message
>
> Feb/04/2014 13:38:26 get DHCP option client ID, len 14
>
> Feb/04/2014 13:38:26   client DUID:
> 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00
>
> Feb/04/2014 13:38:26 get DHCP option opt_8, len 2
>
> Feb/04/2014 13:38:26  this message elapsed time is: 65535
>
> Feb/04/2014 13:38:26 get DHCP option rapid commit, len 0
>
> Feb/04/2014 13:38:26 get option rapid-commit
>
> Feb/04/2014 13:38:26 get DHCP option opt_25, len 12
>
> Feb/04/2014 13:38:26 get option iaid is 1092976726, renewtime 0,
> rebindtime 0
>
> Feb/04/2014 13:38:26 get DHCP option opt_79, len 8
>
> Feb/04/2014 13:38:26 unknown or unexpected DHCP6 option opt_79, len 8
>
> Feb/04/2014 13:38:26 get DHCP option interface identifier, len 11
>
> Feb/04/2014 13:38:26 unknown or unexpected DHCP6 option interface
> identifier, len 11
>
> Feb/04/2014 13:38:26 get DHCP option opt_37, len 22
>
> Feb/04/2014 13:38:26 unknown or unexpected DHCP6 option opt_37, len 22
>
> *Feb/04/2014 13:38:26 client ID 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00*
>
> *Feb/04/2014 13:38:26  status code: not on-link*
>
> Feb/04/2014 13:38:26 set client ID
>
> Feb/04/2014 13:38:26 set server ID
>
> Feb/04/2014 13:38:26 set status code
>
> *Feb/04/2014 13:38:26 send destination address is 2010:3::1, scope id is 0*
>
> *Feb/04/2014 13:38:26 transmit reply to 2010:3::1*
>
> Feb/04/2014 13:38:26 DUID is 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00,
> DUID_LEN is 14
>
> Feb/04/2014 13:38:26 removing ID (ID:
> 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00)
>
> Feb/04/2014 13:38:26 DUID is 00:01:00:01:1a:83:07:6d:90:01:02:00:00:00,
> DUID_LEN is 14
>
> Feb/04/2014 13:38:26 removing ID (ID:
> 00:01:00:01:1a:83:07:6d:90:01:02:00:00:00)
>
> Feb/04/2014 13:38:26 DUID is 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00,
> DUID_LEN is 14
>
> Feb/04/2014 13:38:26 removing ID (ID:
> 00:01:00:01:1a:83:07:6d:00:00:00:00:00:00)
>
> Feb/04/2014 13:38:26 DUID is , DUID_LEN is 0
>
>
>
> All I see on the dhcp6c (-dDf eth0) client is that it is sending (set
> client, set opt_8, set rapid_commit, set opt_25, set IA_PD) out on eth0 -
> no response
>
>
>
> Cheers
>
> Darren
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at 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/20140204/cf1b14b0/attachment-0001.html>


More information about the dhcp-users mailing list