How to change standard port mapping?

[zexi]

The comment in this piece of code says that the default port is 47989. Is there some way to configure the port that the service listens on by default? Seems like sunshine has base port configuration and the other ports will offset automatically.
I tried to use Docker to make the following port mapping, but it didn't succeed.

docker run \                                                       
    -p 20001:47984/tcp \                                               
    -p 20006:47989/tcp \                                           
    -p 20016:47999/udp \                                           
    -p 20027:48010/tcp \                                           
    -p 20117-20127:48100-48110/udp \
    -p 20217-20227:48200-48210/udp 
....

I can add wolf server($hostip:20006) in moonlight client and pairing via http://$hostip:20006/pin/#xxxxxxxx.

But moonlight client shows connection refused after paired.

[Lombra]

Have you been able to change the ports in your Moonclight client accordingly?

[ABeltramo]

@zexi you are missing one tiny bit: after the initial HTTP/S pairing and app list Moonlight and Wolf will agree on a set of ports to be used later on and since Wolf doesn't know that you've mapped it to something else it'll send to Moonlight the default hardcoded ones.

Everything used to be hardcoded in Moonlight, so I just went with that back in the days, but I'll definitely make them configurable soon. There's already another PR that needed that too.

Just bear in mind that not every Moonlight client supports that. Only QT and Android have support for different ports, IIRC.

[zexi]

@zexi you are missing one tiny bit: after the initial HTTP/S pairing and app list Moonlight and Wolf will agree on a set of ports to be used later on and since Wolf doesn't know that you've mapped it to something else it'll send to Moonlight the default hardcoded ones.

@ABeltramo Thank you for the explanation.

Everything used to be hardcoded in Moonlight, so I just went with that back in the days, but I'll definitely make them configurable soon. There's already another PR that needed that too.

Looking forward to this PR merging soon.

Just bear in mind that not every Moonlight client supports that. Only QT and Android have support for different ports, IIRC.

OKay, got it.

[ABeltramo]

I've just pushed a potential fix for this in #191
You can set the ports via the following env variables:

• WOLF_HTTP_PORT (default 47989)
• WOLF_HTTPS_PORT (default 47984)
• WOLF_CONTROL_PORT (default 47999)
• WOLF_RTSP_SETUP_PORT (default 48010)
• WOLF_VIDEO_PING_PORT (default 48100)
• WOLF_AUDIO_PING_PORT (default 48200)

Plus, it wouldn't be required to open multiple ports for audio/video; a single port open can support multiple clients!

It would be nice if you could test it out and report if that works for you too. You can pull the image by using

ghcr.io/games-on-whales/wolf:dev-moonlight-fixes

[zexi]

I've just pushed a potential fix for this in #191 You can set the ports via the following env variables:

• WOLF_HTTP_PORT (default 47989)
• WOLF_HTTPS_PORT (default 47984)
• WOLF_CONTROL_PORT (default 47999)
• WOLF_RTSP_SETUP_PORT (default 48010)
• WOLF_VIDEO_PING_PORT (default 48100)
• WOLF_AUDIO_PING_PORT (default 48200)

Plus, it wouldn't be required to open multiple ports for audio/video; a single port open can support multiple clients!

It would be nice if you could test it out and report if that works for you too. You can pull the image by using

ghcr.io/games-on-whales/wolf:dev-moonlight-fixes

@ABeltramo The following error occurred when running this image, but not knowning which port is used.

03:26:18.557679211 ERROR | Unhandled exception: bind: Address already in use [system:98 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:161:33 in function 'boost::system::error_code boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>::bind(implementation_type &, const endpoint_type &, boost::system::error_code &) [Protocol = boost::asio::ip::tcp]']

In addition, I have checked using netstat, and none of these ports are occupied by other processes.

This is my Docker startup script:

#!/bin/bash

sudo nvidia-container-cli --load-kmods info

docker rm wolf

