[opensuse] No Internet Access After 15.0 > 15.1
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection. I am using Leap 15.1 with KDE Plasma Version5.12.8, KDE Frameworks Version 5.55.0, and QT Version 5.9.7. I had a similar problem when I did a zypper dup from 42.3 to 15.0 some time ago, so I looked up what I did to resolve the problem then and tried it again. But it isn't working. Here are the two methods I tried: 1. -I switched network settings to wicked from Networkmanager -As root, I ran in terminal: netconfig update -f -I restarted the computer -I switched back to networkmanager Didn't fix the problem this time. 2. -In terminal as root, I ran: rm /etc/resolv.conf && rcnetwork restart Didn't work, so I tried separately: #rm /etc/resolv.conv #rcnetwork restart Didn't work. Anyone have a means to fix this problem? Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection.
...
Didn't work. Anyone have a means to fix this problem?
The first thing is to diagnose the problem, not to apply random solutions. So, did you got an IP address? As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf". Then if you do have an IP, next see if you have a route, so "ip route" (all work as user). Next is connectivity. Ping your router, then ping google at 8.8.8.8. Next is name solving, so ping google.com. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection. The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user). #ip route #
Next is connectivity. Ping your router, then ping google at 8.8.8.8. #ping 192.147.1.1 connect: Network is unreachable
Next is name solving, so ping google.com. #ping www.gosgle.com
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me #curl api.ipify curl: (6) api.ipify ~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi. ping: www.gosgle.com Name or service not known (I did spell google correctly when I tried to ping, just trying to get rid of the hyperlink in this email). Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection. The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me #curl api.ipify curl: (6) api.ipify
Both indicate inability to resolve names, but not necessarily that you have no internet access. If you haven't already, check your /etc/resolv.conf, next if you can ping the server(s) listed.
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address.
That looks a bit dodgy to me. ip addr is 192.147.1.1 and broadcast is 192.147.1.298 ?? The oui of '1c:2g:39' isn't listed at the IEEE. I guess you did some obscuring?
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user). #ip route
So no routes at all - not even a default. 'noprefixroute' from your config above prevents 192.147.1.0/24 being added too. -- Per Jessen, Zürich (15.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection.
The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me #curl api.ipify curl: (6) api.ipify
Both indicate inability to resolve names, but not necessarily that you have no internet access.
If you haven't already, check your /etc/resolv.conf, next if you can ping the server(s) listed. I tried to recreate the etc/resolv.conf file as my first step in trying to fix this problem, as I had to do when I had a similar problem using zypper dup to go from 42.3 to 15.0. My first post in this thread
On Mon, 2019-05-27 at 08:13 +0200, Per Jessen wrote: details how I used netconfig update -f, and also another method. The etc/resolv.conf file on my laptop is named resolv.conf.20180610- 203042 I looked at the etc/resolv.conf file using Kate on my laptop, and it only reads "# Generated by NetworkManager" without the quotes. I opened the etc/resolv.conf file, named etc/resolv.conf, the same way on my desktop, and it reads: ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! nameserver 191.147.1.1 In addition, on the laptop the file system is different for etc/resolv.conf. I have a black file icon with a question mark in the middle that is named resolv.conf. Opening it, it reads ### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY=' ' # # See also the netconfig(8) manual page and other documentation. # ### Call 'netconfig update -f to force adjusting of /etc/resolv.conf. nameserver 192.147.1.= When using the real ip address of my wifi router, I can ping it successfully. The NetworkManager icon on the taskbar has a red exclamation mark next to it, which I have understood to mean that I am connected to the wifi router but not to the internet.
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address.
That looks a bit dodgy to me. ip addr is 192.147.1.1 and broadcast is 192.147.1.298 ?? The oui of '1c:2g:39' isn't listed at the IEEE. I guess you did some obscuring?
Yes, I did.
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user).
#ip route
So no routes at all - not even a default. 'noprefixroute' from your config above prevents 192.147.1.0/24 being added too.
-- Per Jessen, Zürich (15.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [05-27-19 07:48]: [...]
I opened the etc/resolv.conf file, named etc/resolv.conf, the same way on my desktop, and it reads:
### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! nameserver 191.147.1.1
In addition, on the laptop the file system is different for etc/resolv.conf. I have a black file icon with a question mark in the middle that is named resolv.conf. Opening it, it reads
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig!
/etc/resolv.conf recently was moved to a symlink to /var/run/netconfig/resolv.conf you can correct your non-compliant box by root: ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf you may need to first mv /etc/resolv.conf to /var/run/netconfig/resolv.conf and maybe last netconfig update -f -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 27 May 2019 09:46:54 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Mark Misulich <munguanaweza@gmail.com> [05-27-19 07:48]: [...]
I opened the etc/resolv.conf file, named etc/resolv.conf, the same way on my desktop, and it reads:
### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! nameserver 191.147.1.1
In addition, on the laptop the file system is different for etc/resolv.conf. I have a black file icon with a question mark in the middle that is named resolv.conf. Opening it, it reads
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig!
/etc/resolv.conf recently was moved to a symlink to /var/run/netconfig/resolv.conf
That would be a mistake, since /var/run is a symlink to /run The correct link would be to /run/netconfig/<whatever> But /run is in any case a tmpfs so any contents are recreated on boot. So there's no point in copying a file to /run or /var/run. Whatever the solution is, it's not that.
you can correct your non-compliant box by
root: ln -s /var/run/netconfig/resolv.conf /etc/resolv.conf
you may need to first mv /etc/resolv.conf to /var/run/netconfig/resolv.conf
and maybe last netconfig update -f
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Misulich wrote:
When using the real ip address of my wifi router, I can ping it successfully. The NetworkManager icon on the taskbar has a red exclamation mark next to it, which I have understood to mean that I am connected to the wifi router but not to the internet.
I am no expert on NetworkManager, but I think that means "no active interface", at all. -- Per Jessen, Zürich (19.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection. The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me
That doesn't mean anything when done before the steps I mentioned. Do things in proper order.
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi.
You mention wifi, but what about the Ethernet? Because there is an IP on ethernet. A strange one. Please clarify your setup. Should WiFi be working, or ethernet, or both? The above says that your own address is 192.147.1.1, but then you ping the router at that address. Why?
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user). #ip route #
Next is connectivity. Ping your router, then ping google at 8.8.8.8. #ping 192.147.1.1 connect: Network is unreachable
Next is name solving, so ping google.com. #ping www.gosgle.com
Don't continue. Previous steps failed. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection.
The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi.
You mention wifi, but what about the Ethernet? Because there is an IP on ethernet. A strange one.
Please clarify your setup. Should WiFi be working, or ethernet, or both? I am not connected by an ethernet cable to the laptop, but I have tried both methods to see if I could connect to the internet. I'm not sure how to answer the question correctly. In Yast I have a configuration designated for the ethernet and a separate configuration for the wifi.
The above says that your own address is 192.147.1.1, but then you ping the router at that address. Why? I thought that was the address of the wifi router. Was I mistaken?
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user).
#ip route #
Next is connectivity. Ping your router, then ping google at 8.8.8.8.
#ping 192.147.1.1 connect: Network is unreachable
Next is name solving, so ping google.com.
#ping www.gosgle.com
Don't continue. Previous steps failed.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 13.52, Mark Misulich wrote:
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global
Notice that the broadcast addrees 298 is impossible, it is bigger than 255.
noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi.
It is not connected ad all via wifi.
You mention wifi, but what about the Ethernet? Because there is an IP on ethernet. A strange one.
Please clarify your setup. Should WiFi be working, or ethernet, or both? I am not connected by an ethernet cable to the laptop, but I have tried both methods to see if I could connect to the internet. I'm not sure how to answer the question correctly. In Yast I have a configuration designated for the ethernet and a separate configuration for the wifi.
Do you have an ethernet cable correctly connected?
The above says that your own address is 192.147.1.1, but then you ping the router at that address. Why? I thought that was the address of the wifi router. Was I mistaken?
It is your own address. There is no address for your router, as there is no route. However, ping for your own address also fails, which is strange. Unless you have written yourself that configuration, which is not correct. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Mon, 2019-05-27 at 14:45 +0200, Carlos E. R. wrote:
On 27/05/2019 13.52, Mark Misulich wrote:
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote: Ok, to try and remove confusion:
here is the correct readout on my laptop from ip addr with the ethernet cable connected. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan2: <BROADCAST,MULTICAST> mtu 1500 qdis mq state DOWN group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff inet 192.168.1.7/24 brd 192.168.1.255 scope gloabal noprefixroute dynamic eth0 valid_lft 85159sec preferred_lft 85159sec inte6 fe80::f07f:48de:cb67::3437/64 scope link noprefixroute valid_lft forever preferred_lft forever Here is the ip addr readout with the ethernet cable disconnected, using the wireless: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 18:5e::0f:3b:92:0f brd ff:ff:ff:ff:ff:ff Here is the readout of ip link with the ethernet cable connected: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 66:17::58:19:77:FE brd ff:ff:ff:ff:ff:ff 4: eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff This is the readout of ip link with the ethernet cable disconnected and using the wireless: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff Here is the readout of ip netconf with the ethernet cable connected: ipv4 dev lo forwarding off rp_filter strict mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv4 dev wlan2 forwarding off rp_filter strict mc_forwarding off prox_neigh off ignore_routes_with_linkdown off ipv4 dev eth0 forwarding off rp_filter loose mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv4 all forwarding off rp_filter strict mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv4 default fowarding off rp_filter strict mc_forwading off proxy_neigh off ignore_routes_with_linkdown off ipv6 dev lo forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 dev wlan2 forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 dev eth0 forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 all forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 default forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off Here is the readout of ip netconf using wireless with the ethernet cable disconnected: ipv4 dev lo forwarding off rp_filter strict mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv4 dev wlan2 forwarding off rp_filter strict mc_forwarding off prox_neigh off ignore_routes_with_linkdown off ipv4 all forwarding off rp_filter strict mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv4 default fowarding off rp_filter strict mc_forwading off proxy_neigh off ignore_routes_with_linkdown off ipv6 dev lo forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 dev wlan2 forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 all forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off ipv6 default forwarding off mc_forwarding off proxy_neigh off ignore_routes_with_linkdown off -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 18.36, Mark Misulich wrote:
On Mon, 2019-05-27 at 14:45 +0200, Carlos E. R. wrote:
On 27/05/2019 13.52, Mark Misulich wrote:
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote: Ok, to try and remove confusion:
here is the correct readout on my laptop from ip addr with the ethernet cable connected.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan2: <BROADCAST,MULTICAST> mtu 1500 qdis mq state DOWN group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff inet 192.168.1.7/24 brd 192.168.1.255 scope gloabal noprefixroute dynamic eth0 valid_lft 85159sec preferred_lft 85159sec inte6 fe80::f07f:48de:cb67::3437/64 scope link noprefixroute valid_lft forever preferred_lft forever
At this point, did you try the network verification steps I said? pings? Notice that your IP here is 192.168.1.7, so your router will be probably 192.168.1.1. or perhaps 192.168.1.254.
Here is the ip addr readout with the ethernet cable disconnected, using the wireless:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 18:5e::0f:3b:92:0f brd ff:ff:ff:ff:ff:ff
Notice that your wlan is NOT active. No network.
Here is the readout of ip link with the ethernet cable connected:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 66:17::58:19:77:FE brd ff:ff:ff:ff:ff:ff 4: eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff
This is the readout of ip link with the ethernet cable disconnected and using the wireless:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff
No network. So, at this point, either use the cable, or find out why wlan doesn't go up. wlan is not my point of expertise, though. I would look at the logs. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 27/05/2019 18.36, Mark Misulich wrote:
On Mon, 2019-05-27 at 14:45 +0200, Carlos E. R. wrote:
On 27/05/2019 13.52, Mark Misulich wrote:
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote: > On 26/05/2019 19.05, Mark Misulich wrote:
At this point, did you try the network verification steps I said? pings? Notice that your IP here is 192.168.1.7, so your router will be probably 192.168.1.1. or perhaps 192.168.1.254. Yes, I did try them. I reported that in another post this morning. No matter, here are the present results. When I ping 192.168.1 it works. When I ping using wlan 192.168.1.254 it works on the first ping, then switches to 192.168.1.6 and continues to reply to the ping. When I
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote: ping with the cable connected 192.168.1.254, it responds on the first ping to 192.168.1.254 and then switches to 192.168.1.7 and continues to respond to the ping. I also can ping 8.8.8.8 successfully on either wlan or cable. I get the same results whether I am connected to cable or wlan, with the one exception that I noted of the change from 192.168.1.254 to 192.168.1.6 or 7.
Here is the ip addr readout with the ethernet cable disconnected, using the wireless:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 18:5e::0f:3b:92:0f brd ff:ff:ff:ff:ff:ff
Notice that your wlan is NOT active. No network.
I think the problem was that it wasn't transmitting the login passphrase in the readouts I posted. It is doing so now, and the wlan state is showing up in ip addr readouts. The NetworkManager icon was not showing connected before, now it is showing connected to the router but the icon has a red exclamation mark next to it. When I've seen this in the past, I think it means that I am connected to the router but not the internet.
Here is the readout of ip link with the ethernet cable connected:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 66:17::58:19:77:FE brd ff:ff:ff:ff:ff:ff 4: eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff
This is the readout of ip link with the ethernet cable disconnected and using the wireless:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff
No network.
So, at this point, either use the cable, or find out why wlan doesn't go up. wlan is not my point of expertise, though. I would look at the logs.
I mentioned in an earlier post that I can't connect to the internet with either the cable or the wlan, so I can't use the cable to get on the internet. Whatever is causing the problem effects both wlan and cable equally. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
On Mon, 2019-05-27 at 14:45 +0200, Carlos E. R. wrote:
On 27/05/2019 13.52, Mark Misulich wrote:
On Mon, 2019-05-27 at 11:07 +0200, Carlos E. R. wrote:
On 27/05/2019 03.44, Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote: > On 26/05/2019 19.05, Mark Misulich wrote:
At this point, did you try the network verification steps I said? pings? Notice that your IP here is 192.168.1.7, so your router will be probably 192.168.1.1. or perhaps 192.168.1.254. After sending my last post, I realized I forgot to include the results of one ping. So here are the results of the pings with the www.google. com ping included.
When I ping 192.168.1 it works. When I ping using wlan 192.168.1.254 it works on the first ping, then switches to 192.168.1.6 and continues to reply to the ping. When I ping with the cable connected 192.168.1.254, it responds on the first ping to 192.168.1.254 and then switches to 192.168.1.7 and continues to respond to the ping. I also can ping 8.8.8.8 successfully on either wlan or cable. I get the same results whether I am connected to cable or wlan, with the one exception that I noted of the change from 192.168.1.254 to 192.168.1.6 or 7. When I ping www.google.com it says Name or service not known Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
At this point, did you try the network verification steps I said? pings? Notice that your IP here is 192.168.1.7, so your router will be probably 192.168.1.1. or perhaps 192.168.1.254. After sending my last post, I realized I forgot to include the results of one ping. So here are the results of the pings with the www.google. com ping included.
When I ping 192.168.1 it works. When I ping using wlan 192.168.1.254 it works on the first ping, then switches to 192.168.1.6 and continues to reply to the ping.
I'd prefer to see the command outputs than your interpretation, then make my own interpretation - please, no offence intended, but if I see the commands and the output then we are at least four eyes observing, not two ;-) and chances improve.
When I ping with the cable connected 192.168.1.254, it responds on the first ping to 192.168.1.254 and then switches to 192.168.1.7 and continues to respond to the ping.
This I have difficulty understanding. Perhaps "ip addr ; ip route" would help, then the actual ping outputs.
I also can ping 8.8.8.8 successfully on either wlan or cable.
Good!
I get the same results whether I am connected to cable or wlan, with the one exception that I noted of the change from 192.168.1.254 to 192.168.1.6 or 7.
When I ping www.google.com it says Name or service not known
This would point to the name resolution not working. What is the result of this: egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf ? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
I'd prefer to see the command outputs than your interpretation, then make my own interpretation - please, no offence intended, but if I see the commands and the output then we are at least four eyes observing, not two ;-) and chances improve. No problem at all with that. I had been typing the readouts on my laptop onto the email that I sent from my desktop computer, and I was just trying to save some time. I'm copying everything into a document and transferring it via a usb stick from laptop to desktop now. Thanks for addressing the issue directly so I can present it in a format easier for you to understand.
Perhaps "ip addr ; ip route" would help, then the actual ping outputs.
From 192.168.1.6 icmp_seq=1 Destination Host Unreachable From 192.168.1.6 icmp_seq=2 Destination Host Unreachable From 192.168.1.6 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.254 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5097ms
From 192.168.1.7 icmp_seq=1 Destination Host Unreachable From 192.168.1.7 icmp_seq=2 Destination Host Unreachable From 192.168.1.7 icmp_seq=3 Destination Host Unreachable From 192.168.1.7 icmp_seq=4 Destination Host Unreachable From 192.168.1.7 icmp_seq=5 Destination Host Unreachable From 192.168.1.7 icmp_seq=6 Destination Host Unreachable From 192.168.1.7 icmp_seq=7 Destination Host Unreachable From 192.168.1.7 icmp_seq=8 Destination Host Unreachable From 192.168.1.7 icmp_seq=9 Destination Host Unreachable ^C --- 192.168.1.254 ping statistics --- 12 packets transmitted, 0 received, +9 errors, 100% packet loss, time 11227ms
Using wlan ~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute dynamic wlan3 valid_lft 86364sec preferred_lft 86364sec inet6 fe80::2050:3958:8df1:28b/64 scope link noprefixroute valid_lft forever preferred_lft forever ~> ip route default via 192.168.1.1 dev wlan3 proto dhcp metric 20600 192.168.1.0/24 dev wlan3 proto kernel scope link src 192.168.1.6 metric 600 ~> ping 192.168.1.6 PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data. 64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.030 ms 64 bytes from 192.168.1.6: icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=3 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=4 ttl=64 time=0.026 ms 64 bytes from 192.168.1.6: icmp_seq=5 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=6 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=7 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=8 ttl=64 time=0.024 ms 64 bytes from 192.168.1.6: icmp_seq=9 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=10 ttl=64 time=0.042 ms ...thence continuing on to seq=61 before I quit the ping... 64 bytes from 192.168.1.6: icmp_seq=60 ttl=64 time=0.042 ms 64 bytes from 192.168.1.6: icmp_seq=61 ttl=64 time=0.043 ms ^C --- 192.168.1.6 ping statistics --- 61 packets transmitted, 61 received, 0% packet loss, time 61417ms rtt min/avg/max/mdev = 0.024/0.035/0.056/0.008 ms ~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.26 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.03 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.34 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.96 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.94 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2.28 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.08 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.96 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.00 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.92 ms ...thence continuing on to seq=424 before I quit the ping 424 packets transmitted, 424 received, 0% packet loss, time 423617ms rtt min/avg/max/mdev = 1.510/2.013/9.831/0.737 ms ~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. pipe 4 ~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=122 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=26.2 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=26.8 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=34.0 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=25.5 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=27.1 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=25.7 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=25.7 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=26.4 ms ...thence continuing on to seq=101... 64 bytes from 8.8.8.8: icmp_seq=100 ttl=52 time=26.0 ms c64 bytes from 8.8.8.8: icmp_seq=101 ttl=52 time=25.9 ms ^C --- 8.8.8.8 ping statistics --- 101 packets transmitted, 101 received, 0% packet loss, time 100147ms rtt min/avg/max/mdev = 25.140/29.068/122.254/9.909 ms ~> ping www.google.com ping: www.google.com: Name or service not known Using Cable Connection ~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute dynamic wlan3 valid_lft 84226sec preferred_lft 84226sec inet6 fe80::2050:3958:8df1:28b/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff inet 192.168.1.7/24 brd 192.168.1.255 scope global noprefixroute dynamic eth0 valid_lft 86381sec preferred_lft 86381sec inet6 fe80::f07f:48de:cb67:3437/64 scope link noprefixroute valid_lft forever preferred_lft forever ~> ip route default via 192.168.1.1 dev eth0 proto dhcp metric 20100 default via 192.168.1.1 dev wlan3 proto dhcp metric 20600 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.7 metric 100 192.168.1.0/24 dev wlan3 proto kernel scope link src 192.168.1.6 metric 600 ~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.470 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.355 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.401 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.416 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.388 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.45 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=7.94 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.348 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.361 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.45 ms ...thence to seq=53 before I quit the ping... 64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=1.93 ms 64 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=7.96 ms 64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=0.378 ms 64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=0.383 ms ^C --- 192.168.1.1 ping statistics --- 53 packets transmitted, 53 received, 0% packet loss, time 52477ms rtt min/avg/max/mdev = 0.323/2.385/8.003/3.057 ms ~> ping 192.168.1.6 PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data. 64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.1.6: icmp_seq=2 ttl=64 time=0.027 ms 64 bytes from 192.168.1.6: icmp_seq=3 ttl=64 time=0.027 ms 64 bytes from 192.168.1.6: icmp_seq=4 ttl=64 time=0.027 ms 64 bytes from 192.168.1.6: icmp_seq=5 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=6 ttl=64 time=0.027 ms 64 bytes from 192.168.1.6: icmp_seq=7 ttl=64 time=0.026 ms 64 bytes from 192.168.1.6: icmp_seq=8 ttl=64 time=0.024 ms 64 bytes from 192.168.1.6: icmp_seq=9 ttl=64 time=0.027 ms 64 bytes from 192.168.1.6: icmp_seq=10 ttl=64 time=0.026 ms 64 bytes from 192.168.1.6: icmp_seq=11 ttl=64 time=0.026 ms ^C --- 192.168.1.6 ping statistics --- 11 packets transmitted, 11 received, 0% packet loss, time 10220ms rtt min/avg/max/mdev = 0.024/0.026/0.033/0.006 ms ~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. pipe 4 ~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=25.6 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=24.4 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=26.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=24.6 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=32.8 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=24.9 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=29.4 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=24.6 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=24.7 ms ...thence to seq=103 when I quit the ping... 64 bytes from 8.8.8.8: icmp_seq=100 ttl=52 time=24.3 ms 64 bytes from 8.8.8.8: icmp_seq=101 ttl=52 time=30.0 ms c64 bytes from 8.8.8.8: icmp_seq=102 ttl=52 time=23.8 ms c64 bytes from 8.8.8.8: icmp_seq=103 ttl=52 time=24.2 ms ^C --- 8.8.8.8 ping statistics --- 103 packets transmitted, 103 received, 0% packet loss, time 102149ms rtt min/avg/max/mdev = 23.118/26.129/39.461/3.064 ms ~> ping www.google.com ping: www.google.com: Name or service not known ~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
When I ping www.google.com it says Name or service not known
This would point to the name resolution not working. What is the result of this:
egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
? Mark
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, 28 May 2019 9:31:04 ACST Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote: I'd prefer to see the command outputs than your interpretation, then make my own interpretation - please, no offence intended, but if I see
On 27/05/2019 20.42, Mark Misulich wrote: the commands and the output then we are at least four eyes observing, not two ;-) and chances improve.
No problem at all with that. I had been typing the readouts on my laptop onto the email that I sent from my desktop computer, and I was just trying to save some time. I'm copying everything into a document and transferring it via a usb stick from laptop to desktop now. Thanks for addressing the issue directly so I can present it in a format easier for you to understand.
OK, now we're getting somewhere. :)
Perhaps "ip addr ; ip route" would help, then the actual ping outputs.
Using wlan
~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute dynamic wlan3 valid_lft 86364sec preferred_lft 86364sec inet6 fe80::2050:3958:8df1:28b/64 scope link noprefixroute valid_lft forever preferred_lft forever
Cool - so your machine has an IP address in the correct subnet. :)
~> ip route default via 192.168.1.1 dev wlan3 proto dhcp metric 20600 192.168.1.0/24 dev wlan3 proto kernel scope link src 192.168.1.6 metric 600
And it has a default route - your router's internal IP address. :)
~> ping 192.168.1.6 PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data. 64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.030 ms 64 bytes from 192.168.1.6: icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=3 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=4 ttl=64 time=0.026 ms 64 bytes from 192.168.1.6: icmp_seq=5 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=6 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=7 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=8 ttl=64 time=0.024 ms 64 bytes from 192.168.1.6: icmp_seq=9 ttl=64 time=0.025 ms 64 bytes from 192.168.1.6: icmp_seq=10 ttl=64 time=0.042 ms ...thence continuing on to seq=61 before I quit the ping... 64 bytes from 192.168.1.6: icmp_seq=60 ttl=64 time=0.042 ms 64 bytes from 192.168.1.6: icmp_seq=61 ttl=64 time=0.043 ms ^C --- 192.168.1.6 ping statistics --- 61 packets transmitted, 61 received, 0% packet loss, time 61417ms rtt min/avg/max/mdev = 0.024/0.035/0.056/0.008 ms
You can ping your own machine's IP address, which means the network stack is working OK. Good.
~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.26 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.03 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.34 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.96 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.94 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2.28 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2.08 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.96 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.00 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.92 ms ...thence continuing on to seq=424 before I quit the ping 424 packets transmitted, 424 received, 0% packet loss, time 423617ms rtt min/avg/max/mdev = 1.510/2.013/9.831/0.737 ms
You can ping the router, so Layer 2 connectivity is fine. :)
~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. From 192.168.1.6 icmp_seq=1 Destination Host Unreachable From 192.168.1.6 icmp_seq=2 Destination Host Unreachable From 192.168.1.6 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.254 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5097ms pipe 4
This IP address does not exist on your local LAN, so you're getting an ICMP Unreachable response from your router, which your machine is then reporting from it's own network address. Expected behaviour. Good.
~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=122 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=26.2 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=26.8 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=34.0 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=25.5 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=27.1 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=25.7 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=25.7 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=26.4 ms ...thence continuing on to seq=101... 64 bytes from 8.8.8.8: icmp_seq=100 ttl=52 time=26.0 ms c64 bytes from 8.8.8.8: icmp_seq=101 ttl=52 time=25.9 ms ^C --- 8.8.8.8 ping statistics --- 101 packets transmitted, 101 received, 0% packet loss, time 100147ms rtt min/avg/max/mdev = 25.140/29.068/122.254/9.909 ms
You can ping outside IP addresses, which means Layer 3 connectivity is good and you're able to route packets to/from the internet. Good.
~> ping www.google.com ping: www.google.com: Name or service not known
So you don't have any DNS servers defined, and your machine does not know how to resolve hostnames to IP addresses. That is what we have to solve now. What DNS servers are other hosts on your LAN using? If you're using DHCP, you should be able to get his information automatically from your router (or whatever is acting as the DHCP server), but you may need to tell Network Manager to get the DNS servers for this connection automatically. Alternatively, you can manually configure DNS servers to override the auto config.
[...]
As expected, your wired ethernet results match those of the wireless connection, so I've cut them out for brevity.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
When I ping www.google.com it says Name or service not known
This would point to the name resolution not working. What is the result of this:
egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
?
Mark
So the machine in question is pointing to the router as its DNS server. Assuming that is the same as the other machines on your LAN that is probably correct. Are either nslookup or dig installed? If so, you can manually set the server used for name lookups by those utilities and test name resolution. For example (screen capture from my machine): user@hostname ~ $ nslookup
server 10.128.1.9 Default server: 10.128.1.9 Address: 10.128.1.9#53 www.google.com Server: 10.128.1.9 Address: 10.128.1.9#53
Non-authoritative answer: Name: www.google.com Address: 216.58.199.68 Name: www.google.com Address: 2404:6800:4006:809::2004
(Use Ctrl+C to exit the nslookup interactive prompt). Or with dig, you would do: dig @192.168.1.1 www.google.com It should return the IP address details. Assuming that works, it is then a matter of figuring out why your machine is not parsing /etc/resolv.conf (may be hinted at in another response) or why it is not getting the dns server address from your router and automatically creating the appropriate file/entry if /etc/resolv.conf is no longer used. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
On Tuesday, 28 May 2019 9:31:04 ACST Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
So you don't have any DNS servers defined, and your machine does not know how to resolve hostnames to IP addresses. That is what we have to solve now. What DNS servers are other hosts on your LAN using? If you're using DHCP, you should be able to get his information automatically from your router (or whatever is acting as the DHCP server), but you may need to tell Network Manager to get the DNS servers for this connection automatically. Alternatively, you can manually configure DNS servers to override the auto config. My laptop etc/resolve.conf file reads nameserver 192.168.1.1 It reads
On Tue, 2019-05-28 at 10:17 +0930, Rodney Baker wrote: the same as the resolve.conf file on my desktop, nameserver 192.168.1.1.
[...]
As expected, your wired ethernet results match those of the wireless connection, so I've cut them out for brevity.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
When I ping www.google.com it says Name or service not known
This would point to the name resolution not working. What is the result of this:
egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
?
Mark
So the machine in question is pointing to the router as its DNS server. Assuming that is the same as the other machines on your LAN that is probably correct.
Are either nslookup or dig installed? If so, you can manually set the server used for name lookups by those utilities and test name resolution. For example (screen capture from my machine):
user@hostname ~ $ nslookup
server 10.128.1.9
Default server: 10.128.1.9 Address: 10.128.1.9#53
www.google.com
Server: 10.128.1.9 Address: 10.128.1.9#53
Non-authoritative answer: Name: www.google.com Address: 216.58.199.68 Name: www.google.com Address: 2404:6800:4006:809::2004
(Use Ctrl+C to exit the nslookup interactive prompt).
Or with dig, you would do:
dig @192.168.1.1 www.google.com
It should return the IP address details.
~> dig @192.168.1.1 www.google.com ; <<>> DiG 9.11.2 <<>> @192.168.1.1 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45760 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 258 IN A 172.217.9.68 ;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon May 27 22:50:23 EDT 2019 ;; MSG SIZE rcvd: 59 ~> nslookup
nslookup never did provide any readout, after 15 minutes of waiting.
Assuming that works, it is then a matter of figuring out why your machine is not parsing /etc/resolv.conf (may be hinted at in another response) or why it is not getting the dns server address from your router and automatically creating the appropriate file/entry if /etc/resolv.conf is no longer used.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [05-27-19 23:07]: [...]
~> nslookup
nslookup never did provide any readout, after 15 minutes of waiting.
it will not unless you give it a parameter, nslookup google.com nslookup 216.58.192.174 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, 28 May 2019 12:35:12 ACST Mark Misulich wrote: [...]
My laptop etc/resolve.conf file reads nameserver 192.168.1.1 It reads the same as the resolve.conf file on my desktop, nameserver 192.168.1.1.
[...]
OK, all good so far. [...]
~> dig @192.168.1.1 www.google.com
; <<>> DiG 9.11.2 <<>> @192.168.1.1 www.google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45760 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 258 IN A 172.217.9.68
;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon May 27 22:50:23 EDT 2019 ;; MSG SIZE rcvd: 59
Good, so that proves that name resolution via your router is working when the machine actually tries to use it.
~> nslookup
nslookup never did provide any readout, after 15 minutes of waiting. [...]
That's because when you run nslookup with no parameters it starts an interactive nslookup shell. You then need to tell it which server to use (using 'server xxx.xxx.xxx.xxx' without the quotes), and then type the hostname to lookup Otherwise, if you simply run "nslookup <hostname>" it will use the default nameservers that your system is configured to use. Try it both ways. Nslookup <hostname> should tell you which nameserver it is trying to use to resolve the name. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
On 28/05/2019 02.01, Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
I'd prefer to see the command outputs than your interpretation, then make my own interpretation - please, no offence intended, but if I see the commands and the output then we are at least four eyes observing, not two ;-) and chances improve. No problem at all with that. I had been typing the readouts on my laptop onto the email that I sent from my desktop computer, and I was just trying to save some time. I'm copying everything into a document and transferring it via a usb stick from laptop to desktop now. Thanks for addressing the issue directly so I can present it in a format easier for you to understand.
Ah, of course, I forgot you can not email from the problem computer, sorry.
Perhaps "ip addr ; ip route" would help, then the actual ping outputs.
Using wlan
~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute dynamic wlan3 valid_lft 86364sec preferred_lft 86364sec inet6 fe80::2050:3958:8df1:28b/64 scope link noprefixroute valid_lft forever preferred_lft forever
~> ip route default via 192.168.1.1 dev wlan3 proto dhcp metric 20600 192.168.1.0/24 dev wlan3 proto kernel scope link src 192.168.1.6 metric 600
Correct.
~> ping 192.168.1.6 PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data. 64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.030 ms
But this is pinging yourself, at the wlan address.
~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.26 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.03 ms
so ping the router works fine.
~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. From 192.168.1.6 icmp_seq=1 Destination Host Unreachable From 192.168.1.6 icmp_seq=2 Destination Host Unreachable From 192.168.1.6 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.254 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5097ms pipe 4
This one I don't understand. Why do you... :-? Ah, because I said the router would be 192.168.1.1 or 192.168.1.254. Ah, ok.
~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=122 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=26.2 ms
Ok, connectivity to internet ok.
~> ping www.google.com ping: www.google.com: Name or service not known
Ok, here is the problem.
Using Cable Connection
~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 18:5e:0f:3b:92:0f brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute dynamic wlan3 valid_lft 84226sec preferred_lft 84226sec inet6 fe80::2050:3958:8df1:28b/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:00:00:2e:ee brd ff:ff:ff:ff:ff:ff inet 192.168.1.7/24 brd 192.168.1.255 scope global noprefixroute dynamic eth0 valid_lft 86381sec preferred_lft 86381sec inet6 fe80::f07f:48de:cb67:3437/64 scope link noprefixroute valid_lft forever preferred_lft forever
Ok... Notice that both wlan and eth are up, just that eth has a lower metric thus precedence.
~> ip route default via 192.168.1.1 dev eth0 proto dhcp metric 20100 default via 192.168.1.1 dev wlan3 proto dhcp metric 20600 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.7 metric 100 192.168.1.0/24 dev wlan3 proto kernel scope link src 192.168.1.6 metric 600
~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.470 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.355 ms
Good.
~> ping 192.168.1.6 PING 192.168.1.6 (192.168.1.6) 56(84) bytes of data. 64 bytes from 192.168.1.6: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.1.6: icmp_seq=2 ttl=64 time=0.027 ms
This ping yourself. I don't know why you do it. :-?
~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. From 192.168.1.7 icmp_seq=1 Destination Host Unreachable From 192.168.1.7 icmp_seq=2 Destination Host Unreachable From 192.168.1.7 icmp_seq=3 Destination Host Unreachable From 192.168.1.7 icmp_seq=4 Destination Host Unreachable
And this one... Ok, I don't understand all, but it is normal. Look, in my computer: cer@Telcontar:~> ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. From 192.168.1.14 icmp_seq=1 Destination Host Unreachable From 192.168.1.14 icmp_seq=2 Destination Host Unreachable From 192.168.1.14 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.254 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4097ms pipe 4 cer@Telcontar:~> it is ping an address that does not exist, so the local machine reports that it can not reach it. All normal.
~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=25.6 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=24.4 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=26.9 ms
Ok
~> ping www.google.com ping: www.google.com: Name or service not known
Problem.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
Ah. The problem seems to be that you told your machine that the router does name solving, but it doesn't. You could do host -v www.google.com 192.168.1.1 host -v www.google.com 8.8.8.8 The first one should fail, the second one succeed. Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses. If it is Windows, you can find out the same information , but differently, in network properties. If it is Android, somewhere else. Setup, system, about... I see the IP in mine, but not the DNS. Ah, yes, Newtwork, WiFi setup, press on the cogwheel, advanced. You will see IP, Gateway, and DNS. What DNS is it using - when connected to your WiFI? It is possible that you can ssh from local machine to local machine, not have to copy things via USB :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
On 28/05/2019 02.01, Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
~> ping www.google.com ping: www.google.com: Name or service not known
Problem.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
Ah.
The problem seems to be that you told your machine that the router does name solving, but it doesn't.
You could do
host -v www.google.com 192.168.1.1 host -v www.google.com 8.8.8.8
The first one should fail, the second one succeed. ~> host -v www.google.com 192.168.1.1 Trying "www.google.com" Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15664 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 171 IN A 172.217.8.196 Received 48 bytes from 192.168.1.1#53 in 41 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46875 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN AAAA ;; ANSWER SECTION: www.google.com. 171 IN AAAA 2607:f8b0:4009:805::2004 Received 60 bytes from 192.168.1.1#53 in 28 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45637 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN MX ;; AUTHORITY SECTION: google.com. 36 IN SOA ns1.google.com. dns- admin.google.com. 250191621 900 900 1800 60 Received 82 bytes from 192.168.1.1#53 in 198 ms lxmark@linux-5w6a:~> host -v www.google.com 8.8.8.8 Trying "www.google.com" Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36721 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 288 IN A 216.58.192.132 Received 48 bytes from 8.8.8.8#53 in 27 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30315 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN AAAA ;; ANSWER SECTION: www.google.com. 242 IN AAAA 2607:f8b0:4009:80f::2004 Received 60 bytes from 8.8.8.8#53 in 25 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39402 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN MX ;; AUTHORITY SECTION: google.com. 59 IN SOA ns1.google.com. dns- admin.google.com. 250191621 900 900 1800 60 Received 82 bytes from 8.8.8.8#53 in 45 ms
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1 On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, 28 May 2019 12:47:05 ACST Mark Misulich wrote: [...]
Received 82 bytes from 8.8.8.8#53 in 45 ms
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
Name resolution via your router is obviously working, just not by default from your laptop. Assuming you are using Network Manager for managing the connection, can you check the connection properties and ensure that it is set to "Automatic" (not "Automatic, addresses only")? Try commenting out the entry in /etc/resolv.conf, or even renaming the file to /etc/resolv.conf.bak, then reboot the machine. Try the hostname lookup again after the network connection is back up, without specifying the nameserver (it should use the default). Then try ping or web browsing again. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
On Tue, 2019-05-28 at 13:33 +0930, Rodney Baker wrote:
On Tuesday, 28 May 2019 12:47:05 ACST Mark Misulich wrote: [...]
Received 82 bytes from 8.8.8.8#53 in 45 ms
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
Name resolution via your router is obviously working, just not by default from your laptop. Assuming you are using Network Manager for managing the connection, can you check the connection properties and ensure that it is set to "Automatic" (not "Automatic, addresses only")?
The connections are set to Automatic (not Automatic, addresses only)
Try commenting out the entry in /etc/resolv.conf, or even renaming the file to /etc/resolv.conf.bak, then reboot the machine. Try the hostname lookup again after the network connection is back up, without specifying the nameserver (it should use the default). Then try ping or web browsing again.
After commenting out the nameserver address in /etc/resolv.conf, then rebooting. The same nameserver address appeared in /etc/resolv.conf. ~> dig @192.168.1.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.2 <<>> @192.168.1.1 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20155 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 27 ;; WARNING: Message has 2 extra bytes at end ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 451278 IN NS h.root-servers.net. . 451278 IN NS m.root-servers.net. . 451278 IN NS l.root-servers.net. . 451278 IN NS a.root-servers.net. . 451278 IN NS d.root-servers.net. . 451278 IN NS k.root-servers.net. . 451278 IN NS f.root-servers.net. . 451278 IN NS c.root-servers.net. . 451278 IN NS e.root-servers.net. . 451278 IN NS i.root-servers.net. . 451278 IN NS g.root-servers.net. . 451278 IN NS b.root-servers.net. . 451278 IN NS j.root-servers.net. ;; ADDITIONAL SECTION: m.root-servers.net. 40904 IN A 202.12.27.33 m.root-servers.net. 40971 IN AAAA 2001:dc3::35 l.root-servers.net. 46468 IN A 199.7.83.42 l.root-servers.net. 155801 IN AAAA 2001:500:9f::42 a.root-servers.net. 40874 IN A 198.41.0.4 a.root-servers.net. 41246 IN AAAA 2001:503:ba3e::2:30 d.root-servers.net. 134556 IN A 199.7.91.13 d.root-servers.net. 520945 IN AAAA 2001:500:2d::d k.root-servers.net. 47423 IN A 193.0.14.129 k.root-servers.net. 501852 IN AAAA 2001:7fd::1 f.root-servers.net. 145967 IN A 192.5.5.241 f.root-servers.net. 583096 IN AAAA 2001:500:2f::f c.root-servers.net. 104173 IN A 192.33.4.12 ;; Query time: 29 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Wed May 29 09:19:20 EDT 2019 ;; MSG SIZE rcvd: 512 ~> nslookup 192.168.1.1 1.1.168.192.in-addr.arpa name = www.routerlogin.com. Authoritative answers can be found from: ~> nslookup 8.8.8.8 8.8.8.8.in-addr.arpa name = google-public-dns-a.google.com. Authoritative answers can be found from: ~> nslookup www.google.com Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: Name: www.google.com Address: 172.217.4.100 Name: www.google.com Address: 2607:f8b0:4009:80d::2004 Browser still can't reach the internet. ~> ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.77 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.73 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.94 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.68 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.92 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.78 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.76 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.78 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.66 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.70 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.75 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.61 ms ^C --- 192.168.1.1 ping statistics --- 12 packets transmitted, 12 received, 0% packet loss, time 11019ms rtt min/avg/max/mdev = 1.612/1.761/1.941/0.097 ms ~> ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=25.5 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=26.2 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=25.3 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=25.4 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=32.2 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=26.5 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=25.1 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=26.0 ms 64 bytes from 8.8.8.8: icmp_seq=11 ttl=52 time=31.6 ms ^C --- 8.8.8.8 ping statistics --- 11 packets transmitted, 11 received, 0% packet loss, time 10013ms rtt min/avg/max/mdev = 25.130/26.944/32.267/2.405 ms ~> ping www.google.com ping: www.google.com: Name or service not known -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/05/2019 05.17, Mark Misulich wrote:
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
On 28/05/2019 02.01, Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote:
On 27/05/2019 18.36, Mark Misulich wrote:
~> ping www.google.com ping: www.google.com: Name or service not known
Problem.
~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf nameserver 192.168.1.1
Ah.
The problem seems to be that you told your machine that the router does name solving, but it doesn't.
You could do
host -v www.google.com 192.168.1.1 host -v www.google.com 8.8.8.8
The first one should fail, the second one succeed. ~> host -v www.google.com 192.168.1.1 Trying "www.google.com" Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15664 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;www.google.com. IN A
;; ANSWER SECTION: www.google.com. 171 IN A 172.217.8.196
Received 48 bytes from 192.168.1.1#53 in 41 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46875 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;www.google.com. IN AAAA
;; ANSWER SECTION: www.google.com. 171 IN AAAA 2607:f8b0:4009:805::2004
Received 60 bytes from 192.168.1.1#53 in 28 ms Trying "www.google.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45637 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION: ;www.google.com. IN MX
;; AUTHORITY SECTION: google.com. 36 IN SOA ns1.google.com. dns- admin.google.com. 250191621 900 900 1800 60
Received 82 bytes from 192.168.1.1#53 in 198 ms
Well, now this is very peculiar, your router *does* DNS queries ...
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses. My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
And it works for your laptop, but not for this machine. Weird. At this point, I can not imagine why. Let's see if someone has another idea. Ok, one: Have a look at "/etc/hosts.conf", it should have: order hosts, bind multi on Or it might not exist. Then look at "/etc/nsswitch.conf". It should have: hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns (and more) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Tue, 2019-05-28 at 12:01 +0200, Carlos E. R. wrote:
On 28/05/2019 05.17, Mark Misulich wrote:
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
On 28/05/2019 02.01, Mark Misulich wrote:
On Mon, 2019-05-27 at 23:52 +0200, Carlos E. R. wrote:
On 27/05/2019 20.42, Mark Misulich wrote:
On Mon, 2019-05-27 at 19:52 +0200, Carlos E. R. wrote: > On 27/05/2019 18.36, Mark Misulich wrote:
Well, now this is very peculiar, your router *does* DNS queries
...
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
And it works for your laptop, but not for this machine. Weird.
At this point, I can not imagine why.
Let's see if someone has another idea. Ok, one:
Have a look at "/etc/hosts.conf", it should have:
order hosts, bind multi on
My file /etc/host.conf has order hosts, bind multi on
Or it might not exist. Then look at "/etc/nsswitch.conf". It should have:
hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns
(and more)
my /etc/nsswitch.conf has hosts: files mdns_minimal [NOTFOUND=return] dns networks: files dns ...(and more) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/05/2019 15.02, Mark Misulich wrote:
On Tue, 2019-05-28 at 12:01 +0200, Carlos E. R. wrote:
On 28/05/2019 05.17, Mark Misulich wrote:
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
Well, now this is very peculiar, your router *does* DNS queries
...
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
And it works for your laptop, but not for this machine. Weird.
At this point, I can not imagine why.
Let's see if someone has another idea. Ok, one:
Have a look at "/etc/hosts.conf", it should have:
order hosts, bind multi on
My file /etc/host.conf has
order hosts, bind multi on
So it is correct.
Or it might not exist. Then look at "/etc/nsswitch.conf". It should have:
hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns
(and more)
my /etc/nsswitch.conf has
hosts: files mdns_minimal [NOTFOUND=return] dns networks: files dns
Same as me, in two installs. Must be correct.
...(and more)
Then I don't have more ideas. Try rebooting the router. The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing. Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wed, 2019-05-29 at 17:45 +0200, Carlos E. R. wrote:
On 29/05/2019 15.02, Mark Misulich wrote:
On Tue, 2019-05-28 at 12:01 +0200, Carlos E. R. wrote:
On 28/05/2019 05.17, Mark Misulich wrote:
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
Well, now this is very peculiar, your router *does* DNS queries
...
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
And it works for your laptop, but not for this machine. Weird.
At this point, I can not imagine why.
Let's see if someone has another idea. Ok, one:
Have a look at "/etc/hosts.conf", it should have:
order hosts, bind multi on
My file /etc/host.conf has
order hosts, bind multi on
So it is correct.
Or it might not exist. Then look at "/etc/nsswitch.conf". It should have:
hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns
(and more)
my /etc/nsswitch.conf has
hosts: files mdns_minimal [NOTFOUND=return] dns networks: files dns
Same as me, in two installs. Must be correct.
...(and more)
Then I don't have more ideas. Try rebooting the router.
The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing.
Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine.
I've been thinking more of a overall view, that the issue is that the zypper dup didn't work. Something in the software is messed up, and we are at an impasse trying to fix it. I think that at this point the thing to do is start over. What I mean is to format the / and /home partitions and install from the iso to see if everything works afterwards. I downloaded the iso, and this morning have copied my data on /home so I can reload it afterwards. If I have the same problem after reinstalling the operating system, I won't be any worse off than I am now. But it will probably fix the problem, and I won't know till I try. I'll report back after I get it all done later today. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Mark Misulich <munguanaweza@gmail.com> [05-29-19 12:26]:
On Wed, 2019-05-29 at 17:45 +0200, Carlos E. R. wrote:
On 29/05/2019 15.02, Mark Misulich wrote:
On Tue, 2019-05-28 at 12:01 +0200, Carlos E. R. wrote:
On 28/05/2019 05.17, Mark Misulich wrote:
On Tue, 2019-05-28 at 03:03 +0200, Carlos E. R. wrote:
Well, now this is very peculiar, your router *does* DNS queries
...
Ok, next step. You said you have more computers. On one that it is working, if it is Linux, see what says /etc/resolv.conf, and perhaps copy it over... The actual name server it uses.
My desktop computer is opensuse. The /etc/resolv.conf file says nameserver 192.168.1.1
On my laptop, the /etc/resolv.conf file says nameserver 192.168.1.1
And it works for your laptop, but not for this machine. Weird.
At this point, I can not imagine why.
Let's see if someone has another idea. Ok, one:
Have a look at "/etc/hosts.conf", it should have:
order hosts, bind multi on
My file /etc/host.conf has
order hosts, bind multi on
So it is correct.
Or it might not exist. Then look at "/etc/nsswitch.conf". It should have:
hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files dns
(and more)
my /etc/nsswitch.conf has
hosts: files mdns_minimal [NOTFOUND=return] dns networks: files dns
Same as me, in two installs. Must be correct.
...(and more)
Then I don't have more ideas. Try rebooting the router.
The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing.
Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine.
I've been thinking more of a overall view, that the issue is that the zypper dup didn't work. Something in the software is messed up, and we are at an impasse trying to fix it. I think that at this point the thing to do is start over.
What I mean is to format the / and /home partitions and install from the iso to see if everything works afterwards. I downloaded the iso, and this morning have copied my data on /home so I can reload it afterwards.
If I have the same problem after reinstalling the operating system, I won't be any worse off than I am now. But it will probably fix the problem, and I won't know till I try. I'll report back after I get it all done later today.
a lot to do if not really necessary. zypper verify will tell you if zypper hickuppeddedd -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/05/2019 18.23, Mark Misulich wrote:
On Wed, 2019-05-29 at 17:45 +0200, Carlos E. R. wrote:
Then I don't have more ideas. Try rebooting the router.
Did you try that?
The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing.
Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine.
I've been thinking more of a overall view, that the issue is that the zypper dup didn't work. Something in the software is messed up, and we are at an impasse trying to fix it. I think that at this point the thing to do is start over.
I doubt it, but we would not find out what is going on.
What I mean is to format the / and /home partitions and install from the iso to see if everything works afterwards. I downloaded the iso, and this morning have copied my data on /home so I can reload it afterwards.
I don't see why format /home.
If I have the same problem after reinstalling the operating system, I won't be any worse off than I am now. But it will probably fix the problem, and I won't know till I try. I'll report back after I get it all done later today.
If you suspect that zypper dup went bad, there are tools to verify that. Did you use "no-recommends"? Then don't. It has to be undone. Try this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE\ Leap\ 15\.1|openSUSE_Leap_15\.1" | less -S It will list all packages that *might* not belong to 15.1. You will then have to consider the action: perhaps missing repo, remove, change repo... Also, run this: rpmconfigcheck The output will be like this, but much longer: Telcontar:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/usr.lib.dovecot.auth.rpmnew /etc/apparmor.d/usr.lib.dovecot.config.rpmnew /etc/apparmor.d/usr.lib.dovecot.dovecot-lda.rpmnew /etc/apparmor.d/usr.sbin.smbd.rpmnew /etc/my.cnf.rpmnew /etc/pam.d/login.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/rsyslog.conf.rpmnew /etc/ssh/ssh_config.rpmnew /etc/ssh/sshd_config.rpmnew Telcontar:~ # You will have to review them. For example, as root, I would do: meld /etc/postfix/main.cf.rpmnew /etc/postfix/main.cf & and then decide what to do. .rpmnew is a new version of the file propossed by the rpm update process, while .rpmsave is the old version (the new was applied). Also, do "aa-logprof" and act on the results. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wed, 2019-05-29 at 22:03 +0200, Carlos E. R. wrote:
On 29/05/2019 18.23, Mark Misulich wrote:
On Wed, 2019-05-29 at 17:45 +0200, Carlos E. R. wrote:
Then I don't have more ideas. Try rebooting the router.
Did you try that? Yes
The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing.
Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine.
I've been thinking more of a overall view, that the issue is that the zypper dup didn't work. Something in the software is messed up, and we are at an impasse trying to fix it. I think that at this point the thing to do is start over.
I doubt it, but we would not find out what is going on.
What I mean is to format the / and /home partitions and install from the iso to see if everything works afterwards. I downloaded the iso, and this morning have copied my data on /home so I can reload it afterwards.
I don't see why format /home.
If I have the same problem after reinstalling the operating system, I won't be any worse off than I am now. But it will probably fix the problem, and I won't know till I try. I'll report back after I get it all done later today.
If you suspect that zypper dup went bad, there are tools to verify that.
Did you use "no-recommends"? Then don't. It has to be undone.
Try this:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE\ Leap\ 15\.1|openSUSE_Leap_15\.1" | less -S
It will list all packages that *might* not belong to 15.1. You will then have to consider the action: perhaps missing repo, remove, change repo...
Also, run this:
rpmconfigcheck
The output will be like this, but much longer:
Telcontar:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/usr.lib.dovecot.auth.rpmnew /etc/apparmor.d/usr.lib.dovecot.config.rpmnew /etc/apparmor.d/usr.lib.dovecot.dovecot-lda.rpmnew /etc/apparmor.d/usr.sbin.smbd.rpmnew /etc/my.cnf.rpmnew /etc/pam.d/login.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/rsyslog.conf.rpmnew /etc/ssh/ssh_config.rpmnew /etc/ssh/sshd_config.rpmnew Telcontar:~ #
You will have to review them. For example, as root, I would do:
meld /etc/postfix/main.cf.rpmnew /etc/postfix/main.cf &
and then decide what to do.
.rpmnew is a new version of the file propossed by the rpm update process, while .rpmsave is the old version (the new was applied).
Also, do "aa-logprof" and act on the results.
Hi, thanks for the ideas about how to continue trying to fix the problem. If I had received them sooner, I would have tried them. It seemed that everyone was out of ideas about fixing the problem, so I thought the way forward was to reinstall. I received your new ideas in this post after I did the reinstall. Everything is working now, problem fixed. Whatever was causing it. Many thanks for your efforts on my behalf to try and fix this. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/05/2019 23.12, Mark Misulich wrote:
On Wed, 2019-05-29 at 22:03 +0200, Carlos E. R. wrote:
...
Hi, thanks for the ideas about how to continue trying to fix the problem. If I had received them sooner, I would have tried them.
It seemed that everyone was out of ideas about fixing the problem, so I thought the way forward was to reinstall. I received your new ideas in this post after I did the reinstall. Everything is working now, problem fixed. Whatever was causing it.
Many thanks for your efforts on my behalf to try and fix this.
Ok! :-) We failed to find the cause, though. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wed, 2019-05-29 at 23:14 +0200, Carlos E. R. wrote:
On 29/05/2019 23.12, Mark Misulich wrote:
On Wed, 2019-05-29 at 22:03 +0200, Carlos E. R. wrote:
...
Hi, thanks for the ideas about how to continue trying to fix the problem. If I had received them sooner, I would have tried them.
It seemed that everyone was out of ideas about fixing the problem, so I thought the way forward was to reinstall. I received your new ideas in this post after I did the reinstall. Everything is working now, problem fixed. Whatever was causing it.
Many thanks for your efforts on my behalf to try and fix this.
Ok! :-)
We failed to find the cause, though.
Yes, that's true unfortunately.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 29 May 2019 17:45:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Then I don't have more ideas. Try rebooting the router.
The only remaining thing I can think off is to use ethereal aka wireshark to watch the connections while you do a simple "host google.com" query. Find out if the computer is asking or if the router does not reply or what. While you do this, better don't have anything else using the network or it can become very confusing.
Well, there is another thing you could do: use your own DNS server in your machine. DNSmasq would do fine.
Possibly going off at a tangent here, but I thought that something like traceroute for DNS might help diagnose the problem, but I didn't know what that program is, so I googled and was pointed towards dig with the +trace option. But I get strange results on my system :( I'm running 15.0 with wicked networking, not NM. My home router is 192.168.1.254. Here's what I see: $ dig www.example.com ; <<>> DiG 9.11.2 <<>> www.example.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38144 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.example.com. IN A ;; ANSWER SECTION: www.example.com. 35847 IN A 93.184.216.34 ;; Query time: 32 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Wed May 29 20:01:26 BST 2019 ;; MSG SIZE rcvd: 60 $ dig +trace www.example.com ; <<>> DiG 9.11.2 <<>> +trace www.example.com ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @192.168.1.254 +trace www.example.com ; <<>> DiG 9.11.2 <<>> @192.168.1.254 +trace www.example.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @8.8.8.8 +trace www.example.com ; <<>> DiG 9.11.2 <<>> @8.8.8.8 +trace www.example.com ; (1 server found) ;; global options: +cmd . 190363 IN NS a.root-servers.net. ...[snip] . 190363 IN RRSIG NS 8 0 518400 20190610230000 20190528220000 25266 . 0Ehr9VW4uYrL9QRjSz5dnceVy5O/b6TzPzCzCPqnFaeXby0RrklO9FGk dTsMdCjC4RsK2rq2FN6cgpze6iAiRDZOxtZTPcvNh5WLZN6z7bEwdi1z Ka8D9bNxNjWl4c1FDgaykjcbN0ehN09+I0yeRkBKJPEZCSbFaGZK7tyJ jYOqEjJ4MnlPmtI3YBmyIaDKxNHnsX4eWnmam9wvOjvWid6Y3So4HqjG rVHKjHt14IFqnTKdoHH4VAHzvFw59tumAefFS01QZwHBZ6YXx8iUHLgZ 2gG0KUXlQkS2Jn6//mmsA5TLu/kuikVWX8q063Gv5dfW0US5UqlGaOI4 HOVYhQ== ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 31 ms com. 172800 IN NS l.gtld-servers.net. ...[snip] com. 172800 IN NS m.gtld-servers.net. com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766 com. 86400 IN RRSIG DS 8 1 86400 20190611170000 20190529160000 25266 . THN276K5UQs00Q9StpDAJ0SHXJ6MQPobdFAHd5hkAjbMbc932wy67YOd GEGRkJ014kIVFTzw40aagFLyJyQsJEUy2E5/d0abalP34GrVpeTOv3UA Er3PxwRRy37DCm/aVoHXw5GTBHDKLhjusMrwijd/CDBbeHKEkeooOg3S Njvy5zZC3qFe80+Erpp9Xl1qEAMeV8dFUUMiT3TKPNXmIDwYwSVGgDNx 17NP20vRnNbNo8uCg5e2acYpcVp751UreAdP0WnOp5C+0wpwrYuF8Po+ 6JG29XiwYls+4AcM3nt1j7DSalaLsQA54yqsfMVt7xx++BmKawVmPbR9 ZKTVoQ== ;; Received 1175 bytes from 192.5.5.241#53(f.root-servers.net) in 40 ms example.com. 172800 IN NS a.iana-servers.net. example.com. 172800 IN NS b.iana-servers.net. ...[snip] example.com. 86400 IN RRSIG DS 8 2 86400 20190603042304 20190527031304 3800 com. injZLSZmfENHXUmm0+Up7Z5PhkyB+dH01YE9QEdKilQwPSgjys/Yvb0r c94xcrLNXZzqThoGS9iNY28hMEmrv78kp1TmBw+GIkMLhqB2DOxBNwA1 y0m3WvK+E8aM3UyyNbM8mvpXYeCwGbVphDUB10nUwl8pGOyncs8CTrTR 3V0= ;; Received 507 bytes from 192.31.80.30#53(d.gtld-servers.net) in 32 ms www.example.com. 86400 IN A 93.184.216.34 www.example.com. 86400 IN RRSIG A 8 3 86400 20190607214328 20190517095823 23689 example.com. fHpcX91kafIvHGkQXbpGOHBw9BFwCHv926APC3ZphVZRL4XG8tI1vpVj MIEm0eStoQbUTt67ho6S9awi5lHcDs3+h1ShO670mCPms/7bR0rQhFq4 K9V/InWOaQz2w2greAiWgB8+cdcaPGa+3ju9agabx1blkAIaTnWIady9 0AU= ;; Received 231 bytes from 199.43.135.53#53(a.iana-servers.net) in 106 ms $ cat /etc/resolv.conf ### /etc/resolv.conf file autogenerated by netconfig! ...[snip] ### Please remove (at least) this line when you modify the file! search lan nameserver 192.168.1.254 So given that my system seems to work properly in all respects except when I use the +trace option, is anybody able to explain what's going on for a poor simple soul? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, 27 May 2019 11:14:39 ACST Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection.
The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me
#curl api.ipify curl: (6) api.ipify
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi.
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user).
#ip route #
Next is connectivity. Ping your router, then ping google at 8.8.8.8.
#ping 192.147.1.1 connect: Network is unreachable
Next is name solving, so ping google.com.
#ping www.gosgle.com ping: www.gosgle.com Name or service not known
(I did spell google correctly when I tried to ping, just trying to get rid of the hyperlink in this email).
Mark
As others have suggested, when troubleshooting networking, a methodical approach will always win over a scatter-gun approach. 1. Check for Layer 1 (physical layer) issues first: is the ethernet (wired) or wireless link up? If that isn't working, nothing else will. Check for configuration or device driver/kernel module/firmware issues. 2. Layer 2 - on most home networks, should be OK if Layer 1 is OK (unless VLANs are involved, which adds another layer of complexity). However, you'll need to know that ARP resolution is working - does your computer know the MAC address of the default gateway or next-hop router? 3. Layer 3 - check for an IP address in the correct (expected) subnet; if you don't have one, is DHCP working correctly, or are you using a static IP address? Check that the default gateway address is correct (it should be your router's IP address, again either assigned via DHCP or statically). Check that you can ping the default gateway; if not, is ARP resolution working (back to Layer 2). If all the above passes, then (and only then) check for external connectivity. If that still fails, repeat the above tests between the router and the ISP. Same approach, different devices. Always break it down to first principles. If the physical link is down, nothing works. If the physical link is up but Layer 2 (link layer) is not functioning correctly, nothing works above that etc. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
On Mon, 2019-05-27 at 18:59 +0930, Rodney Baker wrote:
On Monday, 27 May 2019 11:14:39 ACST Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
As others have suggested, when troubleshooting networking, a methodical approach will always win over a scatter-gun approach.
1. Check for Layer 1 (physical layer) issues first: is the ethernet (wired) or wireless link up? If that isn't working, nothing else will. The ethernet is working, I am using it to send emails on my desktop computer. The wireless is also working, I can connect to it with my cellphone and an ipad that I use for work.
Check for configuration or device driver/kernel module/firmware issues. The configuration in Yast was working before the zypper dup from 15.0 to 15.1. I have gone through and checked the configurations for ethernet and wireless, and they seem correct.
2. Layer 2 - on most home networks, should be OK if Layer 1 is OK (unless VLANs are involved, which adds another layer of complexity). However, you'll need to know that ARP resolution is working - does your computer know the MAC address of the default gateway or next-hop router?
3. Layer 3 - check for an IP address in the correct (expected) subnet; if you don't have one, is DHCP working correctly, or are you using a static IP address? Check that the default gateway address is correct (it should be your router's IP address, again either assigned via DHCP or statically). Check that you can ping the default gateway; if not, is ARP resolution working (back to Layer 2).
If all the above passes, then (and only then) check for external connectivity.
If that still fails, repeat the above tests between the router and the ISP. Same approach, different devices.
Always break it down to first principles. If the physical link is down, nothing works. If the physical link is up but Layer 2 (link layer) is not functioning correctly, nothing works above that etc.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, 27 May 2019 21:31:30 ACST Mark Misulich wrote:
On Mon, 2019-05-27 at 18:59 +0930, Rodney Baker wrote:
On Monday, 27 May 2019 11:14:39 ACST Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote: As others have suggested, when troubleshooting networking, a methodical approach will always win over a scatter-gun approach.
1. Check for Layer 1 (physical layer) issues first: is the ethernet (wired) or wireless link up? If that isn't working, nothing else will.
The ethernet is working, I am using it to send emails on my desktop computer. The wireless is also working, I can connect to it with my cellphone and an ipad that I use for work.
What is working for other devices is irrelevant until it comes to checking external connectivity (which we can now safely assume is working). So, lets concentrate on the device that is not working. Is the ethernet connection between that device and the network switch/router working? Is that a wired ethernet or wireless ethernet connection? Lets do the most basic check first - if we're dealing with a wired ethernet connection, do the link lights come up on the ethernet ports on the device (if it has any) and the switch/router when the cable is plugged in and the device is powered on? No link lights = no physical connectivity, either due to a) ports being shut down/disabled at either end, either administratively or due to lack of drivers being loaded; or b) faulty cable or cable not correctly plugged in. If WiFi, is the WiFi adapter enabled? Are the correct firmware or kernel modules loaded? Is there a hardware or "soft key" switch that has disabled the WiFi adapter? If it is not already installed, can you install net-tools-deprecated from a CD image and show the output of ifconfig? Alternatively, show us the output of ip addr... Also, what chipset (wireless and/or wired ethernet) does your non-working machine use? Have you checked that the required kernel modules are installed and loaded? Were you using the traditional/legacy ifup/ifdown config scripts or NetworkManager to manage the connection previously? What is the newly upgraded OS trying to use?
Check for configuration or device driver/kernel module/firmware issues.
The configuration in Yast was working before the zypper dup from 15.0 to 15.1. I have gone through and checked the configurations for ethernet and wireless, and they seem correct.
Have the interface names changed? Is the device configured to get an IP address automatically, via DHCP, or does it use a static IP address? Can you boot the system from a Live CD and get the network up?
[...]
I may be delayed with further replies tonight as it is bedtime here. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================
On 27/05/2019 15.33, Rodney Baker wrote:
On Monday, 27 May 2019 21:31:30 ACST Mark Misulich wrote:
On Mon, 2019-05-27 at 18:59 +0930, Rodney Baker wrote:
On Monday, 27 May 2019 11:14:39 ACST Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote: As others have suggested, when troubleshooting networking, a methodical approach will always win over a scatter-gun approach.
1. Check for Layer 1 (physical layer) issues first: is the ethernet (wired) or wireless link up? If that isn't working, nothing else will.
The ethernet is working, I am using it to send emails on my desktop computer. The wireless is also working, I can connect to it with my cellphone and an ipad that I use for work.
What is working for other devices is irrelevant until it comes to checking external connectivity (which we can now safely assume is working). So, lets concentrate on the device that is not working. Is the ethernet connection between that device and the network switch/router working? Is that a wired ethernet or wireless ethernet connection?
See the answer he posted at 16:36 UTC, has some of the needed data. He gets a link and an IP; I don't know about route and connectivity, he did no pings. wlan doesn't, at all. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (6)
-
Carlos E. R. -
Dave Howorth -
Mark Misulich -
Patrick Shanahan -
Per Jessen -
Rodney Baker