tethering to android via usb/bluetooth fails
Open, Needs TriagePublic

Description

I tried to share internet from my phone to my laptop using a USB cable and bluetooth. Both failed. Actually bluetooth worked once, but I couldn't get it to work again. Watching journalctl suggests that there might be a race condition in the network set up. I will attach a log to this report.

I am up-to-date with tanglue 3.0 including the updates to kernel 4.3 etc.

May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): new Ethernet device (driver: 'rndis_host' ifindex: 7)
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): exported as /org/freedesktop/NetworkManager/Devices/4
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): link connected
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): preparing device
May 24 10:30:39 droplet NetworkManager[2649]: <info> keyfile: add connection in-memory (30f4884f-5622-45b9-99ee-7f26989dd0d1,"Wired connection 2")
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): created default wired connection 'Wired connection 2'
May 24 10:30:39 droplet NetworkManager[2649]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/net/enx026472600378, iface: enx026472600378)
May 24 10:30:39 droplet NetworkManager[2649]: <info> device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/net/enx026472600378, iface: enx026472600378): no ifupdown configuration found.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
May 24 10:30:39 droplet NetworkManager[2649]: <info> Auto-activating connection 'Wired connection 2'.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: starting connection 'Wired connection 2'
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) scheduled...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) started...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 10:30:39 droplet NetworkManager[2649]: <info> NetworkManager state is now CONNECTING
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) scheduled...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) complete.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) starting...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: prepare -> config (reason 'none') [40 50 0]
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) successful.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) complete.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) started...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: config -> ip-config (reason 'none') [50 70 0]
May 24 10:30:39 droplet NetworkManager[2649]: <info> Activation (enx026472600378) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 24 10:30:39 droplet NetworkManager[2649]: <info> dhclient started with pid 4249
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) complete.
May 24 10:30:39 droplet dhclient[4249]: Bind socket to interface: No such device
May 24 10:30:39 droplet dhclient[4249]:
May 24 10:30:39 droplet dhclient[4249]: If you think you have received this message due to a bug rather
May 24 10:30:39 droplet dhclient[4249]: than a configuration issue please read the section on submitting
May 24 10:30:39 droplet dhclient[4249]: bugs on either our web page at www.isc.org or in the README file
May 24 10:30:39 droplet dhclient[4249]: before submitting a bug. These pages explain the proper
May 24 10:30:39 droplet dhclient[4249]: process and the information we find helpful for debugging..
May 24 10:30:39 droplet dhclient[4249]:
May 24 10:30:39 droplet dhclient[4249]: exiting.
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): DHCPv4 client pid 4249 exited with status 1
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): DHCPv4 state changed unknown -> done
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): canceled DHCP transaction
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) started...
May 24 10:30:39 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) complete.
May 24 10:30:40 droplet org.gtk.vfs.Daemon[3229]: Android device detected, assigning default bug flags
May 24 10:30:40 droplet org.gtk.vfs.Daemon[3229]: Received event PTP_EC_DevicePropChanged in session 1
May 24 10:30:40 droplet org.gtk.vfs.Daemon[3229]: Received event PTP_EC_DevicePropChanged in session 1
May 24 10:30:40 droplet org.gtk.vfs.Daemon[3229]: Received event PTP_EC_DevicePropChanged in session 1
May 24 10:30:41 droplet avahi-daemon[2658]: Joining mDNS multicast group on interface enx026472600378.IPv6 with address fe80::64:72ff:fe60:378.
May 24 10:30:41 droplet avahi-daemon[2658]: New relevant interface enx026472600378.IPv6 for mDNS.
May 24 10:30:41 droplet avahi-daemon[2658]: Registering new address record for fe80::64:72ff:fe60:378 on enx026472600378.*.
May 24 10:30:42 droplet ModemManager[2647]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1': not supported by any plugin
May 24 10:30:42 droplet ntpd[2810]: Listen normally on 7 enx026472600378 fe80::64:72ff:fe60:378 UDP 123
May 24 10:30:42 droplet ntpd[2810]: peers refreshed
May 24 10:30:44 droplet ntpd_intres[2815]: host name not found: 0.debian.pool.ntp.org
May 24 10:30:44 droplet ntpd_intres[2815]: host name not found: 1.debian.pool.ntp.org
May 24 10:30:44 droplet ntpd_intres[2815]: host name not found: 2.debian.pool.ntp.org
May 24 10:30:44 droplet ntpd_intres[2815]: host name not found: 3.debian.pool.ntp.org
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
May 24 10:31:11 droplet NetworkManager[2649]: <info> NetworkManager state is now DISCONNECTED
May 24 10:31:11 droplet NetworkManager[2649]: <warn> (enx026472600378): Activation: failed for connection 'Wired connection 2'
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): device state change: failed -> disconnected (reason 'none') [120 30 0]
May 24 10:31:11 droplet NetworkManager[2649]: <info> (enx026472600378): deactivating device (reason 'none') [0]
May 24 10:31:11 droplet avahi-daemon[2658]: Withdrawing address record for fe80::64:72ff:fe60:378 on enx026472600378.
May 24 10:31:11 droplet avahi-daemon[2658]: Leaving mDNS multicast group on interface enx026472600378.IPv6 with address fe80::64:72ff:fe60:378.
May 24 10:31:11 droplet avahi-daemon[2658]: Interface enx026472600378.IPv6 no longer relevant for mDNS.

