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: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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 192.168.193.0/24 dev vmnet8 proto kernel scope link src 192.168.193.1 jsa@poulsbo:~> ping -I wlan0 www.alaska.net PING aws01.nwc.acsalaska.net (209.112.129.41) from 192.168.86.232 wlan0: 56(84) bytes of data. ^C --- aws01.nwc.acsalaska.net ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5034ms
Ping tests:
jsa@poulsbo:~> ping -I eth0 www.alaska.net PING aws01.nwc.acsalaska.net (209.112.129.41) from 192.168.2.232 eth0: 56(84) bytes of data. 64 bytes from 209.112.129.41: icmp_seq=1 ttl=53 time=47.7 ms 64 bytes from 209.112.129.41: icmp_seq=2 ttl=53 time=46.2 ms ^C --- aws01.nwc.acsalaska.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 46.242/46.988/47.734/0.746 ms
If I reach around back and disconnect the cat5, then wlan0 will ping just fine but with both up, wifi gets essentially choked off somehow. I remember quite explicity that this did use to work on this very same hardware a version or two ago 13.2 or maybe 12.?. -- 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