Thanks for your prompt response.
The intent of my post was to document the observation, and that you'd respond with helpful guidance, so thanks for that. I wasn't aware of the default behavior, but have come up to speed on the fact that the ARM image uses NetworkManager. It's not my preference, but that's not important.
The "why" is all about trouble shooting forked-daap. It is working fine, and fully accessible by my old Roku Soundbridge 1001, but I can't view it on Windows 10. I haven't found a Win10 client where it works (Have tried DAAP Media Client, VLC, Amarok, iTunes). In a VLC forum, there was a suggestion the problem is related to IPv6 running on the server and/or Win10, but still no luck. That's the issue I'm working through.
As for versions, noted.