[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
It is weird, my router is very old, it only supports 2.4G, and I can't reproduce the problem under 2.4G. (This is my laptop, it connects to my old router too.) hwang4@hwang4-Vostro-5390:~$ sudo iwlist wlp0s20f3 frequency wlp0s20f3 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 36 : 5.18 GHz Channel 40 : 5.2 GHz Channel 44 : 5.22 GHz Channel 48 : 5.24 GHz Channel 52 : 5.26 GHz Channel 56 : 5.28 GHz Channel 60 : 5.3 GHz Channel 64 : 5.32 GHz Channel 100 : 5.5 GHz Channel 104 : 5.52 GHz Channel 108 : 5.54 GHz Channel 112 : 5.56 GHz Channel 116 : 5.58 GHz Channel 120 : 5.6 GHz Channel 124 : 5.62 GHz Channel 128 : 5.64 GHz Channel 132 : 5.66 GHz Channel 136 : 5.68 GHz Channel 140 : 5.7 GHz Current Frequency=2.412 GHz (Channel 1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
I tested with new router, which supports 2.4GHz and 5GHz networks. When the RPI is connected to 5G network the problem disappear. However, it is persistent on 2.4GHz network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
Tried this, but I cannot find anything that means something to me with respect to the problem. The log is attached. Row 1: Here the RPI starts with ethernet cable attached and wlan0 configured. Both adapters seem to take their IPs. -> I can estasblish SSH to both. Row 743: I'm removing the ethernet cable and at this moment the eth0 goes down. I'm trying to establish SSH to wlan0 IP a couple of times without success. After that I'm switching off the RPi, plug in the ethernet cable and switch on again. Row 761: This the boot after power on. ** Attachment added: "Syslog" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+attachment/5307578/+files/syslog_1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
I just followed your steps to do the test, I followed all steps except step 7, since on my board, no need to run "netplan try" and "netplan apply", the eth0 and wlan0 already can get the ip from my router. Other steps are same. I can't reproduce your problem, with the new installed 1012 kernel, no matter I plug ethernet or not, I can ssh to wlan0 always. I don't know why you have problem. When problem happens, you could check the /var/log/syslog, it should contain the log about getting the ip for eth0 and wlan0, maybe you could find sth is not correct in that log. for example: Nov 24 07:17:04 ubuntu systemd-networkd[1098]: eth0: Gained carrier Nov 24 07:17:04 ubuntu systemd-networkd[1098]: eth0: DHCPv4 address 192.168.1.106/24 via 192.168.1.1 Nov 24 07:17:04 ubuntu systemd-timesyncd[1141]: Network configuration changed, trying to establish connection. Nov 24 07:17:03 ubuntu systemd-resolved[1139]: Using degraded feature set (UDP) for DNS server 202.106.46.151. Nov 24 07:17:03 ubuntu dbus-daemon[1208]: [system] AppArmor D-Bus mediation is enabled Nov 24 07:17:06 ubuntu wpa_supplicant[1097]: wlan0: WPA: Key negotiation completed with 50:bd:5f:ff:68:12 [PTK=CCMP GTK=CCMP] Nov 24 07:17:06 ubuntu wpa_supplicant[1097]: wlan0: CTRL-EVENT-CONNECTED - Connection to 50:bd:5f:ff:68:12 completed [id=0 id_str=] Nov 24 07:17:06 ubuntu systemd-networkd[1098]: wlan0: Gained carrier Nov 24 07:17:06 ubuntu systemd[1]: Started Snappy daemon. Nov 24 07:17:06 ubuntu systemd[1]: Starting Wait until snapd is fully seeded... Nov 24 07:17:06 ubuntu systemd-networkd[1098]: wlan0: DHCPv4 address 192.168.1.107/24 via 192.168.1.1 Nov 24 07:17:06 ubuntu pollinate[1242]: client verified challenge/response with [https://entropy.ubuntu.com/] Nov 24 07:17:06 ubuntu pollinate[1242]: client hashed response from [https://entropy.ubuntu.com/] Nov 24 07:17:06 ubuntu lxd.activate[1243]: => Starting LXD activation Nov 24 07:17:06 ubuntu lxd.activate[1243]: ==> Loading snap configuration Nov 24 07:17:06 ubuntu lxd.activate[1243]: ==> Checking for socket activation support Nov 24 07:17:06 ubuntu pollinate[1242]: client successfully seeded [/dev/urandom] Nov 24 07:17:06 ubuntu systemd[1]: pollinate.service: Succeeded. Nov 24 07:17:06 ubuntu systemd[1]: Started Pollinate to seed the pseudo random number generator. Nov 24 07:17:06 ubuntu systemd[1]: Starting OpenBSD Secure Shell server... Nov 24 07:17:06 ubuntu systemd[1]: Started Wait until snapd is fully seeded. Nov 24 07:17:06 ubuntu systemd[1]: Starting Apply the settings specified in cloud-config... Nov 24 07:17:06 ubuntu systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped. Nov 24 07:17:07 ubuntu lxd.activate[1243]: ==> Setting LXD socket ownership Nov 24 07:17:07 ubuntu lxd.activate[1243]: ==> LXD never started on this system, no need to start it now Nov 24 07:17:07 ubuntu systemd[1]: snap.lxd.activate.service: Succeeded. Nov 24 07:17:07 ubuntu systemd[1]: Started Service for snap application lxd.activate. Nov 24 07:17:07 ubuntu systemd[1]: Started OpenBSD Secure Shell server. Nov 24 07:17:07 ubuntu systemd[1]: Reached target Multi-User System. Nov 24 07:17:07 ubuntu systemd[1]: Reached target Graphical Interface. Nov 24 07:17:07 ubuntu systemd[1]: Starting Update UTMP about System Runlevel Changes... Nov 24 07:17:07 ubuntu systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. Nov 24 07:17:07 ubuntu systemd[1]: Started Update UTMP about System Runlevel Changes. Nov 24 07:17:07 ubuntu systemd-resolved[1139]: Using degraded feature set (UDP) for DNS server 202.106.46.151. Nov 24 07:17:08 ubuntu systemd-networkd[1098]: wlan0: Gained IPv6LL Nov 24 07:17:08 ubuntu systemd-networkd[1098]: wlan0: Configured -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
I've got a bit confused about the behavior of the system so I restarted the process to check what's happening. Here the steps I performed: 1. Install clean image on SD card. 2. Block internet access of the RPI, so no updates to be installed on first boot. 3. Reboot 4. Remove 50-cloud-init.yaml from /etc/netplan 5. Create eth0-dhcp.yaml in /etc/netplan with the following content: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: false optional: true 6. Create wlan0-dhcp.yaml in /etc/netplan with the following content: network: version: 2 wifis: wlan0: optional: true access-points: "SSID": password: "PASS" dhcp4: true dhcp6: false 7. Execute "netplan try" and "netplan apply" 8. Reboot 9. At that point the kernel is "linux-image-5.3.0-1007-raspi2" and both adapters are connected, have their IPs and SSH is possible to both. 10. Remove ethernet cable from RPI. 11. SSH over wlan0 IP is possible. 12. Reboot 13. Check SSH over wlan0 IP - still possible. 14. Unblock internet access of the RPI and run "sudo apt-get update" 15. Install newest kernel "linux-image-5.3.0-1012-raspi2": sudo apt install linux-image-5.3.0-1012-raspi2 16. Reboot 17. SSH over wlan0 IP - NOT possible (connection time out) 18. Connect ethernet cable. 19. Check again SSH over wlan0 IP - NOT possible (connection time out) 20. Check SSH over eth0 IP - connection possible, but after 5-10 minutes of waiting. 21. Install net tools: "sudo apt install net-tools" 22. ifconfig show that only eth0 is connected. wlan0 is up, but don't have IP. 23. Reboot 24. SSH possible over eth0 and wlan0. ifconfig confirm that both adapters have their IPs. 25. Remove ethernet cable from RPI. 26. SSH not possible to wlan0. 27. Connect ethernet cable - SSH still not possible to either eth0, nor wlan0. 28. Hard reset of the RPI to reboot it - remove power supply. 29. SSH over eth0 possible. ifconfig show that wlan0 is up, but don't have IP. I performed the same steps with "linux-image-5.3.0-1013-raspi2" and the results are the same. As a summaryI would say that "linux-image-5.3.0-1007-raspi2" have no issues with plug-in, pulg-out of the ethernet cable. wlan0 and eth0 seem to work independently and together without issues. With kernels above the before mentioned, plug-in/pulg-out of the ethernet cable disrupt wlan0 and without the cable, SSH (or ping) is not possible to wlan0. Tried to revert the kernel to 1007 (on another clean image) as you suggested, but after reboot I no longer can establish SSH to RPI. And as I'm running headless, I don't know if the RPI actually booted or it's a connection issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
Hi, I've checked multiple kernels and multiple methods to set up the network. I don't know what is going on, but I suspect that it might not be the kernel itself, but the network interfaces conflict. Can you share with me in details how to set up the wireless "wlan0" to connect on a clean image? May be I'm doing something wrong... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
When this problem happens, does the wifi network on rpi4 still work? e.g. using ping command or other network commands other than ssh? Another test is when problems happens, switch back to 1007 kernel (the 1007 kernel, initrd and dtb are in the folder of /boot/firmware/$filename.bak, remove .bak, then you could boot with 1007 kernel), does the ssh work again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
Actually with linux-image-5.3.0-1011-raspi2 also doesn't work. It reaches only once after restart to the "login:" and after entering the user it hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
Installed this kernel, but unfortunately is the same. I tried also with different network for eth0 and wlan0. I can establish SSL to the eth0 IP, but not to wlan0. Also checked the linux-image-5.3.0-1011-raspi2 from your post in this page: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790 -> Everything works with this kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
5.3.0-1012-raspi4 is just a testing kernel, it is based on 5.3.0-1012-raspi2, just changed the flavour name from raspi2 to raspi4, no function change. If you want to test with 5.3.0-1012-raspi4, please find them from: https://people.canonical.com/~hwang4/1012-raspi4/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
Hi, I don't know if that matters, but my "uname -a" returns "Linux ubuntu 5.3.0-1012-raspi2" and yours return "Linux ubuntu 5.3.0-1012-raspi4". How can I get this "Linux ubuntu 5.3.0-1012-raspi4" release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
@Stefan,
I just did the test according to your description, I didn't reproduce
your problem:
On my rpi4B with 4G ram and without ethernet cable connect, I installed
the 1012 kernel:
On the rpi4 board:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1012-raspi4 #14 SMP Thu Nov 21 11:46:38 UTC 2019 aarch64
aarch64 aarch64 GNU/Linux
ubuntu@ubuntu:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
renderer: networkd
wifis:
wlan0:
dhcp4: yes
dhcp6: no
access-points:
"mywifi":
password: "mypassword"
ubuntu@ubuntu:~$ sudo netplan apply
ubuntu@ubuntu:~$ ifconfig
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 44 bytes 3738 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3738 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099 mtu 1500
ether dc:a6:32:0e:9b:c5 txqueuelen 1000 (Ethernet)
RX packets 605 bytes 724475 (724.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 540 bytes 72600 (72.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ubuntu@ubuntu:~$ ifconfig
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 44 bytes 3738 (3.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 44 bytes 3738 (3.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163 mtu 1500
inet 192.168.1.109 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::dea6:32ff:fe0e:9bc5 prefixlen 64 scopeid 0x20
ether dc:a6:32:0e:9b:c5 txqueuelen 1000 (Ethernet)
RX packets 615 bytes 726200 (726.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 558 bytes 75051 (75.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
On my host machine:
hwang4@hwang4-Vostro-5390:~/work/mainline/build/eoan-rpi/ubuntu-eoan/patch$ ssh
ubuntu@192.168.1.109
The authenticity of host '192.168.1.109 (192.168.1.109)' can't be established.
ECDSA key fingerprint is SHA256:ABndCbsaeSF4OTivweZvtSSmvzbtA9j1t1qUjQF2CBg.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.109' (ECDSA) to the list of known hosts.
ubuntu@192.168.1.109's password:
Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-1012-raspi4 aarch64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:https://ubuntu.com/advantage
System information as of Thu Nov 21 14:07:33 UTC 2019
System load: 2.39 Processes:142
Usage of /: 52.4% of 7.00GB Users logged in: 1
Memory usage: 8%IP address for wlan0: 192.168.1.109
Swap usage: 0%
* Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
https://ubuntu.com/kubernetes/docs/release-notes
31 updates can be installed immediately.
25 of these updates are security updates.
To see these additional updates run: apt list --upgradable
Last login: Thu Nov 21 14:06:29 2019
ubuntu@ubuntu:~$ ls
focal-preinstalled-server-armhf+raspi3.img.xz
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1012-raspi4 #14 SMP Thu Nov 21 11:46:38 UTC 2019 aarch64
aarch64 aarch64 GNU/Linux
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Package changed: linux (Ubuntu) => linux-raspi2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853030
Title:
No connection through SSH over WIfi after kernel update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
apport information ** Tags added: apport-collected staging uec-images ** Description changed: After updating from kernel "linux-image-5.3.0-1007-raspi2" to "linux- image-5.3.0-1012-raspi2" I no longer can establish SSH connection to Raspberry over Wifi. When it is on wired connection, SSH works and initial screen shows that both adapters (eth0 and wlan0) are connected and have their IPs. "ifconfig" confirms that both adapters are up and have their IPs. Establishing SSH session with both IPs is successful. When I disconnect the network cable, SSH is no longer possible (connection time out). In the same time the router is showing that the Raspberry is connected to the Wifi network. Plugging back the wire does not make the SSH possible. A restart of the Raspberry is required with plugged in network cable in order to establish SSH again. The system is Raspberry Pi 4, 4GB with Ubuntu server X64 image - clean install. Reference info for what is done so far: https://answers.launchpad.net/ubuntu/+question/685941 Output of "ubuntu-bug linux": ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Mon Nov 18 16:46:39 2019 Dependencies: adduser 3.118ubuntu1 apt 1.9.4 apt-utils 1.9.4 binutils 2.33-2ubuntu1 binutils-aarch64-linux-gnu 2.33-2ubuntu1 binutils-common 2.33-2ubuntu1 busybox-initramfs 1:1.30.1-4ubuntu4 ca-certificates 20190110 coreutils 8.30-3ubuntu2 cpio 2.12+dfsg-9ubuntu0.1 debconf 1.5.73 debconf-i18n 1.5.73 device-tree-compiler 1.4.7-3ubuntu2 devio 1.2-1.2 dpkg 1.19.7ubuntu2 e2fsprogs 1.45.3-4ubuntu2 fdisk 2.34-0.1ubuntu2 flash-kernel 3.98ubuntu5.1 gcc-9-base 9.2.1-9ubuntu2 gpgv 2.2.12-1ubuntu3 initramfs-tools 0.133ubuntu10 initramfs-tools-bin 0.133ubuntu10 initramfs-tools-core 0.133ubuntu10 klibc-utils 2.0.6-1ubuntu3 kmod 26-1ubuntu1 libacl1 2.2.53-4 libapt-pkg5.90 1.9.4 libattr1 1:2.4.48-4 libaudit-common 1:2.8.5-2ubuntu1 libaudit1 1:2.8.5-2ubuntu1 libbinutils 2.33-2ubuntu1 libblkid1 2.34-0.1ubuntu2 libbz2-1.0 1.0.6-9.2 libc6 2.30-0ubuntu2 libcap-ng0 0.7.9-2 libcom-err2 1.45.3-4ubuntu2 libdb5.3 5.3.28+dfsg1-0.6ubuntu1 libext2fs2 1.45.3-4ubuntu2 libfdisk1 2.34-0.1ubuntu2 libffi6 3.2.1-9 libgcc1 1:9.2.1-9ubuntu2 libgcrypt20 1.8.4-5ubuntu2 libgmp10 2:6.1.2+dfsg-4 libgnutls30 3.6.9-5ubuntu1 libgpg-error0 1.36-7 libgpm2 1.20.7-5 libhogweed4 3.4.1-1 libidn2-0 2.2.0-2 libklibc 2.0.6-1ubuntu3 libkmod2 26-1ubuntu1 liblocale-gettext-perl 1.07-3build3 liblz4-1 1.9.1-1 liblzma5 5.2.4-1 liblzo2-2 2.10-0.1 libmount1 2.34-0.1ubuntu2 libncursesw6 6.1+20190803-1ubuntu1 libnettle6 3.4.1-1 libp11-kit0 0.23.17-2 libpam-modules 1.3.1-5ubuntu1 libpam-modules-bin 1.3.1-5ubuntu1 libpam-runtime 1.3.1-5ubuntu1 libpam0g 1.3.1-5ubuntu1 libpcre2-8-0 10.32-5 libseccomp2 2.4.1-0ubuntu0.19.10.3 libselinux1 2.9-2 libsemanage-common 2.9-3 libsemanage1 2.9-3 libsepol1 2.9-2 libsmartcols1 2.34-0.1ubuntu2 libss2 1.45.3-4ubuntu2 libssl1.1 1.1.1c-1ubuntu4 libstdc++6 9.2.1-9ubuntu2 libsystemd0 242-7ubuntu3 libtasn1-6 4.14-3 libtext-charwidth-perl 0.04-9 libtext-iconv-perl 1.7-6 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.1+20190803-1ubuntu1 libudev1 242-7ubuntu3 libunistring2 0.9.10-2 libuuid1 2.34-0.1ubuntu2 libzstd1 1.4.3+dfsg-1 linux-base 4.5ubuntu2 linux-modules-5.3.0-1012-raspi2 5.3.0-1012.14 login 1:4.5-1.1ubuntu4 logsave 1.45.3-4ubuntu2 lsb-base 11.0.1ubuntu1 lz4 1.9.1-1 mtd-utils 1:2.0.1-1ubuntu3 openssl 1.1.1c-1ubuntu4 passwd 1:4.5-1.1ubuntu4 perl-base 5.28.1-6build1 sensible-utils 0.0.12 tar 1.30+dfsg-6 u-boot-tools 2019.07+dfsg-1ubuntu3 ubuntu-keyring 2018.09.18.1 ucf 3.0038+nmu1 udev 242-7ubuntu3 util-linux 2.34-0.1ubuntu2 uuid-runtime 2.34-0.1ubuntu2 zlib1g 1:1.2.11.dfsg-1ubuntu3 DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1012-raspi2 5.3.0-1012.14 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor: 3 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 Hardware : BCM2835 Revision : c03111 Serial : 1000352e9f36 Model: Raspberry Pi 4 Model B Rev 1.1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-1012.14-raspi2 5.3.7 SourcePackage: linux-raspi2 Tags: eoan uec-images Uname: Linux 5.3.0-1012-raspi2 aarch64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 11 2019 seq + crw-rw 1 root