jpritikin edited the task description. (Show Details)May 26 2016, 8:05 PM

Here are the logs from the 1 time that I got bluetooth to work. Let me know what else you need to diagnose the issue.

May 24 08:18:45 droplet colord[2957]: Automatic metadata add icc-d390c71c09b45542cff408bbb5f3ae4e to xrandr-Chi Mei Optoelectronics corp.
May 24 08:18:45 droplet colord[2957]: Device added: xrandr-Chi Mei Optoelectronics corp.
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: starting connection 'Motorola Moto E Network'
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) scheduled...
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) started...
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 08:18:50 droplet NetworkManager[2741]: <info> NetworkManager state is now CONNECTING
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) scheduled...
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) complete.
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) starting...
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): device state change: prepare -> config (reason 'none') [40 50 0]
May 24 08:18:50 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) complete.
May 24 08:18:52 droplet bluetoothd[3383]: connected
May 24 08:18:52 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: (bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via PAN.
May 24 08:18:52 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
May 24 08:18:52 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 3 of 5 (IP Configure Start) started...
May 24 08:18:52 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): device state change: config -> ip-config (reason 'none') [50 70 0]
May 24 08:18:52 droplet NetworkManager[2741]: <warn> (00:00:00:00:5A:AD): interface bnep0 not up for IP configuration
May 24 08:18:52 droplet systemd-udevd[3927]: error changing net interface name 'bnep0' to 'enxacfdce6e5b9e': Device or resource busy
May 24 08:18:52 droplet NetworkManager[2741]: <info> Activation (bnep0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 24 08:18:52 droplet systemd-udevd[3927]: could not rename interface '4' from 'bnep0' to 'enxacfdce6e5b9e': Device or resource busy
May 24 08:18:52 droplet NetworkManager[2741]: <info> dhclient started with pid 3931
May 24 08:18:52 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 3 of 5 (IP Configure Start) complete.
May 24 08:18:52 droplet NetworkManager[2741]: <info> (bnep0): driver 'unknown' does not support carrier detection.
May 24 08:18:52 droplet NetworkManager[2741]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/net/bnep0, iface: bnep0)
May 24 08:18:52 droplet NetworkManager[2741]: <info> device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/net/bnep0, iface: bnep0): n
May 24 08:18:52 droplet dhclient[3931]: DHCPDISCOVER on bnep0 to 255.255.255.255 port 67 interval 4
May 24 08:18:53 droplet avahi-daemon[2743]: Joining mDNS multicast group on interface bnep0.IPv6 with address fe80::aefd:ceff:fe6e:5b9e.
May 24 08:18:53 droplet avahi-daemon[2743]: New relevant interface bnep0.IPv6 for mDNS.
May 24 08:18:53 droplet avahi-daemon[2743]: Registering new address record for fe80::aefd:ceff:fe6e:5b9e on bnep0.*.
May 24 08:18:54 droplet ModemManager[2728]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-7': not supported by any plugin
May 24 08:18:55 droplet ntpd[2952]: Listen normally on 4 bnep0 fe80::aefd:ceff:fe6e:5b9e UDP 123
May 24 08:18:55 droplet ntpd[2952]: peers refreshed
May 24 08:18:56 droplet dhclient[3931]: DHCPDISCOVER on bnep0 to 255.255.255.255 port 67 interval 5
May 24 08:18:57 droplet ntpd_intres[2959]: host name not found: 0.debian.pool.ntp.org
May 24 08:18:57 droplet ntpd_intres[2959]: host name not found: 1.debian.pool.ntp.org
May 24 08:18:57 droplet ntpd_intres[2959]: host name not found: 2.debian.pool.ntp.org
May 24 08:18:57 droplet ntpd_intres[2959]: host name not found: 3.debian.pool.ntp.org
May 24 08:18:59 droplet dhclient[3931]: DHCPREQUEST on bnep0 to 255.255.255.255 port 67
May 24 08:18:59 droplet dhclient[3931]: DHCPOFFER from 192.168.44.1
May 24 08:18:59 droplet dhclient[3931]: DHCPACK from 192.168.44.1
May 24 08:18:59 droplet NetworkManager[2741]: <info> address 192.168.44.222
May 24 08:18:59 droplet NetworkManager[2741]: <info> plen 24 (255.255.255.0)
May 24 08:18:59 droplet NetworkManager[2741]: <info> gateway 192.168.44.1
May 24 08:18:59 droplet NetworkManager[2741]: <info> server identifier 192.168.44.1
May 24 08:18:59 droplet NetworkManager[2741]: <info> lease time 3600
May 24 08:18:59 droplet NetworkManager[2741]: <info> hostname 'droplet'
May 24 08:18:59 droplet NetworkManager[2741]: <info> nameserver '192.168.44.1'
May 24 08:18:59 droplet NetworkManager[2741]: <info> (bnep0): DHCPv4 state changed unknown -> bound
May 24 08:18:59 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 24 08:18:59 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 5 of 5 (IPv4 Commit) started...
May 24 08:18:59 droplet avahi-daemon[2743]: Joining mDNS multicast group on interface bnep0.IPv4 with address 192.168.44.222.
May 24 08:18:59 droplet avahi-daemon[2743]: New relevant interface bnep0.IPv4 for mDNS.
May 24 08:18:59 droplet avahi-daemon[2743]: Registering new address record for 192.168.44.222 on bnep0.IPv4.
May 24 08:18:59 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 24 08:18:59 droplet NetworkManager[2741]: <info> (00:00:00:00:5A:AD): Activation: Stage 5 of 5 (IPv4 Commit) complete.
May 24 08:18:59 droplet dhclient[3931]: bound to 192.168.44.222 -- renewal in 1354 seconds.

