Fix PD for DHCPv6

[alpha_one_x86]

Hi,

How fix my PD for DHCPv6:

subnet6 2803:1920:0:1::/64 {
    option dhcp6.name-servers 2803:1920:0:1::1, 2001:4860:4860::8888;
        prefix6 2803:1920:0:2:: 2803:1920:0:ff:: /64;

    host laptop{
        hardware ethernet b8:2a:72:9e:2a:26;
        fixed-address6 2803:1920:0:1::2;
    }

    host test{
        hardware ethernet 80:14:a8:5f:32:e4;
        fixed-address6 2803:1920:0:1::3;
    }

    host test2{
        hardware ethernet 80:14:a8:87:d2:15;
        fixed-address6 2803:1920:0:1::4;
    }
}

Cheers

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

[Patrick Cervicek]

Be more verbose please:
What is PD?
What does not work with your configuration?
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Patrick Cervicek]

>          prefix6 2803:1920:0:2:: 2803:1920:0:ff:: /64;
try /56


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

[Rudy Zijlstra]

Hi,

Op 03-01-18 om 14:05 schreef alpha_one_x86:

Hi,

How fix my PD for DHCPv6:

subnet6 2803:1920:0:1::/64 {
    option dhcp6.name-servers 2803:1920:0:1::1, 2001:4860:4860::8888;
        prefix6 2803:1920:0:2:: 2803:1920:0:ff:: /64;

    host laptop{
        hardware ethernet b8:2a:72:9e:2a:26;
        fixed-address6 2803:1920:0:1::2;
    }

    host test{
        hardware ethernet 80:14:a8:5f:32:e4;
        fixed-address6 2803:1920:0:1::3;
    }

    host test2{
        hardware ethernet 80:14:a8:87:d2:15;
        fixed-address6 2803:1920:0:1::4;
    }
}

Cheers

Additionally, move the host definitions  out of the subnet definitions. host definitions are always global

Cheers

Rudy

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

[Steven Carr]

On 3 January 2018 at 13:05, alpha_one_x86
<[hidden email]> wrote:
>     host laptop{
>         hardware ethernet b8:2a:72:9e:2a:26;
>         fixed-address6 2803:1920:0:1::2;
>     }

Additionally, host declarations for IPv6 don't support hardware
ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
need to find and use the DUID of the client, example:

host laptop {
            host-identifier option dhcp6.client-id
00:01:00:01:4a:1f:ba:e3:60:b9:1f:01:23:45;
            fixed-address6 2803:1920:0:1::2;
}
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Henri Wahl]

> Additionally, host declarations for IPv6 don't support hardware
> ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
> need to find and use the DUID of the client, example:

Or use dhcpy6d which supports client MAC addresses. See
https://dhcpy6d.ifw-dresden.de for details.


--
Henri Wahl

IT Department
Leibniz-Institut fuer Festkoerper- u.
Werkstoffforschung Dresden

tel: [phone] - 797
email: [hidden email]
https://www.ifw-dresden.de

Nagios status monitor Nagstamon: https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d: https://dhcpy6d.ifw-dresden.de

S/MIME: https://nagstamon.ifw-dresden.de/pubkeys/smime.pem
PGP: https://nagstamon.ifw-dresden.de/pubkeys/pgp.asc

IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Burkard Hillebrands, Dr. Doreen Kirmse

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

[Craig Huckabee]

> On Jan 3, 2018, at 10:48 AM, Steven Carr <[hidden email]> wrote:
>
> On 3 January 2018 at 13:05, alpha_one_x86
> <[hidden email]> wrote:
>>    host laptop{
>>        hardware ethernet b8:2a:72:9e:2a:26;
>>        fixed-address6 2803:1920:0:1::2;
>>    }
>
> Additionally, host declarations for IPv6 don't support hardware
> ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
> need to find and use the DUID of the client, example:
>
> host laptop {
>            host-identifier option dhcp6.client-id
> 00:01:00:01:4a:1f:ba:e3:60:b9:1f:01:23:45;
>            fixed-address6 2803:1920:0:1::2;
> }

hardware ethernet works just fine if your network supports RFC6939 and you are on a fairly recent (> 4.3.4) release that also supports it.

—Craig



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

[sthaug]

> > Additionally, host declarations for IPv6 don't support hardware
> > ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
> > need to find and use the DUID of the client, example:
>
> Or use dhcpy6d which supports client MAC addresses. See
> https://dhcpy6d.ifw-dresden.de for details.

You still can't be sure it works, because the DUID doesn't necessarily
contain a MAC address.

Steinar Haug, Nethelp consulting, [hidden email]
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[alpha_one_x86]

For now this part work.

