Port forwarding (specific ports?) #1698
Replies: 1 comment 4 replies
-
Hi, thanks for the feedback! :)
Haven't re-checked the code, but as far as I remember, Jamulus already tries to be deterministic about its source ports (which is rather uncommon, as source ports are often chosen completely dynamically). I assume that what you are seeing may be caused by some (most?) of your clients being behind NAT. Some NAT implementations may rewrite all source ports, some may only rewrite on conflicts (I don't know the actual details). So, the answer if you can influence this even more, would be No in practice, I suspect. I'm wondering about the Firewall thing though. It's common to run a firewall in servers, but it's uncommon (at least for me) to filter on source ports. What's the reason for doing that in your case? Wouldn't it be ok to allow many (or all) source ports? |
Beta Was this translation helpful? Give feedback.
-
I have setup a private Jamulus server for our mixed chorus and it works very fine. Thanks to you all! This is a great application!
Because the server (Windows, running on port 22124) is located behind a firewall I have to forward the "participants" including the UDP ports to the server. I read, that the portrange 22122 to 22125 should be unblocked. My experience is, that most of my "participants" come thru 22175, but one thru 23491 and others thru ... That means for me to unblock all ports to make sure everyone gets access. But this is not good, because to much "open".
My question: Is it possible to have control, thru which port the clients come in?
If you need more information pls. tell me.
Thank you
Herbert
Beta Was this translation helpful? Give feedback.
All reactions