| Summary: | BR2_SYSTEM_DHCP is removed from .config and breaks auto eth0 | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Patrice Blanchardie <patrice.blanchardie> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | buildroot, yann.morin.1998 |
| Priority: | P5 | ||
| Version: | 2017.08 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Patrice Blanchardie
2018-01-05 12:02:41 UTC
Should I stop relying on these ifup scripts and use a custom script with dhcp client at startup, as explained in https://busybox.net/~vda/no_ifup.txt? I removed ifupdown scripts and emptied cd /etc/network folder and added an init script that uses ifconfig up and down then calls udhcpc, I suppose it's the preferred way. Patrice, BR2_SYSTEM_DHCP is only available if you use the default skeleton, and any of busybox, ifupdown or systemd-networkd package. If you use your own custom skeleton, you are responsible for providing the necessary files (usually /etc/network/interfaces) in your custom skeleton. Regards, Yann E. MORIN. OK thanks for clarification |