dhcpcd-discuss

On 01/03/18 21:24, jobhunts02@xxxxxxx wrote:
> How does the subnet prefix defined on the DHCP server for a pool take effect?

It's used to match incoming packets and decide what addresses to use.
It can also help determine what options to send, but there's no DHCPv6
option for prefix length.  So the DHCPv6 server can't send a prefix and
the client must deduce it from somewhere else.

> For example, if I have 2 different subnets with different prefixes, how would I enforce this?

With router advertisements.  And the client reacts to those by updating
its routing tables to tie the prefix to a network interface.


                Graham

> 
>> On Mar 1, 2018, at 6:28 AM, Roy Marples <roy@xxxxxxxxxxxx> wrote:
>>
>>> On 01/03/2018 02:44, jobhunts02@xxxxxxx wrote:
>>> On my server in dhcpd6.conf  the prefix length is 64:
>>> subnet6 2001:ed8:77b5::/64 {
>>>         range6                          2001:ed8:77b5:0:10:123:105:150 2001:ed8:77b5:0:10:123:105:155;
>>> }
>>> On my client, I am getting an address with a prefix length of 128:
>>> inet6 addr: 2001:ed8:77b5:0:10:123:105:155/128 Scope:Global
>>> Is this the expected behavior?
>>
>> Yes this is expected.
>> A DHCPv6 lease is not tied to any specific prefix.
>> The kernel will use the longest matching prefix as the out-going route.
>>
>> Roy
> 
> 

-- 
------------------------------

*Graham Breed*
Systems Developer, ApplianSys

ApplianSys House
Harry Weston Road
Coventry CV3 2UB

www.appliansys.com

*Our sales team sells by referral:*
Less time looking for customers, more time looking after them

ApplianSys Limited registered in England & Wales #: 07608382 at ApplianSys
House, Harry Weston Road, Coventry CV3 2UB