Steam client version (build number or date): May 23, 2020
Distribution (e.g. Ubuntu): Arch Linux
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
I often use Steam Remote Play for playing games from a Windows streaming box to my Linux machine. However, my configuration is such that I have a Crossover Ethernet cable that connects the two systems directly, without going thru a router. Steam will establish a communication with the systems when they are both connected to the network via a router but will communicate via local IP rather than crossover. Both systems have separate Interfaces for connecting to the LAN and Internet.
The only way to force Steam to connect via crossover when both systems have a second, separate interface connected to the router and Internet, is to close steam on the Windows host side and disconnect from the LAN / Internet on the Linux client side (with Steam already opened and logged in) then once again open Steam on the Windows host side. I have to leave the Linux client side disconnected from the LAN until after I start a game stream via Remote Play then I can Alt-Tab out and reconnect to the Internet.
I've noticed that the new Steam beta client has a "Direct Connection IP Sharing" feature but it isn't what I was hoping it to be. I would like to be able to manually enter the IP address of the Crossover connected machine and Steam Remote Play to connect via that. For instance:
To have Remote Play connect via 169.254.xxx.xxx (Crossover) instead of 192.168.1.xx (LAN)
I often use Steam Remote Play for playing games from a Windows streaming box to my Linux machine. However, my configuration is such that I have a Crossover Ethernet cable that connects the two systems directly, without going thru a router. Steam will establish a communication with the systems when they are both connected to the network via a router but will communicate via local IP rather than crossover. Both systems have separate Interfaces for connecting to the LAN and Internet.
The only way to force Steam to connect via crossover when both systems have a second, separate interface connected to the router and Internet, is to close steam on the Windows host side and disconnect from the LAN / Internet on the Linux client side (with Steam already opened and logged in) then once again open Steam on the Windows host side. I have to leave the Linux client side disconnected from the LAN until after I start a game stream via Remote Play then I can Alt-Tab out and reconnect to the Internet.
I've noticed that the new Steam beta client has a "Direct Connection IP Sharing" feature but it isn't what I was hoping it to be. I would like to be able to manually enter the IP address of the Crossover connected machine and Steam Remote Play to connect via that. For instance:
To have Remote Play connect via 169.254.xxx.xxx (Crossover) instead of 192.168.1.xx (LAN)