I’ll pass this request on to Florian.
Regarding Eth0 and Eth1. As you probably know, they are currently tied together on the same network.
The way I have mine configured is:
WiFi – DHCP Server BomeBoxSteve
Eth0-1 – Hardcoded IP address – However I have a cheap WiFI to Eth bridge attached. (I think I paid around $12 for it on Amazon). I don’t like stringing a cable across my studio.
That way I can get to my BomeBox via BomeNetwork over WiFi from my Windows PC at home (without having to change my local network configuration). Also I can optionally string a CAT5 cable to the other Eth port if I prefer.
If I’m away from home, I can access from my iPhone or Chromebook over the BomeBox Internal WiFI Connection.
I prefer this way as I never have to change my network settings on my BomeBox. I can even run on both interfaces concurrently.
I like the idea of a “share” for the project file location. Also, I believe Florian is working on more device routing options over the network. I specifically asked for the ability to expose individual attached MIDI devices over the BomeNet Connections. I didn’t ask about separate routing for different MIDI data types, such as clock, transport and notes, however I believe you can set up translators in a MT Project file to handle such routing. If you get more specific on a given routing scenario, I might be able to suggest something that would work. Of course, as you say, you would need to have your laptop to change the project and then upload the project file with that routing.
Bottom line is your suggestions make a lot of sense to me (as a user).