[opensuse-factory] New router - cannot connect to the Internet
Hello Firstly apologies for formatting, not following proper etiquette etc as I am using my phone at the moment. I've just upgraded my Internet connection and as a result I have had to switch routers. The new router works fine with everything in the house except my Tumbleweed pc, so there must be something wrong with my connection settings. I use networkmanager on the plasma desktop. I currently have a wired ethernet connection configured (I've also tried creating a fresh one). As far as I can tell from ifconfig I am getting an IP address from the router, but I cannot access the Internet (although I can access the router's configuration panel so there can't be a physical problem). When I issue a ping from the command line the result is "temporary failure on name resolution". What can I do to fix this? Many thanks in advance. Kind regards, Huw Sent from Blue -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14.03.2018 19:36, huw wrote:
Hello
Firstly apologies for formatting, not following proper etiquette etc as I am using my phone at the moment.
I've just upgraded my Internet connection and as a result I have had to switch routers. The new router works fine with everything in the house except my Tumbleweed pc, so there must be something wrong with my connection settings.
I use networkmanager on the plasma desktop. I currently have a wired ethernet connection configured (I've also tried creating a fresh one). As far as I can tell from ifconfig I am getting an IP address from the router, but I cannot access the Internet (although I can access the router's configuration panel so there can't be a physical problem).
When I issue a ping from the command line the result is "temporary failure on name resolution".
What can I do to fix this?
Many thanks in advance.
Kind regards, Huw
Sent from Blue
Hey, try `sudo netconfig update -f` in a terminal window. Greetings Fabian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 14 March 2018 18:39:30 GMT Fabian Niepelt wrote:
Hey,
try `sudo netconfig update -f` in a terminal window.
Greetings Fabian
As simple as that! That did it! THANK YOU very much Fabian; your quick and simple reply saved me hours of frustration! :D Out of interest, what did it do? Kind regards, Huw
On 14.03.2018 20:05, huw wrote:
On Wednesday, 14 March 2018 18:39:30 GMT Fabian Niepelt wrote:
Hey,
try `sudo netconfig update -f` in a terminal window.
Greetings Fabian
As simple as that! That did it! THANK YOU very much Fabian; your quick and simple reply saved me hours of frustration! :D
Out of interest, what did it do?
Kind regards, Huw
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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
On 03/14/2018 02:36 PM, huw wrote:
Hello
Firstly apologies for formatting, not following proper etiquette etc as I am using my phone at the moment.
I've just upgraded my Internet connection and as a result I have had to switch routers. The new router works fine with everything in the house except my Tumbleweed pc, so there must be something wrong with my connection settings.
I use networkmanager on the plasma desktop. I currently have a wired ethernet connection configured (I've also tried creating a fresh one). As far as I can tell from ifconfig I am getting an IP address from the router, but I cannot access the Internet (although I can access the router's configuration panel so there can't be a physical problem).
When I issue a ping from the command line the result is "temporary failure on name resolution".
What can I do to fix this?
Can you ping other devices on your LAN? Can you ping your ISPs gateway? What does "ip route show" indicate? Can you ping 8.8.8.8? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I had this happen to me a while back. As I recall, the issue was that
/etc/resolv.conf only contained an IPv6 address for a nameserver.
Adding another line with the IPv4 address of the router fixed it for
me.
Philip
On Wed, Mar 14, 2018 at 8:41 AM, James Knott
On 03/14/2018 02:36 PM, huw wrote:
Hello
Firstly apologies for formatting, not following proper etiquette etc as I am using my phone at the moment.
I've just upgraded my Internet connection and as a result I have had to switch routers. The new router works fine with everything in the house except my Tumbleweed pc, so there must be something wrong with my connection settings.
I use networkmanager on the plasma desktop. I currently have a wired ethernet connection configured (I've also tried creating a fresh one). As far as I can tell from ifconfig I am getting an IP address from the router, but I cannot access the Internet (although I can access the router's configuration panel so there can't be a physical problem).
When I issue a ping from the command line the result is "temporary failure on name resolution".
What can I do to fix this?
Can you ping other devices on your LAN? Can you ping your ISPs gateway? What does "ip route show" indicate? Can you ping 8.8.8.8?
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 14 March 2018 19:02:34 GMT Philip Tait wrote:
I had this happen to me a while back. As I recall, the issue was that /etc/resolv.conf only contained an IPv6 address for a nameserver. Adding another line with the IPv4 address of the router fixed it for me.
Philip
Thank you for your reply Philip. Fabian's suggestion worked for me, but I suspect your advice would have worked too as it did indeed seem like a name resolution issue specifically. Kind regards, Huw
On 03/14/2018 03:02 PM, Philip Tait wrote:
I had this happen to me a while back. As I recall, the issue was that /etc/resolv.conf only contained an IPv6 address for a nameserver. Adding another line with the IPv4 address of the router fixed it for me.
That shouldn't be a problem, provided that's a valid IPv6 address for a DNS server. My own resolv.conf shows 3 IPv6 addresses. One for my router/firewall and 2 for Google's DNS server IPv6 addresses. There are no IPv4 addresses listed. However, a good test is to manually configure 8.8.8.8 for DNS. If that works, then it's a local DNS issue. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 14 March 2018 18:41:34 GMT James Knott wrote:
Can you ping other devices on your LAN? Can you ping your ISPs gateway? What does "ip route show" indicate? Can you ping 8.8.8.8?
Hi James, thank you very much for replying. As you can see from my previous email, Fabian's suggestion worked. However just out of interest, I was able to ping anything using IP addresses and was even able to display the BBC's website in my browser by using one of its IP addresses. So the issue was something to do with name resolution specifically. Kind regards, Huw
participants (4)
-
Fabian Niepelt -
huw -
James Knott -
Philip Tait