Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

docs: Confusing use of the otbr-snap for non-BR purposes #19

Open
prash813 opened this issue Feb 28, 2024 · 1 comment
Open

docs: Confusing use of the otbr-snap for non-BR purposes #19

prash813 opened this issue Feb 28, 2024 · 1 comment

Comments

@prash813
Copy link

*Please describe the question or issue you're facing with "How to run Matter applications with Thread networking on Ubuntu - Matter on Ubuntu documentation"

I have couple of issues with the dcoumentation

There are two RCPs and they are controlled by same snap otbr-snap installed on Machine A and B.

  1. why otbr-snap running on machine B needs avahi-control interface? becuase Mchine B being just a thread device will not use
    mDNS for service publishing it
  2. why would you need to provide infra-if config option for the otbr-snap running on machine B?

Reported from: https://canonical-matter.readthedocs-hosted.com/en/latest/how-to/matter-and-thread-on-ubuntu/

@farshidtz farshidtz changed the title docs: TYPE YOUR QUESTION HERE docs: Confusing use of the otbr-snap for non-BR purposes Feb 28, 2024
@farshidtz
Copy link
Member

farshidtz commented Apr 24, 2024

Thanks for the feedback.
The documentation doesn't explicitly say that those steps are required, but it points the reader to another how-to, which does.

The avahi-control interface is not required. I'll add a note for that.
The agent does attempt to use the client but moves on without erroring out:

otbr-agent[16695]: [INFO]-MDNS----: Avahi client state changed to 101
otbr-agent[16695]: [INFO]-MDNS----: Avahi client is connecting to the server

When connected:

otbr-agent[18884]: [INFO]-MDNS----: Avahi client state changed to 2
otbr-agent[18884]: [INFO]-MDNS----: Avahi client is ready
otbr-agent[18884]: [INFO]-BA------: Publish meshcop service OpenThread BorderRouter #E3F0._meshcop._udp.local.
otbr-agent[18884]: [INFO]-MDNS----: Commit avahi service OpenThread BorderRouter #E3F0._meshcop._udp
otbr-agent[18884]: [INFO]-ADPROXY-: Publish all hosts and services

infra-if config is needed because the agent does perform some checks on it, before starting the router:

otbr-agent[16695]: [NOTE]-ILS-----: Infra link selected: wlan0
...
otbr-agent[16695]: 49d.18:33:22.314 [I] Platform------: Backbone interface is configured to wlan0 (3)
...
otbr-agent[16695]: [INFO]-APP-----: Thread Border Router started on AIL wlan0.

The agent runs in full operational mode, with backbone routing, ip forwarding, etc, even though most aren't needed. Because of that, the setup oneshot service as well as firewall-control and network-control interfaces are required too.

I'm not sure if there is a way to limit the agent to just activate DBus to RCP communication for the Matter app.

farshidtz added a commit that referenced this issue Apr 24, 2024
locnnil pushed a commit that referenced this issue May 2, 2024
* Add note on avahi-control interface requirement

Related to #19

* Editorial improvements to clarify steps
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants