On 07/07/16 14:51, Rami Rosen wrote:
Hi, Joachim,
Apologies, I could only answer just now. The problem is, for sure,
that restarting the Network Manager did not create the "nameserver
192.168.100.1" entry in /etc/resolv.conf. This is the entry which is
solely responsible for DNS name resolving, and its omission deprives
you from getting an answer to your ping request you mentioned.
I am unsure as to what is the exact reason.
I would suggest the following three actions, to further try to
understand the issue:
Hi Rami,
Today morning, I filed a BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1353184
The BZ seems now to be under examination.
1) post here the content of /etc/NetworkManager/NetworkManager.conf
see attachment!
2) if this config file has "dns=dnsmasq" entry, try to
comment it and
restart NetworkManager, then see if /etc/resolv.conf is empty or not.
3) tell us if selinux is enabled on this machine (the output of
"getenforce" from the command line)
/etc/selinux/config has a line:
SELINUX=disabled
Kind regards and thanks for your efforts
Joachim Backes
--
Fedora release 24 (Twenty Four)
Kernel-4.6.3-300.fc24.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
http://www-user.rhrk.uni-kl.de/~backes/