On Mon, May 16, 2022 at 2:28 AM Janne Johansson <[email protected]> wrote: > While I can see the appeal of trying, it still means the service is > not really made to work for more than one client from that same NAT > pool. Might be fine if you aim for "bill and bob and jenny who works > from home" coming in from separate home broadband connections or > whatever, but it quickly breaks down for any larger cases than that. > It is rather uncommon for UDP services to make demands of the source > port and for them to have expectations about the ports, so when this > happens I think one needs to see and act on it right away, and that > would not happen if it "sometimes work" based on luck or timing or "I > was first into the office so I got todays slot at 08.01 to 08.02 > before the udp session times out in the fw".
You are correct, my use case is hosting UDP video game servers on a simple SOHO network. For any reasonably complex network you would have to deal with the NAT/UDP problem head on instead of relying on defaults.
