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)