OpenWrt 23.05.2 - Service Release

openwrtforever · November 22, 2023, 4:08am

Its not 32 bits now it is 64 bits.

Look at my old post What's with the 32-bit restriction with IPv6-Suffix for static leases?

Now it is 64 bits and it worked for me.

github.com/openwrt/odhcpd

odhcpd does not accept a static hostid greater than 32 bits!

opened 05:09AM - 12 Oct 14 UTC

sgargbugreporter

Hardware: WDR-3600 using OpenWRT Barrier Breaker 14.07 I want to provide the la…st 64 bits of the IPv6 address to my host using DHCPv6 using odhcpd. Have referred to: https://miceliux.com/apuntesderoot/2014/09/07/static-dhcpv6-leases-in-openwrt/ The "/etc/config/dhcp" file contains: ``` config host option name 'hostname' option mac '00:xx:xx:xx:98:03' option ip '10.159.93.40' option duid '000100011b68071900xxxxxx9803' option hostid 'b3e6c2dba12bdf02' ``` Note that the hostid is 8 octets long, i.e: ``` b3e6:c2db:a12b:df02 ``` as it can be. However, this fails and odhcpd provides my host a random IPv6 address: ``` odhcpd[10534]: DHCPV6 SOLICIT IA_NA from 000100011b68071900xxxxxx9803 on br-lan: ok 2001:xxxx:e383:938::9e1/128 fd00:db80:0:938::9e1/128 odhcpd[10534]: DHCPV6 REQUEST IA_NA from 000100011b68071900xxxxxx9803 on br-lan: ok 2001:xxxx:e383:938::9e1/128 fd00:db80:0:938::9e1/12 ``` A similar case happens in the following case (9x4 = 36 bits longs): ``` option hostid 'b3e6c2dbf' ``` which should actually be interpreted as: 0000:000b:3e6c:2dbf but is not! However, the following works: ``` option hostid 'b3e6c2db' ``` and I get: ``` odhcpd[10153]: DHCPV6 SOLICIT IA_NA from 000100011b68071900xxxxxx9803 on br-lan: ok 2001:xxxx:e383:938::b3e6:c2db/128 fd00:db80:0:938::b3e6:c2db/128 odhcpd[10153]: DHCPV6 SOLICIT IA_NA from 000100011b68071900xxxxxx9803 on br-lan: ok 2001:xxxx:e383:938::b3e6:c2db/128 fd00:db80:0:938::b3e6:c2db/128 odhcpd[10153]: DHCPV6 REQUEST IA_NA from 000100011b68071900xxxxxx9803 on br-lan: ok 2001:xxxx:e383:938::b3e6:c2db/128 fd00:db80:0:938::b3e6:c2db/128 ``` which is being interpreted correctly as: 0000:0000:3e6c:2dbf I wonder how is this handled? I have a /48 from he.net and I am routing a /64 from that.