New: BR2_SYSTEM_DHCP is removed from .config and breaks auto eth0

https://bugs.busybox.net/show_bug.cgi?id=10636

Bug ID: 10636
Summary: BR2_SYSTEM_DHCP is removed from .config and breaks
auto eth0
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: patrice.blanchardie at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Hi,

The BR2_SYSTEM_DHCP config is needed if you want the package ifupdown-scripts to add automatic eth0 configuration to /etc/network/interfaces.

It's not available in menuconfig.
If you add it to the defconfig and make, it will be removed. You have to add it to the .config manually and make if you want proper files to be generated.

I'm using a custom skeleton and busybox.

Why is it suppressed? Am I doing something wrong?

Thanks, happy new year!

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10636

--- Comment #1 from Patrice Blanchardie <[email protected]> --- 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?

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10636

--- Comment #2 from Patrice Blanchardie <[email protected]> --- 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.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10636

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998 at free.fr
         Resolution|---                         |INVALID

--- Comment #3 from Yann E. MORIN <[email protected]> --- 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.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10636

--- Comment #4 from Patrice Blanchardie <[email protected]> --- OK thanks for clarification

You are receiving this mail because:
You are on the CC list for the bug.