There seems to be some confusion about the number of UDP ports required for JK. Some of the comments in this forum suggest that 10 ports are required while documentation I have from JK themselves indicated that just 2 UDP ports are needed.
UDP ports required...
|
05-12-2020, 06:13 PM
(05-12-2020, 04:18 PM)StuartR Wrote: There seems to be some confusion about the number of UDP ports required for JK. Some of the comments in this forum suggest that 10 ports are required while documentation I have from JK themselves indicated that just 2 UDP ports are needed.>>> The networking section of the client states 10 (11 actually) ports are to be opened. However, after starting the client I've never seen anymore than 5 consecutive ports bound to the service. You can specify any port you like, but we recommend an even number in the range including 1026-49150 to avoid conflicts with other programs. When configuring Port Forwarding in your router, be sure to open this port along with the next 10. For example, if this field is 12000, then in your router, forward ports 12000-12010 to your computer's IP address.
06-05-2020, 01:08 PM
(05-12-2020, 06:13 PM)Dimitri Muskens Wrote:Hi Dimitri, Do you know if I can safely use ports 12011-12021 on my second device? Thank you(05-12-2020, 04:18 PM)StuartR Wrote: There seems to be some confusion about the number of UDP ports required for JK. Some of the comments in this forum suggest that 10 ports are required while documentation I have from JK themselves indicated that just 2 UDP ports are needed.>>>
06-05-2020, 01:50 PM
For what it's worth, I've been using range: 12000 - 12010. I believe this is the Default, specified in the client - thought the client can be changed. I sometimes run the session on different devices.
This comment i found confusing at first. "recommend an even number in the range including 1026-49150". I much preferred to know only the favorable ports for JamKazam. Why i went with the default. The second device question is interesting since most of the time we run one session at a time, unless you have multiple accounts and running multiple JK's in the same LAN. I suspect you would have to configure unique UDP ranges for each device. Otherwise if you are using only one device at a time, it would be separate UDP forwards in your router, pointing to the respective static IP for the device.
06-05-2020, 03:24 PM
You are correct - for every JK client device, there needs to be a unique IP address and a unique range of ports pointed to each address.
I have selected 12020 ~ 12030 just to be contrary. Seems to work fine
06-05-2020, 03:39 PM
06-05-2020, 03:40 PM
(This post was last modified: 06-05-2020, 05:14 PM by Dimitri Muskens.)
>>>
Just FYI. The portrange 12### as mentioned as an example in the client and on the interwebs in relation to JKZ is NOT set in stone and NOT default. When using JKZ without PF and just let UPnP handle the traffic you'll notice that the ports captured by JKZ are most of the time somewhere in the 50### and 60### ranges. E.g., on my system I see a lot of 54000 - + & up. Never anywhere near 12000 or over.
06-05-2020, 04:47 PM
This is from the UPnP port forwarding table in my router:
JamKazam_at_54538[UDP/54538~54538] 192.168.1.226 Enabled JamKazam_at_54539[UDP/54539~54539] 192.168.1.226 Enabled JamKazam_at_54540[UDP/54540~54540] 192.168.1.226 Enabled Makes sense because IANA does allow ports below 49151 to be registered. Everything above is considered "ephemeral" and cannot be registered. |
Users browsing this thread: 2 Guest(s)