Bug 5361 - resolvconf fail to change dns-nameservers from /etc/network/interfaces
Summary: resolvconf fail to change dns-nameservers from /etc/network/interfaces
Status: RESOLVED FIXED
Alias: None
Product: General Runtime
Classification: Runtime
Component: General Runtime (show other bugs)
Version: 1.5
Hardware: Other arm
: Medium normal
Target Milestone: 1.7
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-10-16 15:59 UTC by Davide Soldan
Modified: 2014-12-03 18:22 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
/etc/network/interfaces file (281 bytes, text/plain)
2014-11-20 11:15 UTC, Davide Soldan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Soldan 2013-10-16 15:59:12 UTC
branch: dora
commit id (meta-yocto): 56f39bcf2237c11508d82238b6292e4bfbfed764
          (meta-fsl-arm): 00f0cf377224829f450d99bdc4664ffe96623996
          (meta-fsl-arm-extra): 12af63db7719877fd191ed2aa921a455a04f677b
          (meta-fsl-demos): 393b0119d513f9abf7b0570ab0d32b81583dedca

Hi,
I'm running an image that inherit core-image on a nitrogen6x and with resolvconf-1.74-r0 package installed.

I want to change the ip of the dns-nameservers in /etc/network/interfaces for eth0. After changing the interfaces file I cannot update /etc/resolv.conf with neither of the commands;
- resolvconf -a eth0 (it hangs and doesn't return)
- resolvconf -u (it returns with no return messages)
- resolvconf -d eth0 (does nothing)
- ifdown eth0, ifup eth0
- reboot

so I cannot reflect the change made in /etc/network/interfaces...
Comment 1 Saul Wold 2013-12-16 23:14:57 UTC
Resolvconf -a is not intended to be run from the command line, it's designed to 
take input from stdin via the dhcp client enter hook, ppp or  ifdown/ifup 
scripts, this might be why you are having issues.  Since this is a shell 
script, if you have further issues, please use sh -x to help better understand 
the failure.

So, even a reboot does not work?
Comment 2 Saul Wold 2013-12-16 23:15:07 UTC
.
Comment 3 Saul Wold 2014-01-14 19:15:40 UTC
Since I have not heard back, I am closing this out, please reopen and provide 
updates if we still feel this is a bug.
Comment 4 Davide Soldan 2014-01-15 16:14:04 UTC
Hi Saul,
excuse me for the late reply.
No, even a reboot does not work.
But maybe I'm doing the wrong things...my procedure is:
- I manually change the dns-nameservers entry (for example for eth0) in /etc/network/interfaces
- I try to update the /etc/resolv.conf file with resolvconf command
- reboot

maybe is not the right way to change dns-nameserver informations?
Comment 5 Saul Wold 2014-11-19 16:46:41 UTC
Davide, I am still working this one in the background, I have a new question: 
what network management are you using?  it's it just static,  busybox with 
udhcp,  the actual dhcp client or connman or ???, what exactly are you setting 
in your /etc/network/interfaces file (full entry if possible).  

I think I have finally made some progress on this!  It seems that the 
resolvconf package is not being installed correctly onto the root filesystem on 
the target image, and even then it relies on bash'isms that may not be 
available with Busybox.
Comment 6 Davide Soldan 2014-11-20 11:15:21 UTC
Created attachment 2251 [details]
/etc/network/interfaces file
Comment 7 Davide Soldan 2014-11-20 11:20:14 UTC
Hi Saul,
the network management is static. I attached my /etc/network/interfaces file.
The behavior is always the same: no updates to /etc/resolv.conf
Comment 8 Diego 2014-11-25 09:50:15 UTC
(In reply to comment #5)
> Davide, I am still working this one in the background, I have a new
> question: 
> what network management are you using?  it's it just static,  busybox with 
> udhcp,  the actual dhcp client or connman or ???, what exactly are you
> setting 
> in your /etc/network/interfaces file (full entry if possible).  
> 
> I think I have finally made some progress on this!  It seems that the 
> resolvconf package is not being installed correctly onto the root filesystem
> on 
> the target image, and even then it relies on bash'isms that may not be 
> available with Busybox.

I've tested v2 patch:
http://patches.openembedded.org/patch/83771/
and it works fine for me for both dhcp and static configurations.