trouble running opkg update - problem with name resolution.

Eric_Fort · July 1, 2013, 8:50am

when I run:

opkg update

on my beaglebone it fails with the following errors:

opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/base/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/machine/beaglebone/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/debug/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/gstreamer/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/all/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/perl/Packages.gz, wget returned 1.
opkg_download: Failed to download http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/python/Packages.gz, wget returned 1.

opkg install

fails with similar errors, i.e. it seems wget has a problem with the hostname or name resolution. any idea why?

The bone can get out to the internet just fine (though I wish traceroute were installed) as I can ping external hosts such as 4.2.2.4. trying to ping by hostname such as

ping google.com

yields

ping: unknown host google.com

route looks proper as it outputs:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.1 * 255.255.255.255 UH 0 0 0 eth0
192.168.7.0 * 255.255.255.252 U 0 0 0 usb0

/etc/resolv.conf looks a bit suspect though as it’s contents are below:

Generated by Connection Manager

nameserver 127.0.0.1

when the bone booted it got it’s address from the network dhcp server. should it have not set up it’s default nameservers as well?

note adding a valid nameserver line to /etc.resolv.conf instantly fixed the problem. Now how can this be set to do so automatically when dhcp dynamically configures the angstrom host?

Thanks,

Eric

Johan_Henselmans · July 2, 2013, 7:06am

Sometimes updating the kernel causes the dns server to fail locally. Add an extra nameserver to /etc/resolv.conf.

I do this via a sh script:

advaitjavadekar · January 24, 2016, 5:19pm

I am having the exact same problem. Please can you help me out with steps to avoid this.