Tethering interface

Bug #1172136 reported by GenghisKhan on 2013-04-24
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Wishlist
Unassigned

Bug Description

Previous summary: Bluetooth interface: bnep0

bnep0 is the name of Bluetooth interface.

The suggestion is as follows:

Adding more network interface or adding an ability to add more than two fields of network interface (currently Wireless and Wired).

I am using a wired interface (eth0) most of the time and it is cumbersome for me to switch every now and then the Wired interface field from eth0 to bnep0 and from bnep0 to eth0, which is easier than using # dhclient bnep0.

You can use icons from the Blueman project to be displayed when the bnep0 interface is available.
/usr/share/icons/hicolor/scalable/apps/blueman.svg

GenghisKhan (genghiskhan) wrote :

Please add a field for Bluetooth or a custom Interface field, so that users would not need to rename eth0 (Ethernet) to bnep0.

Changed in wicd:
status: New → Incomplete
status: Incomplete → New
importance: Undecided → Wishlist

Where do you see this in the interface?

For instances, under "Preferences", where the wireless and the wired interface is listed, add a third option for the Bluetooth?

Changed in wicd:
status: New → Incomplete
GenghisKhan (genghiskhan) wrote :

> Where do you see this in the interface?

In ifconfig, after clicking on Connect to/Network Access Point (ex. iPhone device) in Blueman.

> For instances, under "Preferences", where the wireless and the wired interface is listed, add a third option for the Bluetooth?

Yes, but it may be hidden and appear automatically when bnep0 is discovered, if bnep0 or bnep* is how all Bluetooth Internet Tethering services are realized.

Until there would be a one-click-ed way to connect to Network Access Point service, by Blueman, I suppose, I suggest to add a balloon notification says "Bluetooth Network Access Point is available" with a "Connect" button on that balloon OR adding a check-box in preferences "Prefer Bluetooth Network Access Point".

GenghisKhan (genghiskhan) wrote :

- OR adding a check-box in preferences "Prefer Bluetooth Network Access Point".
+ OR adding a check-box in preferences "Auto-connect to Bluetooth Network Access Point when discovered".

Changed in wicd:
status: Incomplete → Confirmed

In general, this feature request is about adding support for a separate Bluetooth interface configuration.

From an end user perspective, I think the proposal below would be quite consistent with the current way it works:

1) Make the Bluetooth interface name ("bnep0", in your example) configurable. For this, I would propose to add a configuration textbox "Bluetooth interface:" under the existing textbox "Wired interface:" where you can fill in "bnep0" if that's your primary bluetooth interface.

2) Then indeed, under the checkbox for the option "Always switch to a wired connection when available", add a check-box "Always switch to a Bluetooth connection when available".

3) In the main network list, show a section "Bluetooth Network", underneath and similar to the existing "Wired Network", above the list of wireless networks that have been found.

One could argue that there are more generic, less verbose ways of configuring the list of interfaces and their priorities. In theory, this would be even nicer to have, but will probably require more coding work (or something for wicd 2.0)?

GenghisKhan (genghiskhan) wrote :

The following proposition, which is not a good solution, involves a Bluetooth Manager and Wicd:

* Add to Blueman an option that would execute a command after establishing Network Access Point, but then it would be necessary to do so with Bluetooth Manager of KDE and others, so this proposition is too specific and is not good.

* Add to Wicd a Command Line argument that would add a custom interface.

Thinking...

Please use --wireless or --wired to specify the type of connection to operate on.

 --bluetooth bnep0 (it is as if I write --custom custom0, not good)

Failed to think.

description: updated
tags: added: usb0
summary: - Bluetooth interface: bnep0
+ Tethering interface
GenghisKhan (genghiskhan) wrote :

Please see the following resources:
https://wiki.archlinux.org/index.php/Android_Tethering
http://wiki.gentoo.org/wiki/Android_USB_Tethering

> You can use icons from the Blueman project to be displayed when the bnep0 interface is available.
/usr/share/icons/hicolor/scalable/apps/blueman.svg

Instead, you can use one of these icons:
insert-link (better without "arrow" part)
network-cellular-connected (better without "arrows" part)
phone (seems like best choice, as long as it looks like a cellular phone in othere themes)
preferences-system-sharing

All above icons are included in gnome-icon-theme.

tags: added: usb
tags: added: tethering
GenghisKhan (genghiskhan) wrote :

A note I want to post:

$ wicd-cli
Please use --wireless or --wired or --tether to specify the type of connection to operate on.
No operations performed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers