[PATCH v2 08/10] mesh: Add virtual interface on booting

Jouni Malinen j
Tue Dec 30 06:43:02 PST 2014

On Tue, Dec 30, 2014 at 12:03:23PM +0900, Masashi Honma wrote:
> I have thought that creating vif on booting is allowed, because -m option is
> doing it.
> Now I recognize you think P2P_GROUP_ADD and MESH_GROUP_ADD as same priority,
> but -m option is used for more prior case.
> Could you explain what is a use case of -m option and how it is special ?

The -m parameter ("Configuration file for the P2P Device interface) does
not create a new virtual interface; it provides configuration for the
global P2P Device instance that some drivers uses. That P2P Device
context gets created automatically and as such, it is not similar to
P2P_GROUP_ADD/MESH_GROUP_ADD. The P2P Device instance is not used for
normal data connection (it is not even a netdev).

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list