HTTPS_PORT=20000

HTTP_PORT=$((HTTPS_PORT+5))
CONTROL_PORT=$((HTTPS_PORT+15)) # udp
VIDEO_PING_PORT=$((HTTPS_PORT+116)) # udp
AUDIO_PING_PORT=$((HTTPS_PORT+216)) # udp
RTSP_SETUP_PORT=$((HTTPS_PORT+26))

docker run \
    --name wolf \
    -p $HTTPS_PORT:$HTTPS_PORT \
    -p $HTTP_PORT:$HTTP_PORT \
    -p $CONTROL_PORT:$CONTROL_PORT/udp \
    -p $VIDEO_PING_PORT:$VIDEO_PING_PORT/udp \
    -p $AUDIO_PING_PORT:$AUDIO_PING_PORT/udp \
    -p $RTSP_SETUP_PORT:$RTSP_SETUP_PORT \
    -e XDG_RUNTIME_DIR=/tmp/sockets \
    -v /tmp/sockets:/tmp/sockets:rw \
    -e WOLF_HTTP_PORT=$HTTP_PORT \
    -e WOLF_HTTPS_PORT=$HTTPS_PORT \
    -e WOLF_CONTROL_PORT=$CONTROL_PORT \
    -e WOLF_RTSP_SETUP_PORT=$RTSP_SETUP_PORT \
    -e WOLF_VIDEO_PING_PORT=$VIDEO_PING_PORT \
    -e WOLF_AUDIO_PING_PORT=$AUDIO_PING_PORT \
    -e NVIDIA_DRIVER_VOLUME_NAME=nvidia-driver-vol \
    -v nvidia-driver-vol:/usr/nvidia:rw \
    -e HOST_APPS_STATE_FOLDER=/etc/wolf-$HTTPS_PORT \
    -v /etc/wolf-$HTTPS_PORT:/etc/wolf-$HTTPS_PORT:rw \
    -v /var/run/docker.sock:/var/run/docker.sock:rw \
    --device /dev/nvidia-uvm \
    --device /dev/nvidia-uvm-tools \
    --device /dev/dri/ \
    --device /dev/nvidia-caps/nvidia-cap1 \
    --device /dev/nvidia-caps/nvidia-cap2 \
    --device /dev/nvidiactl \
    --device /dev/nvidia0 \
    --device /dev/nvidia-modeset \
    --device /dev/uinput \
    --device /dev/uhid \
    -v /dev/:/dev/:rw \
    -v /run/udev:/run/udev:rw \
    --device-cgroup-rule "c 13:* rmw" \
    ghcr.io/games-on-whales/wolf:dev-moonlight-fixes

[zexi]

03:26:18.557679211 ERROR | Unhandled exception: bind: Address already in use [system:98 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:161:33 in function 'boost::system::error_code boost::asio::detail::reactive_socket_serviceboost::asio::ip::tcp::bind(implementation_type &, const endpoint_type &, boost::system::error_code &) [Protocol = boost::asio::ip::tcp]']

@ABeltramo The error is caused by the WOLF_HTTP_PORT environment variable. For the specific reason, please refer to this #191 (comment) .

[ABeltramo]

@zexi sorry about that, I should've tested the changes. Thanks for looking thru the code and point out the issues, I should've fixed everything now. I've managed to get a Moonlight session going with the custom ports and env variables that you've posted above.

[zexi]

@ABeltramo Thanks your fixes. I've pulled the image ghcr.io/games-on-whales/wolf:dev-moonlight-fixes again and tested with moonlight. But the video and audio stream are not recevied when I open 'Firefox' or 'Test ball' app.

The following are the logs of Wolf and Moonlight:

• Wolf log: 07:26:34.551238288 DEBUG | UDP Socket is not open