Here's what usually happened with bluetooth:

May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: starting connection 'Motorola Moto E Network'
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) scheduled...
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) started...
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 20:33:51 droplet NetworkManager[2589]: <info> NetworkManager state is now CONNECTING
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) scheduled...
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 1 of 5 (Device Prepare) complete.
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) starting...
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): device state change: prepare -> config (reason 'none') [40 50 0]
May 24 20:33:51 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): Activation: Stage 2 of 5 (Device Configure) complete.
May 24 20:33:51 droplet bluetoothd[3063]: connected
May 24 20:33:51 droplet systemd-udevd[12372]: error changing net interface name 'bnep0' to 'enxacfdce6e5b9e': Device or resource busy
May 24 20:33:51 droplet systemd-udevd[12372]: could not rename interface '4' from 'bnep0' to 'enxacfdce6e5b9e': Device or resource busy
May 24 20:33:51 droplet NetworkManager[2589]: <info> (bnep0): driver 'unknown' does not support carrier detection.
May 24 20:33:51 droplet NetworkManager[2589]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/net/bnep0, iface: bnep0)
May 24 20:33:51 droplet NetworkManager[2589]: <info> device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/net/bnep0, iface: bnep0): no ifupdo
May 24 20:33:53 droplet avahi-daemon[2575]: Joining mDNS multicast group on interface bnep0.IPv6 with address fe80::aefd:ceff:fe6e:5b9e.
May 24 20:33:53 droplet avahi-daemon[2575]: New relevant interface bnep0.IPv6 for mDNS.
May 24 20:33:53 droplet avahi-daemon[2575]: Registering new address record for fe80::aefd:ceff:fe6e:5b9e on bnep0.*.
May 24 20:33:53 droplet ModemManager[2571]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-7': not supported by any plugin
May 24 20:33:55 droplet ntpd[2760]: Listen normally on 4 bnep0 fe80::aefd:ceff:fe6e:5b9e UDP 123
May 24 20:33:55 droplet ntpd[2760]: peers refreshed
May 24 20:33:57 droplet ntpd_intres[2769]: host name not found: 0.debian.pool.ntp.org
May 24 20:33:57 droplet ntpd_intres[2769]: host name not found: 1.debian.pool.ntp.org
May 24 20:33:57 droplet ntpd_intres[2769]: host name not found: 2.debian.pool.ntp.org
May 24 20:33:57 droplet ntpd_intres[2769]: host name not found: 3.debian.pool.ntp.org
May 24 20:34:21 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
May 24 20:34:21 droplet NetworkManager[2589]: <info> NetworkManager state is now DISCONNECTED
May 24 20:34:21 droplet NetworkManager[2589]: <warn> (00:00:00:00:5A:AD): Activation: failed for connection 'Motorola Moto E Network'
May 24 20:34:21 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): device state change: failed -> disconnected (reason 'none') [120 30 0]
May 24 20:34:21 droplet NetworkManager[2589]: <info> (00:00:00:00:5A:AD): deactivating device (reason 'none') [0]
May 24 20:34:21 droplet avahi-daemon[2575]: Withdrawing address record for fe80::aefd:ceff:fe6e:5b9e on bnep0.
May 24 20:34:21 droplet avahi-daemon[2575]: Leaving mDNS multicast group on interface bnep0.IPv6 with address fe80::aefd:ceff:fe6e:5b9e.
May 24 20:34:21 droplet avahi-daemon[2575]: Interface bnep0.IPv6 no longer relevant for mDNS.
May 24 20:34:21 droplet avahi-daemon[2575]: Withdrawing workstation service for bnep0.
May 24 20:34:21 droplet NetworkManager[2589]: <info> devices removed (path: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/net/bnep0, iface: bnep0)
May 24 20:34:23 droplet ntpd[2760]: Deleting interface #4 bnep0, fe80::aefd:ceff:fe6e:5b9e#123, interface stats: received=0, sent=0, dropped=0, active_time=28 secs
May 24 20:34:23 droplet ntpd[2760]: peers refreshed

