Closed chuacw closed 5 years ago
The trace is generated by one of the ubus calls in the dhcpv6 script; nothing can be done in the odhcp6c code to fix this trace
I get this also and the interface does not get it's assigned address.
Any clues how to debug this in ubus?
You can add logger statements in the dhcv6 script to find out which cmd triggers this trace
I already did. The problem is that $INTERFACE
is not always set and the script ends up with ubus calls where interface: ""
.
I ran this command:
odhcp6c -s /lib/netifd/dhcpv6.script -Ntry -P0 -t120 eth1.2
I got this response:
Can the code be improved to specify what is "Not found"? What is the something that is not found?