Hi Johan, On Mon, 2017-12-04 at 17:05 +0200, Johan Hedberg wrote: > Hi Steve, > > On Mon, Dec 04, 2017, Steve Brown wrote: > > I added the command as you suggested. > > > > I had to change them to net-connect and node-connect because of > > command > > completion. > > > > If I issue a node-connect while the mesh-shell ident command is > > active, > > it connects. > > > > If you think there's interest, I'll post the patch. > > I think we should definitely add support for this upstream, but after > thinking a bit more about it, maybe we could simply extend the > existing > connect command instead of adding a new one. Node Identity is always > in > the context of a given NetKey Index, so I think it'd be just as > natural > to have a second optional parameter to the existing connect command > which would be the element address. If only one parameter is given > then > meshctl looks for Net ID, if two are given it looks for Node ID. > Sounds > reasonable? > > Johan I'll do that. Saves lots of duplicated code. Steve -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