Bwt I saw your bug report concerning tethering with Android. I tend to say that Android could be the cause. I saw that ipv4 connection worked and ipv6 failed. Somewhere I read that dhcpv6 in Android still is not working. Maybe you could set the parameters for the network connection via bluetooth and usb to ipv4 only and give it again a try.

Where would I set the network connection parameters? On the Android site or laptop side?

jeno added a subscriber: jeno.Jun 18 2016, 7:36 AM

On the laptop. I guess you use networkmanager. There you are able set up your connection parameters and your should be able to deselect ipv6

Disabling ipv6 makes it fail much faster. Here is the log:

Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: starting connection 'Profile 1'
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) started...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) scheduled...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 1 of 5 (Device Prepare) complete.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) starting...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) successful.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 2 of 5 (Device Configure) complete.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) started...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> Activation (enx026472600378) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> dhclient started with pid 12460
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 3 of 5 (IP Configure Start) complete.
Jun 20 08:51:13 droplet dhclient[12460]: Bind socket to interface: No such device
Jun 20 08:51:13 droplet dhclient[12460]:
Jun 20 08:51:13 droplet dhclient[12460]: If you think you have received this message due to a bug rather
Jun 20 08:51:13 droplet dhclient[12460]: than a configuration issue please read the section on submitting
Jun 20 08:51:13 droplet dhclient[12460]: bugs on either our web page at www.isc.org or in the README file
Jun 20 08:51:13 droplet dhclient[12460]: before submitting a bug. These pages explain the proper
Jun 20 08:51:13 droplet dhclient[12460]: process and the information we find helpful for debugging..
Jun 20 08:51:13 droplet dhclient[12460]:
Jun 20 08:51:13 droplet dhclient[12460]: exiting.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): DHCPv4 client pid 12460 exited with status 1
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): DHCPv4 state changed unknown -> done
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): canceled DHCP transaction
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) started...
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> Disabling autoconnect for connection 'Profile 1'.
Jun 20 08:51:13 droplet NetworkManager[2604]: <warn> (enx026472600378): Activation: failed for connection 'Profile 1'
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): Activation: Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 20 08:51:13 droplet NetworkManager[2604]: <info> (enx026472600378): deactivating device (reason 'none') [0]

