[Dnsmasq-discuss] dhcpv6 duid gen

[Jan Seiffert]

2012/3/1 Vladislav Grishenko <themiron at mail.ru>:
> Hi, Simon
>
> Currenly 2.60 uses first interface and its hw type as (time) link-layer duid
> source with exceptions of loopback and ppp.
> RFC3315 says "The hardware type MUST be a valid hardware type assigned by
> the IANA, as described in RFC 826", which describes only 48bit-long ethernet
> addresses.
> So, if there's any kind non-ethernet interfaces in system, which has first
> index, dnsmasq duid generation is obviously wrong.
> Example - 6to4 tunnel interfaces
> sit0      Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-4D-62-00-00-00-00-00-00-00-00
>          NOARP  MTU:1480  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> So, instead of checking device flags, it's better to check against encap
> type and allow only ether&ieee802, like dhcp6s/wide-dhcpv6 do.

Hold it, there is IEEE1394, a.k.a Firewire missing.
RFC3164
Firewire is the "only" transport with a  EUI-64 instead of the classic
Mac-Adress with 48 bits.

[snip]
> Best Regards, Vladislav Grishenko
>

Greetings
Jan

-- 
˙qɐɥ ʇɟnɐʞǝƃ ʎɐqǝ ıǝq ɹnʇɐʇsɐʇ ǝuıǝ ɹıɯ ɥɔı sɐp lɐɯ ǝʇzʇǝl sɐp ʇsı sɐp
'ʇɯɯɐpɹǝʌ