dhcpd -6 dont start

[Kari, Vitali]

Hi,

 

just compiled 4.3.4b1 with DHCPv6 support, but cannot start in dhcpv6 mode.

 

If I try to start with:

/sbin/dhcpd -6 -d -cf /etc/dhcpd6.conf eth2

Internet Systems Consortium DHCP Server 4.3.4b1

Copyright 2004-2016 Internet Systems Consortium.

All rights reserved.

For info, please visit https://www.isc.org/software/dhcp/

Config file: /etc/dhcpd6.conf-test

Database file: /var/db/dhcpd6.leases

PID file: /var/run/dhcpd6.pid

Wrote 0 NA, 0 TA, 0 PD leases to lease file.

 

No subnet6 declaration for eth2 (fe80::250:56ff:fea3:217d).

** Ignoring requests on eth2.  If this is not what

   you want, please write a subnet6 declaration

   in your dhcpd.conf file for the network segment

   to which interface eth2 is attached. **

 

 

Not configured to listen on any interfaces!

 

 

Testing the config file says:

/sbin/dhcpd -6 -t /etc/dhcpd6.conf eth2

/etc/dhcpd6.conf: interface name too long (is 16)

 

 

My /etc/dhcpd6.conf is quite simple:

 

option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;

 

subnet6 2a03:4920:100::/44 {

    prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56;

}

 

 

 

 

Any ideas what I’m doing wrong?

 

 

 

Best regards

Mit freundlichen Grüßen

Vitali Kari 

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[A.L.M.Buxey]

hi,

 

** Ignoring requests on eth2.  If this is not what

   you want, please write a subnet6 declaration

   in your dhcpd.conf file for the network segment

   to which interface eth2 is attached. **

define a subnet6 statement for the eth2 address space but dont put any ranges/stuff into it.

 

alan

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Simon Hobson]

Alan Buxey <[hidden email]> wrote:

> define a subnet6 statement for the eth2 address space but dont put any ranges/stuff into it.

Or configure the server to only listen on interfaces you want to serve.


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Anderson, Charles R]

On Mon, Apr 04, 2016 at 05:12:35PM +0100, Simon Hobson wrote:
> Alan Buxey <[hidden email]> wrote:
>
> > define a subnet6 statement for the eth2 address space but dont put any ranges/stuff into it.
>
> Or configure the server to only listen on interfaces you want to serve.

> > > No subnet6 declaration for eth2 (fe80::250:56ff:fea3:217d).

Is it really necessary to define a subnet6 for the Link-Local subnet
on all interfaces?  If so, this should work (I haven't tried):

subnet6 fe80::/64 {
}

> > > /etc/dhcpd6.conf: interface name too long (is 16)

That is interesting.  What interfaces do you have? (ifconfig -a)
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Kari, Vitali]

I added

subnet6 fe80::/64 {
}
to my config and it starts now with sample config:

/sbin/dhcpd -6 -d -cf /etc/dhcpd6.conf-test eth2

Internet Systems Consortium DHCP Server 4.3.4b1
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Config file: /etc/dhcpd6.conf-test
Database file: /var/db/dhcpd6.leases
PID file: /var/run/dhcpd6.pid
Wrote 0 NA, 0 TA, 0 PD leases to lease file.
Multiple interfaces match the same subnet: eth0 eth2
Multiple interfaces match the same shared network: eth0 eth2
Multiple interfaces match the same subnet: eth0 eth1
Multiple interfaces match the same shared network: eth0 eth1
Bound to *:547
Listening on Socket/5/eth2/fe80::/64
Sending on   Socket/5/eth2/fe80::/64
Server starting service.

But I am a little cunfused why I need a subnet6 for Link-Local interface to bring the daemon up. The fe80::/64 will fit to all Link-Local interfaces, so I get a warning about multiple interface matching even if I start the daemon with eth2.


My test config is now:
--------------
option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
subnet6 2a03:4920:100::/44 {
    prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56;
}

subnet6 fe80::/64 {
}
------------

Best regards
Mit freundlichen Grüßen

Vitali Kari 
Teamleiter NGN

-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Chuck Anderson
Gesendet: Montag, 4. April 2016 18:43
An: [hidden email]
Betreff: Re: dhcpd -6 dont start

