Issues with UDP on Machines/AppsV2

[Brandon15811]

Hey kwaw,

Thanks for the explanation, I was doing experiments to see if I could route by port, but the way you explained that it works makes more sense. The routing fix that was applied earlier should be good enough for my use case.

I do have one more question: if I set up multiple machines on the same app in the same region, and give them each a unique port, will it route to the specific machine based on the port, or will it load balance between them regardless of the port?

I did find a reference to UDP port routing here, but I wanted to make sure that was still the case:

Dedicated IP Billing

You can make that happen if you spawn machines manually. You can delegate each machine to listen to one specific port. Do remember that for UDP on Fly you have to listen on the same port you’re exposing for each machine. So maybe this is how’d do: Create a machines app Add a dedicated IPv4 Spawn each server on a machine listening to their own port. Your users would use you-domain.com:machine-port to connect Does that sound like a good enough approach for WebRTC?