I bind my netbook to my PC having a broadband Internet connection and check the option to use the PC for networking. I then open the NetworkManager applet menu and see the connection created. But it's not useable as I click to connect.
I tried it several times with same result.
Steps to Reproduce:
1. Bind a notebook to a PC having a USB bluetooth dongle installed;
2. Choose the newly created Internet connection in the NetworkManager applet.
The NetworkManager icon twirls for a while showing it is working on the command, but then goes back to "disconnected". No connection actually established. When doing same action with a mobile phone it connects well and changes its icon to "wireless connection".
I have also tried to do the same with Blueman and it also failed saying "Failed to obtain an IP address on bnep0". I'm not sure if it's related, though, as these are different software.
I have googled for the error message, but it seems to be a rare issue. I have also asked on IRC, but I assume noone got interested to answer.
*** Bug 593572 has been marked as a duplicate of this bug. ***
*** Bug 593570 has been marked as a duplicate of this bug. ***
This is what I have on my desktop PC:
I will provide other info if needed. Thank you.
This problem may have been fixed in a testing update of NetworkManager. Try:
su -c 'yum --enablerepo=updates-testing update NetworkManager'
and see if that fixes your problem. The specific fixes are for Bluetooth PAN connections, which it sounds like you're using. If this update fails, please attach your /var/log/messages file from the time the error occurs. Thanks!
Created attachment 415391 [details]
Created attachment 415392 [details]
Also, this time there was no menu item until I logged out and back in.
I believe this is due to errors with the kernel driver for your bluetooth device:
May 20 20:40:35 mini dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 67 interval 14
May 20 20:40:37 mini kernel: btusb_intr_complete: hci0 urb f0a71800 failed to resubmit (1)
May 20 20:40:37 mini kernel: btusb_bulk_complete: hci0 urb f0a71a80 failed to resubmit (1)
May 20 20:40:37 mini kernel: btusb_bulk_complete: hci0 urb f0a71e80 failed to resubmit (1)
May 20 20:40:44 mini NetworkManager: <warn> (bnep0): DHCPv4 request timed out.
May 20 20:40:44 mini NetworkManager: <info> (bnep0): canceled DHCP transaction, DHCP client pid 2555
Basically, NM can't get a response from your device for the DHCP requests over the PAN interface. The messages from the kernel are somewhat worrying and possibly indicative of a failure of the bluetooth stack to communicate with the hardware.
The problem persists.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.