DUID across VLANs

[Miloslav Hůla]

Hi,

I'm solving issue with DHCPv6 and Windows 10 connected by two interfaces
into two different VLANs. One for ordinary data, the other one for
network management.

Now, we have stations registered by MACs.

host milo.example.com {
         hardware ethernet 00:13:3b:9c:9f:ab;
         fixed-address6 2002:817:2:1100::ffff;
}

I'm aware that this is not the "RFC way", but registration by DUID would
result into the same issue.

The problem is, that OS uses the same DUID for all ethernet interfaces.
It is nice from the end-user point of view, cable can be plugged into
any interface. But I need two separated IPv6 addresses for admin access
and some netadmin tests.

Is it possible somehow to achieve that?

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

[Enno Rey]

Hi,

On Tue, Sep 12, 2017 at 10:28:44AM +0200, Miloslav H??la wrote:

> Hi,
>
> I'm solving issue with DHCPv6 and Windows 10 connected by two interfaces
> into two different VLANs. One for ordinary data, the other one for
> network management.
>
> Now, we have stations registered by MACs.
>
> host milo.example.com {
>          hardware ethernet 00:13:3b:9c:9f:ab;
>          fixed-address6 2002:817:2:1100::ffff;
> }
>
> I'm aware that this is not the "RFC way", but registration by DUID would
> result into the same issue.
>
> The problem is, that OS uses the same DUID for all ethernet interfaces.
> It is nice from the end-user point of view, cable can be plugged into
> any interface. But I need two separated IPv6 addresses for admin access
> and some netadmin tests.
>
> Is it possible somehow to achieve that?

unfortunately no (at least afaik).
by design the DUID is generated once per system and hence does not/should not (by design) depend on or be associated with an individual interface.

however if you use the MAC address for the reservations (and all devices involved support RFC 6939) you should be able to achieve what you have in mind (different DHCPv6-issued addresses for different interfaces).

cheers

Enno





>
> Thank you, Milo
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users

--
Enno Rey

ERNW GmbH - Carl-Bosch-Str. 4 - 69115 Heidelberg - www.ernw.de
Tel. [phone] - Fax [phone] - Cell [phone]

Handelsregister Mannheim: HRB 337135
Geschaeftsfuehrer: Matthias Luft, Enno Rey

=======================================================
Blog: www.insinuator.net || Conference: www.troopers.de
Twitter: @Enno_Insinuator
=======================================================
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Simon Hobson]

Miloslav Hůla <[hidden email]> wrote:

> I'm solving issue with DHCPv6 and Windows 10 connected by two interfaces into two different VLANs. One for ordinary data, the other one for network management.
>
> Now, we have stations registered by MACs.
>
> host milo.example.com {
>        hardware ethernet 00:13:3b:9c:9f:ab;
>        fixed-address6 2002:817:2:1100::ffff;
> }
>
> I'm aware that this is not the "RFC way", but registration by DUID would result into the same issue.

Have you tried specifying multiple addresses in the fixed-address6 statement ? With the v4 server, you can specify multiple addresses, and it'll pick one that's applicable to the client's network.

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

[Miloslav Hůla]

Dne 2017-09-12 v 19:56 Simon Hobson napsal(a):

> Miloslav Hůla <[hidden email]> wrote:
>
>> I'm solving issue with DHCPv6 and Windows 10 connected by two interfaces into two different VLANs. One for ordinary data, the other one for network management.
>>
>> Now, we have stations registered by MACs.
>>
>> host milo.example.com {
>>         hardware ethernet 00:13:3b:9c:9f:ab;
>>         fixed-address6 2002:817:2:1100::ffff;
>> }
>>
>> I'm aware that this is not the "RFC way", but registration by DUID would result into the same issue.
>
> Have you tried specifying multiple addresses in the fixed-address6 statement ? With the v4 server, you can specify multiple addresses, and it'll pick one that's applicable to the client's network.

I did. When tried to use multiple addresses: ERROR Only one fixed
address declaration per host.

It looks like that multiple host declarations with the same MAC would work.

Thank you for the tip.

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

[Miloslav Hůla]

Dne 2017-09-12 v 10:40 Enno Rey napsal(a):

> Hi,
>
> On Tue, Sep 12, 2017 at 10:28:44AM +0200, Miloslav H??la wrote:
>> Hi,
>>
>> I'm solving issue with DHCPv6 and Windows 10 connected by two interfaces
>> into two different VLANs. One for ordinary data, the other one for
>> network management.
>>
>> Now, we have stations registered by MACs.
>>
>> host milo.example.com {
>>           hardware ethernet 00:13:3b:9c:9f:ab;
>>           fixed-address6 2002:817:2:1100::ffff;
>> }
>>
>> I'm aware that this is not the "RFC way", but registration by DUID would
>> result into the same issue.
>>
>> The problem is, that OS uses the same DUID for all ethernet interfaces.
>> It is nice from the end-user point of view, cable can be plugged into
>> any interface. But I need two separated IPv6 addresses for admin access
>> and some netadmin tests.
>>
>> Is it possible somehow to achieve that?
>
> unfortunately no (at least afaik).
> by design the DUID is generated once per system and hence does not/should not (by design) depend on or be associated with an individual interface.
>
> however if you use the MAC address for the reservations (and all devices involved support RFC 6939) you should be able to achieve what you have in mind (different DHCPv6-issued addresses for different interfaces).

Thank you for the tip on RFC 6939, I'll check our relay agent devices
for support.

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