Stream across subnets?

[{TIA}-Zero-Cool]

Is there ever going to be a way to manually set the host address from the client so we can cross subnets with this? My home network topology (and many others who use both wired and wireless together) is devided into multiple subnets. im not willing to redesign my entire network topology for a video game, and i know for a fact im not the only one with this setup. seperating your wired and wireless network segments onto different subnets is networking 101.

there needs to be a manual setup option or a way to expand the scope of network discovery to inclube extra subnets. should be a simple tweak... i think they are worried people will use the service to share games across the internet and such but if they check for private ip scope like 10. or 192. that will kill any attempts to route over the internet...

[Lerkus]

That Solution implies, the use of an Mac-Broadcast from Steam...
Which is a K.O. for Solution with a normal router >.<

[M3TaBoLiC]

You could connect your sever computer to all the subnets that it will be streaming to using multiple network adapters.

[Borealid]

I have made this work with an OpenWRT router by using the "bcrelay" command to send broadcast traffic from one subnet to the other.

[ReBoot]

What's the reason to use different subnets? My home network is a conglomerate of Ethernet, WLAN and PLC, yet everything is in the same subnet. No trouble whatsoever

[MARPATdroid]

I have multiple subnets as well, mine is because I work from home as a contractor, and I specifically keep all of the connections to my client sites separate from my home network. I also segregate my traffic for the kids too, so when it's time for bed/homework/etc I can just disable thier access all at once, it's nice having a comercial set up but sometimes it can make things standout that you just wouldn't notice otherwise. It's not a common problem, but it would be nice to have a solution that allows it to work.

[DJDark]

Maybe your knowledge could give me some guidance. What could be the reason for my macbook not recognizing the PC I use for in-home streaming when it is on wifi instead of DSL cable? How could this make a difference on network level? Do you have any suggestions for directing me to the right kind of problem resolution forum or info?

{TIA}-DrPuff1nK1nd-(-NUGZ-) původně napsal:

conclusion: you lack education. so here... let me share a bit. subnetting eliminates broadcast traffic as well as isolating sensetive network resources from the more public network segments.
You may not have web servers (or game servers) on your home network, but i do. My network spans several buildings and several functions. It is in my best interests for a number of reasons to iscolate buildings and sensetive network resources from one another. this gives me the opton to throttle network traffic where necessary and to outright deny access on a packet by packet basis to any or all network resources. you may not require this level of control, but i do. please get even half a clue before you spout your baseless opinions all over the place. k?... thanks.

[{TIA}-Zero-Cool]

right off i would look at the ip addresses of the respective machines. I suspect you will find that they are on seperate subnets. Many networks isolate the wireless segment for the reasons i mentiond above. In order for them to see one another the first three sections of the address much match. so 1.2.3.4 must match 1.2.3.x where x can be any number. The actual values in each of these locations will be something else (192.168.x.x) most likely but maybe not. This does not matter as long as the first three numbers match. So it the mac is 192.168.1.x and the PC is 192.168.0.x (these are just examples), the machines will not see each other because the one address has a 1 in the location that the other has a 0. If this is not the problem then you likely have a firewall issue. try turning them both off and running it. cheers. hope that helps. :)

[DJDark]

Thanks man!

[adhocadhoc]

Steam please add an option manually input IP addresses. People been asking since like 2015 for this. Having to integrate a UDP packet forwarder just because a simple option is missing is outstanding. This is on both the Steamlink hardware and Samsung TV steamlink.

[MCP90]

In my case I've a router plus an AP connected to it via LAN and obviously everything on it is on a different subnet and the AP runs its own dhcp.

Since my router is modded with OpenWRT, I created a static route to connect the two subnets (only unicast works) and then on the access point (an arm mini pc with debian) I used bcrelay command to relay broadcasts between LAN and WiFi interfaces of the AP.

The problem is that now clients connected to the AP can see the Host PC but the streaming doesn't start giving the error "can't connect to the remote computer".

I'm sure I am missing something to make this work but I'll repeat this: Steam Link and Steam Link on android let you specify the IP and it works flawlessy this way! JUST ADD THE SAME ON DESKTOPS!

[adhocadhoc]

I was able to resolve this myself not long after I posted..I had to add a UDP broadcast forwarder on the router...so for anyone with Ubiquiti equipment check here >>

https://community.ubnt.com/t5/EdgeRouter/Multicast-Sonos-Phorus-amp-Play-Fi-Broadcast-255-255-255-255-lt/m-p/1268559/highlight/true#M67208

[Sir Warren<still alive>]

The Streaming Client supports the --server <IP Address> option, but Valve didn't provide us with an interface to change it :( It defaults to 255.255.255.255:27031 ... (and you can't start the streaming client manually, because it needs to receive open handles to some shared libraries)

