[PATCH v2 08/10] mesh: Add virtual interface on booting
Mon Dec 29 19:03:23 PST 2014
2014-12-25 3:04 GMT+09:00 Jouni Malinen <j at w1.fi>:
> This exact same "limitation" applies to P2P groups. Why should mesh gate
> have an exception and need something new on the command line? That
> sounds undesirable to me.. I.e., if you want this to behave just like
> any other existing network block with disabled=0, there should not be
> MESH_INTERFACE_ADD command in the first place. If on the other hand you
> want this to be a special case, it sounds reasonable to expect
> MESH_INTERFACE_ADD command to be used.. What is the issue with using
> wpa_cli (or some other tool) to send a control interface command to
> enable mesh gate operation?
> I would like to better understand the high level use case for this. It
> does not sound desirable to get new command line parameters needed for
> all new types of connections and I don't see why mesh would be the
> special case needing such a command while others would not.
I have thought that creating vif on booting is allowed, because -m option is
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 ?
More information about the Hostap