Bug 748306

Summary: USB tethering device gets wrong MAC address, ends up as eth0 not usb0
Product: [Fedora] Fedora Reporter: Luke Hutchison <luke.hutch>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:06:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Luke Hutchison 2011-10-24 04:18:16 UTC
Description of problem:
Plugging in my HTC Sensation Android phone and enabling USB tethering causes NetworkManager to detect the device and connect to it, but tethering does not work, because NetworkManager thinks the device is eth0 not usb0. No connection usb0 is even created. The only solution is to manually create a connection usb0 in NetworkManager, and then manually specify the MAC addresses for both usb0 and eth0.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-3.git20110927.fc15.x86_64

How reproducible:
Every time

Steps to Reproduce:
See below

--



Plugged in phone and selected USB tethering in HTC tethering menu. lsusb shows:

Bus 002 Device 005: ID 0bb4:0ffe High Tech Computer Corp. Desire HD (modem mode)

NetworkManager connects automatically when the phone is plugged in, and says eth0 is active. The NM menu shows "HTC Android Phone" as eth0 and "Intel 82567V Gigabit" as disconnected.

ifconfig shows: 

eth0      Link encap:Ethernet  HWaddr 00:1C:7E:F4:0C:BD  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Memory:ffce0000-ffd00000 

usb0      Link encap:Ethernet  HWaddr 3A:79:3E:E5:AB:94  
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::3879:3eff:fee5:ab94/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:308 (308.0 b)  TX bytes:15595 (15.2 KiB)

system-config-network shows eth0 as Inactive and usb0 as Active, and shows usb0 correctly mapped to the phone and eth0 correctly mapped to the Intel 82567V. Clicking "Deactivate" on usb0 gives the error message that it can't be deactivated, and says:

ERROR    : [/etc/sysconfig/network-scripts/ifdown-eth] Device usb0 has MAC address 3A:79:3E:E5:AB:94, instead of configured address BA:60:15:45:1B:1F. Ignoring.

Clicking Edit on usb0 and then probing the MAC address overwrites the erroneous MAC address with the correct one.  Then the connection can be deactivated and reactivated without error. However NetworkManager still shows the USB device as eth0, and the data connection doesn't work.

Going into NetworkManager's connections list and manually setting the IP address for eth0 and then creating a new connection for usb0 (also with a manually-set IP address) fixes the problem.

Comment 1 Fedora End Of Life 2012-08-07 16:06:14 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping