On 04/02/2017 01:15 AM, Andrei Borzenkov wrote:
02.04.2017 09:38, John Andersen пишет:
On 04/01/2017 10:39 PM, Andrei Borzenkov wrote:
02.04.2017 01:55, John Andersen пишет:
On My laptop:
If I plug a cat5 cable in, my wlan0 becomes unuseable.
It still has an IP. Network Manager still shows it connected. Kde Connect to my phone still works.
But: Ping -I wlan0 <target> doesn't work via wlan0 wget --bind-address=(wlan0-IP) fails Existing ssh connections via wlan0 become dead
Is this Intentional and Normal?
Show "ip a" and "ip r" output with both interfaces connected.
Here it is, along with a simple ping test, one via each:
jsa@poulsbo:~> ip a 1: lo:
mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:15:c5:55:97:51 brd ff:ff:ff:ff:ff:ff inet 192.168.2.232/24 brd 192.168.2.255 scope global dynamic eth0 valid_lft 10767sec preferred_lft 10767sec inet6 fe80::215:c5ff:fe55:9751/64 scope link valid_lft forever preferred_lft forever 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:16:cf:89:40:37 brd ff:ff:ff:ff:ff:ff inet 192.168.86.232/24 brd 192.168.86.255 scope global dynamic wlan0 valid_lft 86361sec preferred_lft 86361sec inet6 fe80::216:cfff:fe89:4037/64 scope link valid_lft forever preferred_lft forever 4: vmnet8: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff inet 192.168.193.1/24 brd 192.168.193.255 scope global vmnet8 valid_lft forever preferred_lft forever jsa@poulsbo:~> jsa@poulsbo:~> ip r default via 192.168.2.1 dev eth0 proto static metric 100 default via 192.168.86.1 dev wlan0 proto static metric 600 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.232 metric 100 192.168.86.0/24 dev wlan0 proto kernel scope link src 192.168.86.232 metric 600 How these two interfaces are connected? Do they go to the same router?
eth0 is connected via cat5 to 192.168.2.1 (192.168.2.1 is an opensuse box which is my main router/firewall/gateway). Wlan0 is connected by wifi to 192.168.86.1 (wifi router) which is connected to that same 192.168.2.1 network. So yes, eventually wlan0 arrives at the same router as does eth0. But here's the thing... After bringing up both interfaces: eth0 can ping just about anywhere. wlan0 can't ping anywhere beyond its own subnet. Taking down eth0 makes wlan0 instantly able to ping anywhere.
Does it work if you create explicit route to this host?
ip route add 209.112.129.41/32 via 192.168.86.1 dev wlan0
Yes, after adding this route I can ping that specific machine. Removing that route blocks pinging that IP again. Does this suggest that Network Manager removes ALL routes from a wifi interface when a wired interface becomes available? Is this intentional? It didn't use to be that way in past releases. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org