On Wednesday, 14 March 2018 19:13:07 GMT Fabian Niepelt wrote:
Glad to hear that helped! It recreates the network configuration and forces replacement, including the resolv.conf. This file includes the DNS servers your host asks for DNS information. My guess is that the resolv.conf didn't get updated properly for your new router, so forcing it to update resolves the issue.
Greetings Fabian
Aha. I suspected that "resetting the connection" (in layman's terms) would fix it - however I thought that simply adding a new connection in the networkmanager applet would suffice. Apparently not. Out of interest, I briefly tried going back to the Yast networking service (wicked?) to see if that helped, and the symptoms were precisely the same. Kind regards, Huw