New: NetworkManager/Ping unable to resolve domains
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.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9481] NetworkManager/Ping unable to resolve domains
https://bugs.busybox.net/show_bug.cgi?id=9481
--- Comment #1 from Petr Vorel <[email protected]> --- Could you please submit config file which you used for it?
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.
[Buildroot] [Bug 9481] NetworkManager/Ping unable to resolve domains
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=9481
Carlos Santos <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NEEDINFO
Assignee|unassigned at buildroot.uclibc |unixmania at gmail.com
|.org |--- Comment #2 from Carlos Santos <[email protected]> --- Closing, since the OP never provided the defconfig requested by Peter Vorel in comment #1.
Signature · 2 lines
You are receiving this mail because: You are on the CC list for the bug.