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,
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
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
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,
Hi F24 users,
after a manual restart of NetworkManager (for some reasons) with
sudo systemctl restart NetworkManager.service
having some problems:
1. The Networkmanager icon disappeared from the dashboard
of the GNOME3 desktop
2. DNS is no more operable: trying to access remote hosts
by a hos
