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@xxxxxxxxxxxxxx> http://www-user.rhrk.uni-kl.de/~backes/
# Configuration file for NetworkManager. # # See "man 5 NetworkManager.conf" for details. # # The directory /usr/lib/NetworkManager/conf.d/ can contain additional configuration # snippets installed by packages. These files are read before NetworkManager.conf # and have thus lowest priority. # The directory /etc/NetworkManager/conf.d/ can contain additional configuration # snippets. Those snippets override the settings from this main file. # # The files within one conf.d/ directory are read in asciibetical order. # # If /etc/NetworkManager/conf.d/ contains a file with the same name as # /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored. # Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can # put an empty file with the same name. # # If two files define the same key, the one that is read afterwards will overwrite # the previous one. [main] #plugins=ifcfg-rh,ibft [logging] # When debugging NetworkManager, enabling debug logging is of great help. # # Logfiles contain no passwords and little sensitive information. But please # check before posting the file online. You can also personally hand over the # logfile to a NM developer to treat it confidential. Meet us on #nm on freenode. # Please post full logfiles except minimal modifications of private data. # # You can also change the log-level at runtime via # $ nmcli general logging level TRACE domains ALL # However, usually it's cleaner to enable debug logging # in the configuration and restart NetworkManager so that # debug logging is enabled from the start. # # You will find the logfiles in syslog, for example via # $ journalctl -u NetworkManager # #level=TRACE #domains=ALL
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
