Created attachment 9700 [details]
Patch to encode option data as hex string oin env variable if not directly supported in dhcpv6 client

Using busybox v1.36.1

When running a DHCPv6 client and adding user defined options, using the -O, on the udhcpc6 command line, the data returned by the DHCP server is not accessible in the script defined in the -s command line option.

The use of the -O option works for DHCPv4 clients with the option data being processed and exposed as an environment variable.  E.g. with "-O 143" on the command line any returned data would be encoded as a hex string under the variable opt143, which is in turn accessible in the script referenced by the -s CLI option (as $opt143).

This does not seem to be implemented for the DHCPv6 client.

To address this I have created a local patch file that replicates the behavior I observed with DHCPv4 (see attachment)

I hope this can be used to address this bug...