Request auto-connect network-observe for couch-remote

store-requests privileged-interfaces
1 
I'm the publisher of **couch-remote** (strictly confined, published to the global store: https://snapcraft.io/couch-remote). I'd like to request **auto-connection of the `network-observe` interface**.

**Why it's needed**
The app provides Wake-on-LAN to power a TV on. To send the magic packet it needs the TV's network MAC address. mDNS discovery (`_androidtvremote2._tcp`) advertises the device name, IP and port but **not** the MAC, so after discovering the device on the LAN the app reads `/proc/net/arp` to obtain it — which requires `network-observe`. Without auto-connect, users have to run `snap connect couch-remote:network-observe` or type the MAC by hand, which defeats the feature.

**Scope of use**
Read-only: the app only maps an already-discovered device IP to its MAC address from the ARP table. It never modifies network configuration. The snap otherwise plugs only `network` and `network-bind`.

**Verified on device**
With the interface connected, the app correctly reads the TV's MAC from the ARP table; the feature degrades gracefully (the MAC is simply left empty) when the interface is not connected.

Thanks for considering.
2

This request has been added to the queue for review by the @reviewers team.

3

Hello @WwWuengy!

This is a +1 from me for granting auto-connect to the network-observe interface for the snap couch-remote given the necessary functionality described.

1 Like
4

+1 from me as well to grant auto-connection of network-observe interface.

1 Like
5

I really appreciate it :folded_hands:

1 Like
6

Thank you for the trust :folded_hands:

7

+2 votes for, 0 votes against, granting auto-connect of interface network-observe to snap couch-remote. This is now live.

1 Like