All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stotland, Inga" <inga.stotland@intel.com>
To: "sbrown@cortland.com" <sbrown@cortland.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: mesh: meshctl - How to access the functions in config-server.c?
Date: Mon, 30 Oct 2017 19:12:53 +0000	[thread overview]
Message-ID: <1509390771.5672.14.camel@intel.com> (raw)
In-Reply-To: <1509382210.18029.1.camel@cortland.com>

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

Hi Steve,

On Mon, 2017-10-30 at 12:50 -0400, Steve Brown wrote:
> The unicast address for meshctl is 0077. 
> 
> But the command "configure 0077" doesn't appear to be the answer.
> 
"configure 0077" does result in routing config commands to itself.
For example, "set-ttl" will result in change to local-node.json

However, the local config server does not send a status message back.
I submitted a patch to take care of that ([PATCH BlueZ] mesh: Add
config server response for loopback).

> Is it possible to route meshctl commands to itself?
> 
> Thanks,
> 
> Steve
> 
> 


I should mention that the implemented functionality in local config
server is very scarce: only get/set ttl and set publication are
currently handled.

Regards,

Inga

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3266 bytes --]

      reply	other threads:[~2017-10-30 19:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 16:50 mesh: meshctl - How to access the functions in config-server.c? Steve Brown
2017-10-30 19:12 ` Stotland, Inga [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1509390771.5672.14.camel@intel.com \
    --to=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sbrown@cortland.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.