# Music Assistant package – LAN/L2 networking limitation

**URL:** <https://community.start9.com/t/music-assistant-package-lan-l2-networking-limitation/5663>\
**Category:** StartOS Support\
**Tags:** diy\
**Created:** [August 29, 2026, 11:01am UTC](https://community.start9.com/t/music-assistant-package-lan-l2-networking-limitation/5663 "2026-08-29T11:01:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yan](https://community.start9.com/letter_avatar_proxy/v4/letter/y/3e96dc/32.png) [@yan](https://community.start9.com/u/yan)\
**Post date:** [August 29, 2026, 11:01am UTC](https://community.start9.com/t/music-assistant-package-lan-l2-networking-limitation/5663/1 "2026-08-29T11:01:02Z")

</div>

Hi,

I’m packaging **Music Assistant 2.10.1** for **StartOS 0.4.0.1**.

The package itself works: the service starts, the web UI is reachable, and the same image works correctly on the LAN outside StartOS.

The blocking point is LAN discovery/connectivity from the StartOS service container.

From the **Aeon host** , a multicast probe receives normal mDNS/SSDP replies:

```auto

```

```auto
Responders: 15

```

From the **Music Assistant container** , with the exact same probe:

```auto

```

```auto
Responders: 0

```

As a control, running the same Music Assistant image on another Debian machine with:

```auto

```

```auto
docker run --network host ...

```

immediately discovers both my **Denon AVR-1912** and **WiiM Mini** , and playback works.

So the remaining requirement is a **supported StartOS way to give this service direct LAN/L2 access** , or an equivalent supported mechanism for:

- mDNS / SSDP discovery
- direct player connectivity
- dynamic TCP/UDP ports used by protocols such as AirPlay

I’d prefer not to use a privileged LXC, broad firewall changes, or unsupported host-network workarounds.

Is there already a supported mechanism for this in StartOS 0.4, or is this currently a platform limitation?

I can provide the `.s9pk`, package source, and multicast probe if useful.

Thanks.

---

<div class="post-metadata">

**Author:** ![StuPleb](https://community.start9.com/user_avatar/community.start9.com/stupleb/32/195_2.png) [@StuPleb](https://community.start9.com/u/StuPleb)\
**Post date:** [August 29, 2026, 6:16pm UTC](https://community.start9.com/t/music-assistant-package-lan-l2-networking-limitation/5663/2 "2026-08-29T18:16:30Z")

</div>

Your diagnosis is right, and it’s a platform limitation rather than anything wrong with your package. Every StartOS service runs in a container on a NAT bridge, and there is currently no supported way to give a service L2/LAN presence — no host networking, no macvlan — and multicast (mDNS/SSDP) is not reflected between the LAN and the container network in either direction. That’s exactly why you see 0 responders inside the container and 15 on the host, and why upstream Music Assistant mandates host networking or macvlan for Docker installs.

What StartOS _can_ do today: fixed ports can be exposed raw (plain TCP, and TCP+UDP for port ranges) on the server’s LAN IP via the SDK (`secure: { ssl: false }` on a bind, or `bindPortRange`), and outbound connections from the container to LAN devices work. So a degraded-but-useful package may be possible: the web UI, plus players added by manual IP for the providers that support it (Google Cast, Sonos, HEOS, Sendspin) — provided Music Assistant can be configured to advertise the server’s LAN IP and a fixed stream port that the package forwards. If you test that combination I’d be very interested in the result. AirPlay, DLNA, and Squeezebox discovery rely on multicast or dynamically-negotiated ports and cannot work under the current model, and I’d steer you away from privileged-container hacks — they’ll fight the OS’s networking and break on update.

The real fix is a platform feature: opt-in LAN access for a service, granted by the user. These types of features, including various other types of hardware pass-through, are slated for future versions of StartOS.