On Mon, Apr 04, 2016 at 05:12:35PM +0100, Simon Hobson wrote:
> Alan Buxey <[hidden email]> wrote:
>
> > define a subnet6 statement for the eth2 address space but dont put any ranges/stuff into it.
>
> Or configure the server to only listen on interfaces you want to serve.

> > > No subnet6 declaration for eth2 (fe80::250:56ff:fea3:217d).

Is it really necessary to define a subnet6 for the Link-Local subnet on all interfaces?  If so, this should work (I haven't tried):

subnet6 fe80::/64 {
}

> > > /etc/dhcpd6.conf: interface name too long (is 16)

That is interesting.  What interfaces do you have? (ifconfig -a) _______________________________________________
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

[Simon Hobson]

"Kari, Vitali" <[hidden email]> wrote:

> But I am a little cunfused why I need a subnet6 for Link-Local interface to bring the daemon up. The fe80::/64 will fit to all Link-Local interfaces, so I get a warning about multiple interface matching even if I start the daemon with eth2.
>
>
> My test config is now:
> --------------
> option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
> subnet6 2a03:4920:100::/44 {
>    prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56;
> }
>
> subnet6 fe80::/64 {
> }

What IP addresses do you have on eth2 - in particular does it match the /44 subnet you've defined ?

Also, and bear in mind I'm no IPv6 expert, should the subnet and prefix declarations have different prefix lengths ?


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Kari, Vitali]

All my clients will be behind a relay agent, so it is theoretically not needed to put a Link-Local address in scope of subnet.
But it seems that the dhcp daemon do not start without that.

That is what I want:
[DHCPv6]-----(fe80::/64 + 2001:db8::15/64)--------[DHCP Relay]------(2a03:4920:100::/44)----[Clients]



-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Simon Hobson
Gesendet: Dienstag, 5. April 2016 09:15
An: Users of ISC DHCP <[hidden email]>
Betreff: Re: dhcpd -6 dont start

"Kari, Vitali" <[hidden email]> wrote:

> But I am a little cunfused why I need a subnet6 for Link-Local interface to bring the daemon up. The fe80::/64 will fit to all Link-Local interfaces, so I get a warning about multiple interface matching even if I start the daemon with eth2.
>
>
> My test config is now:
> --------------
> option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
> subnet6 2a03:4920:100::/44 {
>    prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56; }
>
> subnet6 fe80::/64 {
> }

What IP addresses do you have on eth2 - in particular does it match the /44 subnet you've defined ?

Also, and bear in mind I'm no IPv6 expert, should the subnet and prefix declarations have different prefix lengths ?


_______________________________________________
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

[Sten Carlsen]

On 05/04/2016 9:14, Simon Hobson wrote:

"Kari, Vitali" [hidden email] wrote:

But I am a little cunfused why I need a subnet6 for Link-Local interface to bring the daemon up. The fe80::/64 will fit to all Link-Local interfaces, so I get a warning about multiple interface matching even if I start the daemon with eth2.


My test config is now:
--------------
option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
subnet6 2a03:4920:100::/44 {
   prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56;
}

subnet6 fe80::/64 {
}

What IP addresses do you have on eth2 - in particular does it match the /44 subnet you've defined ?

Also, and bear in mind I'm no IPv6 expert, should the subnet and prefix declarations have different prefix lengths ?

Given the previous discussions on IPv6 vs. IPv4 addressing, I don't see a logical reason a subnet is needed?

The NIC has an address, who it can talk to is a completely different story, defined by the prefixes given by router(s).

Is the concept of the subnet being needed really a left-over from IPv4?, like the address/subnet concept which does not exist in IPv6?

Also I am not an IPv6 expert by far J

_______________________________________________
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

[Brice Abba]

Hi Kari,

DHCP doesn't  need LLA to work. The problem you have is due on some operating system implementation some linux distri.

On linux system like ubuntu you should include a subnet declaration of one of the IPv6 address of the interface you want the server to listening on. so never use LLA because you'll have same subbed every where as state in your DHCPv6 output.

If you were using openBSD you just need to specify the DHCP interface in /etc/rc.conf so no need to create a subnet definition for the server to listen over any interface.

