Hi!
I'm working on a permanent sound installation in a building. A computer will run a Linux distribution and PD. We want to control the patch remotely, ideally over Internet, at least over local network. The control will be pretty simple: some sliders, bangs and toggles, values. We obviously need a feedback.
The IP of the building will probably be static so we can access the computer, but we want to access it from dynamic IP anywhere.

I found some clues about how to do that, but I'm not sure what is the best solution for our needs:
-webPD: https://github.com/sebpiq/WebPd. The patch and the remote computer access the same server, maybe on localhost in the building
-[netsend] [netreceive]: but I guess we need a relay, and I don't know how...
-other??

thank you!

@rph-r I don't know WebPd and will let others advise you on the networking issues, but you could easily make a remote UI for your installation patch using netsend/netreceive because by default they support Pd list messages:
server and remote.zip

@rph-r For a local network it is easy.
Using @Jameslo's example above you would [connect 192.168.1.50 8000( of course replacing the IP with that of your installation computer.
You should always give your computers a static address in this situation.

Also your remote computer will have no problems accessing an already existing server on the remote IP if it is listening for access requests.

But you can access the installation computer directly from your remote computer if the router in the installation building is set to allow a "hole" to be punched through its firewall and the port to be re-routed to your installation computer.
That is not so difficult to set up, but they would need to allow you to change their router settings.
David.

thank you both,
I can manage with them to allow a port for that, but then can I receive datas from the installation computer even if my IP changes?
e.g. I could send my IP to the patch?

@rph-r You can use [netreceive] in the installation patch.
Then use [netsend] in your remote patch.
Once your remote patch is connected you will be able to receive messages back from the installation through those same objects (see the help files).

If you use a tcp connection in [netsend] and [netreceive] then the left outlet of [netsend] indicates whether it connected (the value will change from one to zero when you try to send a message if the connection has been lost).
That is because the TCP protocol needs an acknowledgement packet sent back, or it will send the packet again..... and again until it times out. UDP will not do that.

If you need an "alarm" that the connection has been lost, or that the installation patch has stopped sending messages, then add a [metro] sending a ping back to [netsend] from the [netreceive] in your installation patch.

Then you could set up an auto reconnect in your remote patch.
You can only "find" another computer on the net if its IP has changed by using DNS lookup, and if an address changes it can take up to 2 days for all the worlds DNS servers to be updated.
Maybe something like DynDns is quicker, but if you are instigating the connection using your controller (remote) computer then you don't need that anyway.

You will always be able to reach the installation computer from any internet address.
David.

P.S. of course you can set up and test on your local network before implementation.

It sound's wonderful, I'll try that these days, I'll tell you how it goes...
thank you!

Check also AOO
Audio over Internet but also messaging (check pipelines section https://git.iem.at/cm/aoo/-/pipelines). It uses a public server for connection between peers.
https://git.iem.at/cm/aoo