jeno added a comment.EditedJun 23 2016, 6:23 PM

Too bad. I thought this is the issue. Could you try the following: connect your phone by cable with your computer tethering switched on. What does "lsusb" and "ip link" tell you. Should be something like usb... or en..
Another idea, but i am not very convinced. Do you use some kind of security...firewall..protective software on your phone? It might block network traffic over usb and/or bluetooth
Forgot to mention. It might be also this one

Do you use some kind of security...firewall..protective software on your phone? It might block network traffic over usb and/or bluetooth

I thought it might be that because I flashed a recent cyanogen, but I tried with another phone Panasonic T41 Android 4.4.2 and obtained the same behavior.

lsusb

Bus 003 Device 008: ID 22b8:2e24 Motorola PCS 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x22b8 Motorola PCS
  idProduct          0x2e24 
  bcdDevice            2.28
  iManufacturer           1 motorola
  iProduct                2 Moto E
  iSerial                 3 TA10703Q3O
  bNumConfigurations      1

ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 80:fa:5b:1c:8d:25 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether ac:fd:ce:6e:5b:9a brd ff:ff:ff:ff:ff:ff
4: enx026472600378: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 02:64:72:60:03:78 brd ff:ff:ff:ff:ff:ff

The enx026472600378 interface is the phone.

It might be also [[ https://code.google.com/p/android/issues/detail?id=82545 | this one ]]

That issue has a bunch of complaints with no clear resolution.

jeno added a comment.Jun 26 2016, 9:17 AM
 The enx026472600378 interface is the phone.
 
>  It might be also [[ https://code.google.com/p/android/issues/detail?id=82545 | this one ]]
 
 That issue has a bunch of complaints with no clear resolution.

Is your Profile 1 connection mapped to the enx026472600378 interface? To be honest I am nearby on my wits end. I made a test with a moto g and a oneplus one on Kubuntu with kernel 4.4 (I only have a Tanglu on a virtual machine). Both phones support tethering via usb-cable flawlessly. They run on Android 5th and 6th Generation.
I found one point at the xda-developers forum. One member mentioned that AT&T use a tethering lock

I found one point at the xda-developers forum. One member mentioned that AT&T use a tethering lock

That wouldn't apply since I flashed cyanogen.

Kubuntu with kernel 4.4

That's great, but I was trying to ween myself off of Ubuntu. That's the whole point of tanglu, no?

Oh well, I guess I'll wait for the next tanglu release.

I upgraded to dasyatis today. I am happy to report that USB tethering works great again.