Bug 8701 - udhcpc: network setting not applied after receiving a lease
Summary: udhcpc: network setting not applied after receiving a lease
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: 1.24.x
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-16 09:58 UTC by felix.wiedenroth
Modified: 2016-02-18 07:06 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description felix.wiedenroth 2016-02-16 09:58:35 UTC 
Hello, 

I experience a bug, when I try to use latest Busybox-Version on Linux.

The Linux-Distribution is Slackware, Version 13.37 64-Bit.

When I call ./busybox-x86_64 udhcpc the IP obtained from the dhcp-Server is not set - Broadcast, DNS, Netmask is of course also not set. Program goes to background and does nothing.

Screen output is as follows:

bash-4.1# ./busybox-x86_64 udhcpc   
udhcpc (v1.24.0.git) started
Sending discover...
Sending select for 149.172.109.174...
Lease of 149.172.109.174 obtained, lease time 2375
bash-4.1# 

Is that a known issue? Or is this specific to my Linux-Distribution?

Regards,

Felix
Comment 1 Mike Frysinger 2016-02-18 07:06:34 UTC 
please post the .config file you're using

be aware that udhcp runs a script when it gets a response and that script is the one responsible for actually configuring interfaces.  from the help:
config UDHCPC_DEFAULT_SCRIPT
    string "Absolute path to config script"
    default "/usr/share/udhcpc/default.script"
    depends on UDHCPC
    help
      This script is called after udhcpc receives an answer. See
      examples/udhcp for a working example. Normally it is safe
      to leave this untouched.

so you need to make sure you've installed a script at that location.