@tommyk mm is meant to be a closed system on the wall…
no one needs to access this, as its output only… SO
the default config says ONLY apps INSIDE this SAME machine can access the MM server
localhost is the name of the network connection (loop back)
now, it so happens one could add controls to limit JUST ONE (or a few) machines too…
this is the ipWhitelist
but as we’ve seen that (output only with no external access) doesn’t work for a number of use cases.
remote control, my mmm-config, …
SO, changing the config
address means listen for incoming requests on A network adapter, wifi OR ethernet…
address=“192.168.2.106” (for my desktop ethernet address)
but what if you have both? or more than one…
you can ONLY put ONE address there…
so there is a shortcut , “0.0.0.0”, means listen on ALL adapters, regardless their address…
now… i’ll just make an example, not implying anything…
you built this thing, and if ANYONE in your house could get in and fiddle with the MM parts, or others,
they might take the system down or something else…
kids that don’t know, but LOVE to explore…!!
how can i keep THEM out…
we I could limit access to ONLY MY phone, laptop,… then they couldn’t get in…
so you could put your phone and laptop ip addresses in the ipWhitelist:[] list
and then only YOU can get into the MM app system …
the RemoteControl readme, mentions this change in the config…