07:26:32.698490041 DEBUG | Starting video pipeline:
interpipesrc listen-to=18046928878093460462_video is-live=true stream-sync=restart-ts max-buffers=1 block=false !
queue leaky=downstream max-size-buffers=1 !
cudaupload !
cudaconvertscale !
video/x-raw(memory:CUDAMemory), width=1920, height=1080, chroma-site=mpeg2, format=NV12, colorimetry=bt601, pixel-aspect-ratio=1/1 !
nvh265enc gop-size=-1 bitrate=15308 aud=false rc-mode=cbr zerolatency=true preset=p1 tune=ultra-low-latency multi-pass=two-pass-quarter !
h265parse !
video/x-h265, profile=main, stream-format=byte-stream !
rtpmoonlightpay_video name=moonlight_pay payload_size=1392 fec_percentage=20 min_required_fec_packets=2 !
appsink name=wolf_udp_sink
07:26:32.768873305 DEBUG | Setting up wolf_udp_sink
0:00:15.820645475     1 0x7f82440016d0 WARN        cudaconvertscale gstcudaconvertscale.c:1399:gst_cuda_base_convert_set_info:<cudaconvertscale3> Can't calculate borders
0:00:15.820694399     1 0x7f82440016d0 WARN           cudaconverter gstcudaconverter.c:2104:gst_cuda_converter_setup:<cudaconverter0> Couldn't compile to cubin, trying ptx
07:26:32.816282678 INFO  | [DOCKER] Starting container: /WolfFirefox_18046928878093460462
07:26:32.816327806 DEBUG | [DOCKER] Starting container: {
 id: 6d53dc7c9f8e304d80d8b38ca2f6e25abc80fb391673a37f60ecbe40a0343500
 name: /WolfFirefox_18046928878093460462
 image: ghcr.io/games-on-whales/firefox:edge
 status: 0
 ports: []
 mounts: [/tmp/sockets/pulse-socket:/tmp/sockets/pulse-socket:rw, /tmp/sockets/wayland-1:/tmp/sockets/wayland-1:rw, /etc/wolf-20000/18046928878093460462/Firefox:/home/retro:rw, nvidia-driver-vol:/usr/nvidia:rw, /etc/wolf-20000/18046928878093460462/Firefox/udev:/run/udev/:rw, /etc/wolf-20000/fake-udev:/usr/bin/fake-udev:ro]
 devices: [/dev/dri/card0:/dev/dri/card0:mrw, /dev/dri/renderD128:/dev/dri/renderD128:mrw, /dev/dri/card0:/dev/dri/card0:mrw, /dev/nvidia0:/dev/nvidia0:mrw, /dev/nvidia-modeset:/dev/nvidia-modeset:mrw, /dev/nvidia-uvm:/dev/nvidia-uvm:mrw, /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools:mrw, /dev/nvidiactl:/dev/nvidiactl:mrw]
 env: ["RUN_SWAY=1", "MOZ_ENABLE_WAYLAND=1", "GOW_REQUIRED_DEVICES=/dev/input/* /dev/dri/* /dev/nvidia*", "PULSE_SOURCE=virtual_sink_18046928878093460462.monitor", "GAMESCOPE_REFRESH=60", "PUID=1000", "PULSE_SINK=virtual_sink_18046928878093460462", "WAYLAND_DISPLAY=wayland-1", "GAMESCOPE_HEIGHT=1080", "PGID=1000", "PULSE_SERVER=/tmp/sockets/pulse-socket", "XDG_RUNTIME_DIR=/tmp/sockets", "GAMESCOPE_WIDTH=1920", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "UMASK=000", "UNAME=retro", "HOME=/home/retro", "TZ=Europe/London", "DEBIAN_FRONTEND=noninteractive", "NEEDRESTART_SUSPEND=1", "GAMESCOPE_VERSION=3.15.14", "BUILD_ARCHITECTURE=amd64", "DEB_BUILD_OPTIONS=noddebs"]
}
07:26:33.124327956 DEBUG | Starting audio pipeline:
interpipesrc listen-to=18046928878093460462_audio is-live=true stream-sync=restart-ts max-bytes=0 max-buffers=3 block=false !
queue max-size-buffers=3 leaky=downstream ! audiorate ! audioconvert !
opusenc bitrate=96000 bitrate-type=cbr frame-size=5 bandwidth=fullband audio-type=restricted-lowdelay max-payload-size=1400 !
rtpmoonlightpay_audio name=moonlight_pay packet_duration=5 encrypt=true aes_key="bcc7f467f498a06c343d43eb3584bdd2" aes_iv="915527054" !
appsink name=wolf_udp_sink
07:26:33.127988805 DEBUG | Setting up wolf_udp_sink
0:00:17.602284589     1 0x7f8244001f40 WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc1> segment format mismatched, ignore
07:26:34.551238288 DEBUG | UDP Socket is not open
07:26:35.304028372 DEBUG | [GSTREAMER] Forcing IDR
07:26:43.737962290 DEBUG | [ENET] disconnected client: 192.168.204.223:11214
07:26:43.738031533 DEBUG | [GSTREAMER] Pausing pipeline: 18046928878093460462
07:26:43.738070793 DEBUG | [GSTREAMER] Pausing pipeline: 18046928878093460462

