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)