|
Bugzilla – Full Text Bug Listing |
| Summary: | busybox udhcpc: event PROG missing | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Dominique Leuenberger <dimstar> |
| Component: | Other | Assignee: | Ihno Krumreich <ihno> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | ihno, kukuk, mpdesouza, radoslav.kolev |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Marcos de Souza enabled it, don't know why he did it, changes file does not contain any usefull hint. In general, we should not support this as yet another way to setup the network. Sicne there are some obscure valid use cases for udhcpc, I didn't disable it but correctly configured the build options. But there will be no script to set up the system network with the received data, this is something the users have to do themself for their use cases. udhcpc will not be supported as standard dhcp client. I added notes about this to the package description. (In reply to Thorsten Kukuk from comment #1) > Marcos de Souza enabled it, don't know why he did it, changes file does not > contain any usefull hint. > In general, we should not support this as yet another way to setup the > network. So I added it to make it work with virtme-ng[1]. The tool passes a script[2] to it, so maybe that's why it worked in the end. [1]: https://github.com/arighi/virtme-ng/blob/1e9e35be70ff447aa919dd798de0b8e926ec54ec/virtme/guest/virtme-init#L217 [2]: https://github.com/arighi/virtme-ng/blob/1e9e35be70ff447aa919dd798de0b8e926ec54ec/virtme/guest/virtme-udhcpc-script |
Using buysbox udhcp to retreive a DHCP address and configure the host does not work using busybox 1.36.1 The issue at hand seems to be that busybox udhcpc requires a client script (/usr/share/udhcpc/default.script according to upstream README) Our manpage indicates this being 'deconfigured' though: udhcpc udhcpc [-fbqRB] [-t N] [-T SEC] [-A SEC|-n] [-i IFACE] [-s PROG] [-p PIDFILE] [-oC] [-r IP] [-V VENDOR] [-F NAME] [-x OPT:VAL]... [-O OPT]... -i IFACE Interface to use (default ) -s PROG Run PROG at DHCP events (default ) note the empty default value for -s PROG. Without this script present, though, busybox udhcpc does request the IP address from the server, takes the lease, but never configures the network card