• Moonlight log:

00:00:29 - SDL Info (0): Dropping window event during flush: 6 (1920 1080)
00:00:29 - SDL Info (0): IDR frame request sent
00:00:31 - Qt Info: Discord integration ready for user: lzx0325
00:00:37 - SDL Info (0): Terminating connection due to lack of video traffic
00:00:37 - SDL Info (0): UDP port 47998 test successful
00:00:37 - SDL Info (0): UDP port 48000 test successful
00:00:37 - SDL Error (0): Connection terminated: -100
00:00:37 - Qt Critical: No video received from host. 

Check your firewall and port forwarding rules for port(s): UDP 47998, UDP 48000
00:00:37 - SDL Info (0): Quit event received
00:00:37 - SDL Info (0): Stopping input stream...
00:00:37 - SDL Info (0): done
00:00:37 - SDL Info (0): Stopping audio stream...
00:00:37 - SDL Info (0): No audio traffic was ever received from the host!
00:00:37 - Qt Info: Found "gamecontrollerdb.txt" at "/Users/lzx/Library/Caches/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt"
00:00:37 - SDL Info (0): Loaded 155 new gamepad mappings
00:00:37 - SDL Info (0): ENet wait interrupted
00:00:37 - SDL Info (0): Control stream connection failed: 4
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Stopping video stream...
00:00:38 - SDL Info (0): No video traffic was ever received from the host!
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Stopping control stream...
00:00:38 - SDL Info (0): ENet peer acknowledged disconnection
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Cleaning up input stream...
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Cleaning up video stream...
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Cleaning up control stream...
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Cleaning up audio stream...
00:00:38 - SDL Info (0): done
00:00:38 - SDL Info (0): Cleaning up platform...
00:00:38 - SDL Info (0): done

[ABeltramo]

@zexi I can't reproduce your issue, I've tried running Wolf with a variation of your script:

#!/bin/bash

docker rm wolf

HTTPS_PORT=20000

HTTP_PORT=$((HTTPS_PORT+5))
CONTROL_PORT=$((HTTPS_PORT+15)) # udp
VIDEO_PING_PORT=$((HTTPS_PORT+116)) # udp
AUDIO_PING_PORT=$((HTTPS_PORT+216)) # udp
RTSP_SETUP_PORT=$((HTTPS_PORT+26))