iptables packet forwarding

What I did to circumvent this limitation, to use In-Home Streaming over VPN connection is to use iptables on the Linux client to force-forward the used ports to the target machine:

#!/bin/bash

ipaddr="10.0.0.42"

iptables -A OUTPUT -t nat -p udp --dport 27031 -d 255.255.255.255 -j DNAT --to-destination $ipaddr
iptables -A OUTPUT -t nat -p udp --dport 27036 -d 255.255.255.255 -j DNAT --to-destination $ipaddr
iptables -A OUTPUT -t nat -p tcp --dport 27036 -d 255.255.255.255 -j DNAT --to-destination $ipaddr
iptables -A OUTPUT -t nat -p tcp --dport 27037 -d 255.255.255.255 -j DNAT --to-destination $ipaddr

You must execute it as root (sudo ./steam-inhome-streaming-ports.sh). This will forcily forward all required In-Home streaming & discovery ports to the target machine $ipaddr.
I tried to do the same under Windows with the firewall, but it didn't work for me.

[lordlethris]

Start steam with:

Steam.exe -console

Then when steam load, tap the console menu that should appear and type:

connect_remote [Your Host IP:27036]

for example:

connect_remote 10.0.0.1:27036

voila, the In-Home Streaming should now connect.

[Hetorus NL]

lord_lethris původně napsal:

Start steam with:

Steam.exe -console

Then when steam load, tap the console menu that should appear and type:

connect_remote [Your Host IP:27036]

for example:

connect_remote 10.0.0.1:27036

voila, the In-Home Streaming should now connect.

AWESOME! @lord_lethris
This also works for me with a Windows host and Linux client, will post the OpenVPN configs later


Edit with the OpenVPN config files:

OpenVPN server config:

#!/bin/bash
# port and protocol information
port 1194
proto udp

# the interface used for the vpn [dev tap, dev tun]
dev tap
;dev tun  # default

# certificate configuration (CHANGE TO MATCH YOUR CERTIFICATES)
tls-server
ca ca.crt
cert server.crt
key server.key
dh dh2048.pem

# set the server mode, network topology and gateway to server dhcp
mode server  # default disabled, enable multi-client server
topology subnet  # default disabled
route-gateway dhcp

# configure the server mode and subnet
server 10.8.0.0 255.255.255.0

# enable clients to connect to each other
client-to-client

# ping every 10 seconds back and forth,
# assume disconnect after 120 seconds no ping
keepalive 10 120

# select a cryptographic cipher
cipher AES-256-CBC

# persist certain resources that may no longer
# be accessible because of privlege downgrade
persist-key
persist-tun

# log the current status and the default OpenVPN log
status openvpn-status.log
log openvpn.log

# log level verbosity [0-9]
verb 3

# notify clients of server restarts to automatically reconnect
explicit-exit-notify 1

# push some options to the clients that connect
push "topology subnet"
push "route-gateway dhcp"

OpenVPN client config:

#!/bin/bash
# we're a client, so pull some configs from the server.
client

# used for dhcp clients
float

# the interface used for the vpn [dev tap, dev tun]
dev tap
;dev tun

# the hostname and port of the server, and the protocol
remote CHANGEME 1194   # insert IP address or domain name here
proto udp

# keep trying to resolve the hostname of the server
resolv-retry infinite

# most clients don't need to bind to a local port
nobind

# Try to preserve some state across restarts.
persist-key
persist-tun

# certificate configuration
remote-cert-tls server
tls-client
ca ca.crt
cert CHANGEME.crt  # certificate generated for the client
key CHAMGEME.key  # key generated for the client

# verify that the server certificate has the correct key set
remote-cert-tls server

# select a cryptographic cipher
cipher AES-256-CBC

# Set log file verbosity.
verb 3

# redirect all trafic over the vpn
redirect-gateway def1

[purchases]

{TIA}-DrPuff1nK1nd-(-NUGZ-) původně napsal:

Is there ever going to be a way to manually set the host address from the client so we can cross subnets with this? My home network topology (and many others who use both wired and wireless together) is devided into multiple subnets. im not willing to redesign my entire network topology for a video game, and i know for a fact im not the only one with this setup. seperating your wired and wireless network segments onto different subnets is networking 101.

there needs to be a manual setup option or a way to expand the scope of network discovery to inclube extra subnets. should be a simple tweak... i think they are worried people will use the service to share games across the internet and such but if they check for private ip scope like 10. or 192. that will kill any attempts to route over the internet...

I would totally love this as well, as people more and more are setting up more sophisticated networks at home. BTW, love your response, OP. To the rest, please do get a clue before replying, or at least attempt to understand what an OP is trying to do before respond. This is pretty half-a** right now to depend on broadcast or some fancy service discovery when simple config would have done as well.