| Summary: | udhcpc: unicast renew fails sporadically | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | json.wago |
| Component: | Networking | Assignee: | unassigned |
| Status: | NEW --- | ||
| Severity: | normal | CC: | busybox-cvs, json.wago |
| Priority: | P5 | ||
| Version: | 1.34.x | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: |
config
pcap of the failed dhcp renew |
||
Created attachment 9634 [details]
pcap of the failed dhcp renew
|
Created attachment 9631 [details] config When using busybox udhcpc in combination with OpenDHCP server, its sometimes observed that udhcpc fails to handle/recognize the ACK for the unicast REQUEST (renew). The following broadcast renew is handled successfully. This behavior is not observed when using a different dhcp-server like dnsmasq or isc-dhcp-server. The unhandled dhcp ACK is seen on the interface that udhpc is listening on (via tcpdump).