NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having trouble the last week or two ssh'sing into the machine, and printing from the machine when I am sitting at the keyboard. I also could not connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The Android phone is running Android 12, and the phone is set to "USB Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the machine uses the Android phone as the ethernet connection. It literally calls the connection "ethernet", as if it was using the network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new behavior. Second, the wired gigabit ethernet connection is not used by default. And thrid, the Android phone's connection is called "ethernet" instead of something more meaningful like "USB" or "Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was misleading enough to waste a lot of time troubleshooting the issue. I thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is the Android phone uses Wifi and it is on a different VLAN and subnet to keep traffic segregated from my trusted internal network.
-----
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
Docs: man:systemd-
# service network-manager status
● NetworkManager.
Loaded: loaded (/lib/systemd/
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkMana
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.
└─928 /usr/sbin/
...
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitec
ProcVersionSign
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Ethernet 5d31ea14-
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1)
IpRoute:
default via 192.168.11.111 dev usb0 proto dhcp metric 100
169.254.0.0/16 dev usb0 scope link metric 1000
192.168.11.0/24 dev usb0 proto kernel scope link src 192.168.11.182 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitec
ProcVersionSign
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Ethernet 5d31ea14-
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled enabled enabled enabled
Thank you for your bug report, could you do
$ apport-collect 1975549
on the machine at the time you are having the issue?