Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Moonlight rejecting stream when running with multiple IPs #116

Open
ABeltramo opened this issue Sep 4, 2024 · 0 comments
Open

Fix Moonlight rejecting stream when running with multiple IPs #116

ABeltramo opened this issue Sep 4, 2024 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@ABeltramo
Copy link
Member

This has been reported in Discord, the short version is as follows:

  • LAN IP: 192.168.1.X
  • Wireguard IP: 172.17.0.Y

Moonlight was reaching Wolf via 192.168 and Wolf was sending back the video and audio stream over 172.17, as a security measure Moonlight will reject that because it comes from an unknown IP.

Snippet from the logs:

DEBUG | 172.17.0.2 [GET] HTTPS://192.168.1.20/appasset
DEBUG | 172.17.0.2 [GET] HTTPS://192.168.1.20/serverinfo
DEBUG | 172.17.0.2 [GET] HTTPS://192.168.1.20/launch
...
DEBUG | Starting video pipeline: 
...
udpsink bind-port=48100 host=172.17.0.2 port=51928 sync=true

Manually setting the env variable WOLF_INTERNAL_IP fixes it but I think we can do better here and automatically match the IP from the HTTPS endpoints when setting our IP for the Moonlight session.

@ABeltramo ABeltramo added bug Something isn't working enhancement New feature or request labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant