Bug 712119

Summary: iphone usb tethering doesn't work as expected
Product: [Fedora] Fedora Reporter: Gianluca Cecchi <gianluca.cecchi>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 16:01:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
extract from f14 /var/log/messages
none
extract from f15 /var/log/messages
none
messages with new kernel and NM and problem disappeared... none

Description Gianluca Cecchi 2011-06-09 14:37:08 UTC
Description of problem:
Environment: iphone 3gs
In Fedora14 it seems NM doesn't manage usb tethering.
So when I connected my iphone via usb I had to:
- connect iphone via usb
- enable usb tethering on iphone menu
- automatically the ipheth kernel module was loaded and an interface
wwan0 created
- ifconfig wwan0 up
- dhclient wwan0
and I got an ip from the iphone, being able to go to internet this way.
This works in F14 with both fw 4.2.1 and 4.3.3 (in this latest the iphone menu is called "personal hot spot")

Now I'm testing on the same PC with Fedora 15 and same iphone with 4.3.3 fw
What it was usb tethering is now called personal hot spot on iphone menu.
For 3gs it remains bluetooth and usb tethering (the hot spot word by
apple is misleading in this case), while for iphone 4 devices there is
also a wifi option that makes it actually a hot spot.

In Fedora15 it seems Network Manager can manage this kind of
connection. Or at least it tries to manage the device...
My onboard nic is seen as em1.
When I connect the iphone and enable personal hotspot I have the
interface eth0 that appears.
I have configured a dhcp profile and attempt to bind it to my eth0
connection but it seems it doesn't get any ip and then it switches to
a static profile
(this latest one in my opinion is a bug... it simply shouldn't switch
to another profile but keep the interface as not connected)


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

How reproducible:
always

Steps to Reproduce:
1. connect iphone via usb
2. activate iphone menu "personal hot spot"
3. bind a predefined dhcp profile to apple iphone device
  
Actual results:
dhcpclient goes timeout

Expected results:
dhcpclient gets an IP to be able to surf internet

Additional info:

Other components:
Components:
libimobiledevice-1.1.1-1.fc15.x86_64
kernel: 2.6.38.6-27.fc15.x86_64

In F14 working enviroment:
libimobiledevice-1.0.4-1.fc14.x86_64
NetworkManager-0.8.4-1.fc14.x86_64
kernel-2.6.35.13-91.fc14.x86_64

I'm going to attach both f15 logs and f14 logs

Comment 1 Gianluca Cecchi 2011-06-09 14:40:56 UTC
Created attachment 503914 [details]
extract from f14 /var/log/messages

Comment 2 Gianluca Cecchi 2011-06-09 14:46:00 UTC
Created attachment 503916 [details]
extract from f15 /var/log/messages

embedded nic is named em1.
when connecting usb it names it as eth0.
As soon as it is plugged it tries a static ip conenction named "Poli" (because this profile is configured as automatic for all users).
Then I set a dhcp profile named "dhcp".
It tries but then it goes timeout and re-set "Poli" profile...

Comment 3 Dan Williams 2011-06-14 20:47:36 UTC
If you want to use a certain connection, you need to "lock" that connection to the specific device using the MAC address of that device.  YOu'd take the MAC address of the iphone eth interface and enter that in the "MAC Address" field for the connection in nm-connection-editor.  Then NM will only use that connection with the iphone ethernet interface.

Comment 4 Gianluca Cecchi 2011-06-24 13:11:01 UTC
Ok, I did the reverse:
I bound "Poli" connection to mac address of em1 integrated device.
Also, I updated my system and now it seems to work ok via NetworkManager.
I'm going to attach relevant /var/log/messages entries I get now.

For the record, current relevant packages involved are:
kernel 2.6.38.8-32.fc15.x86_64
NetworkManager 0.8.9997-4.git20110620
avahi 0.6.30-3 (though not changed since problem detection date)
let me know if you need other information, but I think you can close the ticket...
btw: the error
Jun 24 13:06:11 ope46 NetworkManager[868]: <error> [1308913571.764687] [nm-device-ethernet.c:753] real_update_permanent_hw_address(): (eth0): unable to read permanent MAC address (error 0)

was there both beofre and after resolution... donna what does it mean.
Gianluca

Comment 5 Gianluca Cecchi 2011-06-24 13:12:25 UTC
Created attachment 509752 [details]
messages with new kernel and NM and problem disappeared...

Comment 6 Fedora End Of Life 2012-08-07 16:01:20 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