I don't know what your router's gonna do.
But I'm pretty sure when I coded with UDP streams lately, they MAY be using only one port to communicate, BUT only in a request/answer mode, not really full duplex.
If you have a host and multiple clients running in several windows on one desktop then you do HAVE TO use a diffrent port for client and host.
If host and client are on individual machines, the ports may be the same. It doesn't matter so much what ports you use, it's rather a question of who creates the stream. A firewall or router may block the creation of a stream from outside, even if you allow to send data over that port.
An easy solution would be to use a common port of a service that is rarely in use today. eg Telnet (port 23) or so. Common ports usually aren't blocked by routers.
But I'm pretty sure when I coded with UDP streams lately, they MAY be using only one port to communicate, BUT only in a request/answer mode, not really full duplex.
If you have a host and multiple clients running in several windows on one desktop then you do HAVE TO use a diffrent port for client and host.
If host and client are on individual machines, the ports may be the same. It doesn't matter so much what ports you use, it's rather a question of who creates the stream. A firewall or router may block the creation of a stream from outside, even if you allow to send data over that port.
An easy solution would be to use a common port of a service that is rarely in use today. eg Telnet (port 23) or so. Common ports usually aren't blocked by routers.