Re: Fedora 24: Network inoperable after a manual NetworkManager restart

2016-07-07 Thread Joachim Backes
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,

Re: Fedora 24: Network inoperable after a manual NetworkManager restart

2016-07-07 Thread Rami Rosen
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 gett

Re: Fedora 24: Network inoperable after a manual NetworkManager restart

2016-07-06 Thread Joachim Backes
On 07/06/16 15:54, Rami Rosen wrote: > Hi, Joachim, > > Regarding DNS resolving: the /etc/resolv.conf, which is generated by > Network Manager, as responsible for DNS resolving > Can you please post the output of > cat /etc/reslov.conf > after fresh reboot, before restarting NetworkManager, when

Re: Fedora 24: Network inoperable after a manual NetworkManager restart

2016-07-06 Thread Rami Rosen
Hi, Joachim, Regarding DNS resolving: the /etc/resolv.conf, which is generated by Network Manager, as responsible for DNS resolving Can you please post the output of cat /etc/reslov.conf after fresh reboot, before restarting NetworkManager, when ping succeeds, and after restargin NetworkManager,