After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613598 - [enh] add NAP support
[enh] add NAP support
Status: RESOLVED DUPLICATE of bug 783013
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
: 612871 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-03-22 15:01 UTC by Bastien Nocera
Modified: 2017-05-23 19:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2010-03-22 15:01:37 UTC 
NAP is the server counterpart of PANU, which we currently support.

The use cases for it are:
1)
- Laptop is connected to the internet via wi-fi or wired
- Phone wants to access Internet without using pricey data service (or can't access it when roaming)
2)
- Desktop/server is connected to the Internet
- Laptop has rubbish wireless driver, internet connection to update it is only a few clicks away

Implementation is a simple "Connect(nap)" on org.bluez.Network

The configuration UI would be responsible for creating the GConf-tree for enabling the connection, which would not be visible to in nm-applet (but in gnome-bluetooth or gnome-user-share instead, for example)
Comment 1 Dan Williams 2010-04-04 21:11:30 UTC 
*** Bug 612871 has been marked as a duplicate of this bug. ***
Comment 2 Olivier Crête 2013-07-25 16:31:33 UTC 
Sub-use-case of 1.

1.1) Phone is Android which doesn't support Ad-hoc.. Laptop is intel-based, which doesn't support master mode or wifi-direct.
Comment 3 Lubomir Rintel 2017-05-23 19:17:40 UTC 
In review now

*** This bug has been marked as a duplicate of bug 783013 ***