WireGuard fails to provide Internet after upgrade from 5.4.0-1026-raspi to 5.4.0-1028-raspi; screen 4.8.0-1ubuntu0.1 at fault

[juanejot]

Initial problem:
Upon upgrading:
a) from kernel 5.8.0-43 to -44 on an Ubuntu Server 20.10 (on an AMD EPYC CPU), as well as
b) from aarch kernel 5.4.0-1026-raspi to 5.4.0-1028-raspi on a local Raspberry Pi 3 running Ubuntu Server 20.04,
(Both of which upgraded by apt-get update, then apt-get full-upgrade)
Wireguard stopped working on either installation: clients will connect & the server shows their status with “wg show,” but no Internet data gets sent by the server ("transfer: [several] KiB received, [92 or 184 or 220] B sent,” over the course of several minutes, with no ability to visit any website).

All clients still connect to & can use Internet from commercially (non-self-) maintained Wireguard servers, so it’s not on any of my clients’ ends, and there have been no config changes on any of my clients. Removing & reinstalling wireguard & wireguard-tools from my servers, messing around with .conf files (I could bore you with the details, but you’re Ubuntu, not wireguard) does not seem to help, even (when installed) with the wg-quick@wg0 daemon definitely active on both systems, says systemctl.

Partial (amd64-only) resolution:
An update to the package “screen” (from version 4.8.0_2 to 4.8.0_2ubuntu0.1_amd64.deb) on the 20.10 Linode server seems to have resolved the issue, so thanks for any part you may have had in quickly fixing that, same day!

Unfortunately, apt-cache policy seems to show that “screen” on the aarch version on my Pi remains at 4.8.0-1ubuntu0.1 today, with the same bad behavior. Hopefully the aarch and/or raspi repo gets updated soon!

[Doug Smythies (dsmythies)]

This is not an Ubuntu Serverguide documentation problem.
You seem to have done some work suggesting it might be a screen problem.
Anyway, setting status to invalid against Serverguide.

[juanejot (juanejot)]

Thanks, new to this process. Posted as a question for the screen package.