Relaying some UDP traffic through tinc?

Guus Sliepen guus at tinc-vpn.org
Fri Apr 13 08:10:28 CEST 2018


On Thu, Apr 12, 2018 at 11:57:27PM +0200, Alex Corcoles wrote:

> I've got a four site site-to-site tinc mesh working nicely. I have the
> following systems at two of those sites:
> 
> 10.a.a.2: Linux box running tinc and DHCP/DNS for site A
> 10.a.a.dhcp: Windows desktop with a GPU
> 10.b.b.2: Linux box running tinc and DHCP/DNS for site B
> 10.b.b.dhcp: Linux laptop
> 
> I'd like to use Steam In-Home Streaming to game in the laptop streaming
> from the desktop. The Steam protocol is not well documented, but it
> seems to rely on UDP broadcasts to x.x.x.127 UDP port 27036 to discover
> remote nodes.

Tinc itself supports UDP broadcast packets. However, in router mode, it
will only treat 255.255.255.255/32 and 224.0.0.0/4 as broadcast address
ranges. If you are using tinc 1.1pre11 or later, you can add the
following to your tinc.conf files:

BroadcastSubnet = x.x.x.127

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180413/c50f7f79/attachment.sig>


More information about the tinc mailing list