hardware ethernet b8:2a:72:9e:2a:26;

The unique problem is the delegated prefix assigned is random.
I need a fixed delegated prefix.

Cheers,

On 01/03/18 19:49, [hidden email] wrote:

Additionally, host declarations for IPv6 don't support hardware
ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
need to find and use the DUID of the client, example:

Or use dhcpy6d which supports client MAC addresses. See
https://dhcpy6d.ifw-dresden.de for details.

You still can't be sure it works, because the DUID doesn't necessarily
contain a MAC address.

Steinar Haug, Nethelp consulting, [hidden email]
_______________________________________________
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

[alpha_one_x86]

If you prefer in this case:

     host laptop{
         hardware ethernet b8:2a:72:9e:2a:26;
         fixed-address6 2803:1920:0:1::2;
     }

I need route the prefix 2803:1920:0:9::/64 via 2803:1920:0:1::2
Then for me, it's important for the mac address b8:2a:72:9e:2a:26, have
aisgned fixed-address6 2803:1920:0:1::2 and prefix delegation
2803:1920:0:9::/64

On 01/03/18 22:38, alpha_one_x86 wrote:

>
> For now this part work.
>
> hardware ethernet b8:2a:72:9e:2a:26;
>
> The unique problem is the delegated prefix assigned is random.
> I need a fixed delegated prefix.
>
> Cheers,
>
> On 01/03/18 19:49, [hidden email] wrote:
>>>> Additionally, host declarations for IPv6 don't support hardware
>>>> ethernet (as far as I'm aware), DHCPv6 doesn't use MAC addresses, you
>>>> need to find and use the DUID of the client, example:
>>> Or use dhcpy6d which supports client MAC addresses. See
>>> https://dhcpy6d.ifw-dresden.de  for details.
>> You still can't be sure it works, because the DUID doesn't necessarily
>> contain a MAC address.
>>
>> Steinar Haug, Nethelp consulting,[hidden email]
>> _______________________________________________
>> dhcp-users mailing list
>> [hidden email]
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
> --
> alpha_one_x86/BRULE Herman<[hidden email]>
> Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management
> IT, OS, technologies, research & development, security and business department
>
>
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users

--
alpha_one_x86/BRULE Herman <[hidden email]>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management
IT, OS, technologies, research & development, security and business department

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

[Henri Wahl]

> You still can't be sure it works, because the DUID doesn't necessarily
> contain a MAC address.

dhcpy6d takes the MAC address from neighbor cache - no DUID involved.


--
Henri Wahl

IT Department
Leibniz-Institut fuer Festkoerper- u.
Werkstoffforschung Dresden

tel: [phone] - 797
email: [hidden email]
https://www.ifw-dresden.de

Nagios status monitor Nagstamon: https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d: https://dhcpy6d.ifw-dresden.de

S/MIME: https://nagstamon.ifw-dresden.de/pubkeys/smime.pem
PGP: https://nagstamon.ifw-dresden.de/pubkeys/pgp.asc

IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Burkard Hillebrands, Dr. Doreen Kirmse

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

[Christian Kratzer]

Hi,

On Fri, 5 Jan 2018, Henri Wahl wrote:

>> You still can't be sure it works, because the DUID doesn't necessarily
>> contain a MAC address.
>
> dhcpy6d takes the MAC address from neighbor cache - no DUID involved.

which means that it always needs to be on the network and cannot be behind a relay.

Greetings
Christian

--
Christian Kratzer                   CK Software GmbH
Email:   [hidden email]               Wildberger Weg 24/2
Phone:   [phone] - 0       D-71126 Gaeufelden
Fax:     [phone] - 9       HRB 245288, Amtsgericht Stuttgart
Mobile:  [phone]           Geschaeftsfuehrer: Christian Kratzer
Web:     http://www.cksoft.de/
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Henri Wahl]

>
>>> You still can't be sure it works, because the DUID doesn't necessarily
>>> contain a MAC address.
>>
>> dhcpy6d takes the MAC address from neighbor cache - no DUID involved.
>
> which means that it always needs to be on the network and cannot be
> behind a relay.
>
>

Yes, this is the price to pay to be able to use the MACs.

--
Henri Wahl

IT Department
Leibniz-Institut fuer Festkoerper- u.
Werkstoffforschung Dresden

tel: [phone] - 797
email: [hidden email]
https://www.ifw-dresden.de

Nagios status monitor Nagstamon: https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d: https://dhcpy6d.ifw-dresden.de

S/MIME: https://nagstamon.ifw-dresden.de/pubkeys/smime.pem
PGP: https://nagstamon.ifw-dresden.de/pubkeys/pgp.asc

IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Burkard Hillebrands, Dr. Doreen Kirmse


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