All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9481] New: NetworkManager/Ping unable to resolve domains
Date: Fri, 16 Dec 2016 18:17:36 +0000	[thread overview]
Message-ID: <bug-9481-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9481
           Summary: NetworkManager/Ping unable to resolve domains
           Product: buildroot
           Version: 2016.11
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: nnabavian at sonendo.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

NetworkManager/Ping fails to resolve domain names, responds with "bad address".

This issue was seen on arm imx6 with ipv6.

By default NetworkManager.conf has set dns=dnsmasq
Although dnsmasq was not built as a part of the packages.

This issue was fixed by setting dns=none.

Also, the resolve.conf was a broken link.
This was fixed by reestablishing the symlink to the proper path.

ln -s /run/NetworkManager/resolv.conf /etc/resolv.conf


With theses changes NetworkManager was able to ping and resolve domains names.

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

             reply	other threads:[~2016-12-16 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 18:17 bugzilla at busybox.net [this message]
2017-02-13 20:52 ` [Buildroot] [Bug 9481] NetworkManager/Ping unable to resolve domains bugzilla at busybox.net
2019-08-10 23:23 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-9481-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.