switch-lan-play icon indicating copy to clipboard operation
switch-lan-play copied to clipboard

Allow using a server link without a port

Open FaserF opened this issue 4 years ago • 6 comments

Thank you for your work. Please allow in the clients the usage without a server port.

Background. I have a subdomain switch.mydomain.com with a Proxy behind it. The proxy sends the web page to my docker switch lan play server to the correct port (11451).

So I would like to tell the client to use switch.mydomain.com as my server url, but it fails and stops with an error that the IP couldn't be parsed.

FaserF avatar Jul 21 '21 08:07 FaserF

switch lan play uses both TCP and UDP on the same port number. (TCP/HTTP for query infomation, UDP for gaming data, the client only uses UDP). And UDP is not a part of web page you mentioned. Not sure what exactly you want.

spacemeowx2 avatar Jul 21 '21 09:07 spacemeowx2

I think you might want the user to omit the port part :11451. So when no colon is detected switch lan play will connect to the default port 11451. This is a good suggestion.

spacemeowx2 avatar Jul 21 '21 09:07 spacemeowx2

My LAN-Play Server runs within my network. I have enabled port forwarding for 11451 on UDP and TCP on my router. for my subdomain switch.mydomain.com I have set up a proxy redirection, means that when I access switch.smartlife.tk it automatically gets redirected to my local IP 192.168.1.2 and the port 11451. I can successfully access the LAN Page Info page with switch.smartlife.tk/info

But I am unable to tell the lan play client to just use this domain, it forces me to enter a port number. On Windows the Client just force closes when entering no port, on linux (raspberrypi) i can see the following:

[ERROR]: Failed to parse and get ip address. --relay-server-addr: switch.smartlife.tk

If it is technically not possible because of your first explanation, then its fine, I just thought that this should be doable.

FaserF avatar Jul 21 '21 09:07 FaserF

@FaserF it could be because you also have ipv6, dns prefers ipv6 over ipv4, so when you use the fqdn, it's trying to connect to the ipv6 which the client doesn't support. Since there's 0 support for v6 at this time, there's no method to specify using the ipv4 ip. The only other potential option would be to put ONLY the ipv4 in your /etc/hosts (or windows hosts) and it will stop looking up the ipv6

drizuid avatar Aug 28 '21 00:08 drizuid

I‘ve got an ipv4 Adress (only) unfortunately :/ So this should not be the issue

FaserF avatar Aug 28 '21 11:08 FaserF

I‘ve got an ipv4 Adress (only) unfortunately :/ So this should not be the issue

not according to the DNS lookup.

Non-authoritative answer:
Name:    switch.smartlife.tk
Addresses:  2606:4700:3030::6815:5def
          2606:4700:3031::ac43:d8b3
          104.21.93.239
          172.67.216.179

based on the above, it is likely precisely what i stated

drizuid avatar Aug 30 '21 14:08 drizuid