Intel's IWD 1.8 Wireless Daemon Released With WiFi P2P Support

[phoronix]

Phoronix: Intel's IWD 1.8 Wireless Daemon Released With WiFi P2P Support

The iNet wireless daemon (IWD) software developed by Intel's open-source team have released IWD 1.8...

http://www.phoronix.com/scan.php?page=news_item&px=Intel-IWD-1.8-Released

[schmidtbag]

What's the difference between that and ad-hoc?

[CochainComplex]

What's the difference between that and ad-hoc?

privileged access for NSA...if it includes intel me

[Danny3]

It would be nice if it would now be possible for a laptop to connect to a wireless router for internet but also to a phone where you can use Kore (Kodi's remote) or KDE connect for remote control or file sharing.
Right now it's only possible through the access point which is bad for signal quality and stability.
KDE Conect file sharing is very slow when it works or doesn't work at all sometimes.
The phone's battery also dies faster because of this indirect connection.

[brad0]

Right now it's only possible through the access point which is bad for signal quality and stability.

Sounds like you have a crappy network. Quite common. What would be more logical is to fix the network.

[tildearrow]

Typo:

handling of auto-connection and qucik scan,

[starshipeleven]

What's the difference between that and ad-hoc?

Ad-hoc is a crappy subset of wifi network specification, so apart from some technicalities that require all devices to support ad-hoc networks to connect to it (afaik Android does not) it will act like a normal wifi network, you set encryption and passwords and stuff and then connect to it, from multiple devices to the same "access point". Devices connected to the "access point" will be able to talk to each other too, as this is a network. (also called "multi-hop communication")

Wifi P2P or Wifi Direct is bluetooth-like device-to-device communication with wifi range and bandwith, so you do a pairing step and then connect one device to another device and have a dedicated link.
This is the wireless specification that is needed to support Miracast, aka remote screen protocol used by Android and Windows to connect wirelessly to a TV or HDMI/Chromecast dongle, but can be used for whatever else.
On Linux you can use Miracast (or create a Miracast server device you can connect PCs and Android phones to) with Miraclecast application https://github.com/albfan/miraclecast
Note how it says Wifi P2P/Direct support is needed.

[starshipeleven]

It would be nice if it would now be possible for a laptop to connect to a wireless router for internet but also to a phone where you can use Kore (Kodi's remote) or KDE connect for remote control or file sharing.
Right now it's only possible through the access point which is bad for signal quality and stability.

What is preventing you from connecting the smartphone to the same wireless router?
Or, if you are using a wireless router already for both devices, then it's wifi is crap (or it is placed in a bad spot in the house, get a wireless access point or a wifi extender)

KDE Conect file sharing is very slow when it works or doesn't work at all sometimes.

File a bug for KDE Connect? Use a better sync application like Syncthing (what I also use)?

[starshipeleven]

privileged access for NSA...if it includes intel me

Come on, it was a honest question

[StefanBruens]

What is preventing you from connecting the smartphone to the same wireless router?
Or, if you are using a wireless router already for both devices, then it's wifi is crap (or it is placed in a bad spot in the house, get a wireless access point or a wifi extender)

Transmitting data from one device to another via the router is very often a waste of resources - especially if the distance between the devices is much smaller than the distance to the router/AP. The airtime is at least twice as long (more if the AP is somewhat further away), RTTs are also longer.

For device-to-device communication in a managed ("with AP") environment TDLS (Tunneled-Direct-Link-Setup) exists, but unfortunately it is hardly supported. With TDLS, management frames go to the AP, while data is transmitted directly.

File a bug for KDE Connect? Use a better sync application like Syncthing (what I also use)?

KDE Connect works fine, at least if the used network is not total crap. Also, KConnect is not a "sync" application, but targetted at transferring single files between devices (among some other completely orthogonal stuff). It is a replacement for slow Bluetooth file transfers (i.e. what BT 4.0 promised with WiFi Offloading, but never delivered).