udhcpc6 missing source address

[Denys Vlasenko]

On Tue, Dec 13, 2022 at 4:58 PM John Lemonovich
<john.lemonovich at foresys.com> wrote:
>
> Thanks for the replies.  Yes David, it's also my understanding per the spec, that the client's link-local address must be included for the solicit message.

Where does it say that in https://www.rfc-editor.org/rfc/rfc3315 ?

>  The reply from the server is unicast.  What do you mean by the proper IPv6 version of the script...to which script are you referring to?  Can you possibly show an example?
>
> Just out of curiosity, has it ever been tested or known to work with a DHCPv6 server then?

I wrote the code based on IPv4. Couldn't test it.
Surprisingly, people reported that it did work on the first try
(with a number of bugs quickly discovered and hopefully fixed).

I have no doubt it still has obvious bugs due to limited exposure.

> I've tried with 3 different DHCP servers and they all seem to NOT want to reply with a broadcast and are expecting to receive an address (e.g.: the link local address) for a reply.  My windows machines and my Ubuntu/Cent-OS machines are doing it this way - they are not sending all 0's for the source address for their requests.

Here you mean "source address of the IPv6 packet", or some DHCPv6 option?

Can you tcpdump clients which do acquire a lease from these servers?