docker run \
    --name wolf \
    -p $HTTPS_PORT:$HTTPS_PORT \
    -p $HTTP_PORT:$HTTP_PORT \
    -p $CONTROL_PORT:$CONTROL_PORT/udp \
    -p $VIDEO_PING_PORT:$VIDEO_PING_PORT/udp \
    -p $AUDIO_PING_PORT:$AUDIO_PING_PORT/udp \
    -p $RTSP_SETUP_PORT:$RTSP_SETUP_PORT \
    -e XDG_RUNTIME_DIR=/tmp/sockets \
    -v /tmp/sockets:/tmp/sockets:rw \
    -e WOLF_HTTP_PORT=$HTTP_PORT \
    -e WOLF_HTTPS_PORT=$HTTPS_PORT \
    -e WOLF_CONTROL_PORT=$CONTROL_PORT \
    -e WOLF_RTSP_SETUP_PORT=$RTSP_SETUP_PORT \
    -e WOLF_VIDEO_PING_PORT=$VIDEO_PING_PORT \
    -e WOLF_AUDIO_PING_PORT=$AUDIO_PING_PORT \
    -v /etc/wolf:/etc/wolf:rw \
    -v /var/run/docker.sock:/var/run/docker.sock:rw \
    -v /dev/:/dev/:rw \
    -v /run/udev:/run/udev:rw \
    --gpus=all \
    -e NVIDIA_DRIVER_CAPABILITIES=all \
    -e NVIDIA_VISIBLE_DEVICES=all \
    --device /dev/dri/ \
    --device /dev/uinput \
    --device /dev/uhid \
    --device-cgroup-rule "c 13:* rmw" \
    ghcr.io/games-on-whales/wolf:dev-moonlight-fixes

and I can definitely, connect via Moonlight QT on OSX.
Is this over LAN or WAN? Could it be that you haven't opened the ports? Some firewall in between?
Do you have by any chance Sunshine running on the same machine too? Have you tried using the standard ports first just to make sure that it's not firewall/network related?

[zexi]

Is this over LAN or WAN? Could it be that you haven't opened the ports? Some firewall in between?
Do you have by any chance Sunshine running on the same machine too? Have you tried using the standard ports first just to make sure that it's not firewall/network related?

@ABeltramo Thanks for the troubleshooting steps. I tested the version ghcr.io/games-on-whales/wolf:stable and ghcr.io/games-on-whales/wolf:dev-moonlight-fixes in same network.

• In same LAN with no NAT network: both version are working.
• In same network with NAT:
  • stable version is working and can recevice stream.
  • dev-moonlight-fixes is not working and the moonlight client doesn't receive the video and audio stream.

[ABeltramo]

Can you elaborate a bit more on what you mean with In same network with NAT? I need to find a way to replicate your issue..
If you pass the env variables to change the ports dev-moonlight-fixes will switch to those ports whilst stable will keep using the hardcoded ones, are you sure you have opened them in your network?

[salty2011]

Hey @zexi

Might need more context on the Same network with NAT scenario. When you say same network but with NAT, what are you meaning

• is client and server on the same network
• is the client on external network and you have forwarded ports from external to internal where server is
• what kind of NAT, is this a CGNAT ( many internet providers use cgnat these days)

Just reading your previous statement on face value indicates both client and server are on the same network so NAT wouldn’t be involved. Given your having issues I’m guessing there not the same network.

Are you able to repeat the steps and upload the logs?

[zexi]

@ABeltramo @salty2011 Thanks for the support.

Now, there is no problem with pulling the latest version of the ghcr.io/games-on-whales/wolf:dev-moonlight-fixes image. Perhaps the commits c0ccf73 and 3913fde have fixed this issue?

• In same network with NAT means using stable and dev-moonlight-fixes version of wolf and connecting by moonlight client.
  • Net1: 192.168.6.0/24 gateway 192.168.6.254
  • Net2: 192.168.167.0/24 gateway 192.168.167.254
  • Wolf server's IP is 192.168.6.60 in Net1
  • Moonlight client is 192.168.167.20 in Net2
  • Both Net1 and Net2 are a wireless router. Net2 is connected to the LAN port of Net1 through its WAN port. Therefore, when the client access the server of Net1 from Net2, NAT will be performed.