- Remove LLA address and use a GUA instead

2016-04-05 12:39 GMT+04:00 Sten Carlsen <[hidden email]>:

On 05/04/2016 9:14, Simon Hobson wrote:

"Kari, Vitali" [hidden email] wrote:

But I am a little cunfused why I need a subnet6 for Link-Local interface to bring the daemon up. The fe80::/64 will fit to all Link-Local interfaces, so I get a warning about multiple interface matching even if I start the daemon with eth2.


My test config is now:
--------------
option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
subnet6 2a03:4920:100::/44 {
   prefix6 2a03:4920:100:100:: 2a03:4920:10f:ff00:: /56;
}

subnet6 fe80::/64 {
}

What IP addresses do you have on eth2 - in particular does it match the /44 subnet you've defined ?

Also, and bear in mind I'm no IPv6 expert, should the subnet and prefix declarations have different prefix lengths ?

Given the previous discussions on IPv6 vs. IPv4 addressing, I don't see a logical reason a subnet is needed?

The NIC has an address, who it can talk to is a completely different story, defined by the prefixes given by router(s).

Is the concept of the subnet being needed really a left-over from IPv4?, like the address/subnet concept which does not exist in IPv6?

Also I am not an IPv6 expert by far J

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!" 

_______________________________________________
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

[Simon Hobson]

On 5 Apr 2016, at 09:05, "Kari, Vitali" <[hidden email]> wrote:

> All my clients will be behind a relay agent, so it is theoretically not needed to put a Link-Local address in scope of subnet.
> But it seems that the dhcp daemon do not start without that.
>
> That is what I want:
> [DHCPv6]-----(fe80::/64 + 2001:db8::15/64)--------[DHCP Relay]------(2a03:4920:100::/44)----[Clients]

Is that 2001:db8::15 the address of the server ? The server probably needs a prefix defining that includes that, assuming it's working in a similar fashion to DHCPv4.

Thus, as I read the man pages (learning as I go !), you probably need an empty subnet6 declaration :
subnet6 2001:db8::/64 {
}

The reason it's needed is that the server does not know that there aren't any locally connected clients. Therefore the assumption must be that a client could appear locally to eth2, and the server must know how to handle that client. Hence the need for the subnet6 declaration. That declaration can be empty since you (as the admin) know there won't be any local clients.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Kari, Vitali]

Thank you for the hint Simon!

That is, with empty subnet declaration it works as expected.
And as Brice wrote before this should be Global Unique Address.

So this is a minimal working config for DHCPv6 behind relay Server: (WAN addresses for Documentation)

----------
# google DNSv6
option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;

#Customer Traffic Subnet
subnet6 2001:db8:100::/44 {
    prefix6 2001:db8:100:100:: 2001:db8:10f:ff00:: /56;
}

# local interface, need to get things working
subnet6 2001:db8::/64 {
}
----------

Thanks all!


Best regards
Mit freundlichen Grüßen

Vitali Kari 
Teamleiter NGN

-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Simon Hobson
Gesendet: Dienstag, 5. April 2016 12:20
An: Users of ISC DHCP <[hidden email]>
Betreff: Re: dhcpd -6 dont start


On 5 Apr 2016, at 09:05, "Kari, Vitali" <[hidden email]> wrote:

> All my clients will be behind a relay agent, so it is theoretically not needed to put a Link-Local address in scope of subnet.
> But it seems that the dhcp daemon do not start without that.
>
> That is what I want:
> [DHCPv6]-----(fe80::/64 + 2001:db8::15/64)--------[DHCP Relay]------(2a03:4920:100::/44)----[Clients]

Is that 2001:db8::15 the address of the server ? The server probably needs a prefix defining that includes that, assuming it's working in a similar fashion to DHCPv4.

Thus, as I read the man pages (learning as I go !), you probably need an empty subnet6 declaration :
subnet6 2001:db8::/64 {
}

The reason it's needed is that the server does not know that there aren't any locally connected clients. Therefore the assumption must be that a client could appear locally to eth2, and the server must know how to handle that client. Hence the need for the subnet6 declaration. That declaration can be empty since you (as the admin) know there won't be any local clients.

_______________________________________________
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