search for: broadcastsubnet

Hi, 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

...; > 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> > > _______________________________________________ > tinc mailing list > tinc at tinc-vpn.org > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > &...

...erface link status accordingly. * Tinc now tells the resolver to reload /etc/resolv.conf when it receives SIGALRM. * Improved error messages and event loop handling on Windows. * LocalDiscovery now uses local address learned from other nodes, and is enabled by default. * Added a "BroadcastSubnet" option to change the behavior of broadcast packets in router mode. * Added support for dotted quad notation in IPv6 (e.g. ::1.2.3.4). * Improved format of printed Subnets, MAC and IPv6 addresses. * Added a "--batch" option to force the tinc CLI to run in non-interactive...

...erface link status accordingly. * Tinc now tells the resolver to reload /etc/resolv.conf when it receives SIGALRM. * Improved error messages and event loop handling on Windows. * LocalDiscovery now uses local address learned from other nodes, and is enabled by default. * Added a "BroadcastSubnet" option to change the behavior of broadcast packets in router mode. * Added support for dotted quad notation in IPv6 (e.g. ::1.2.3.4). * Improved format of printed Subnets, MAC and IPv6 addresses. * Added a "--batch" option to force the tinc CLI to run in non-interactive...

...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-...

Dear All, We are trying the Tinc invites to let nodes join the network. This is working as described but we want to push some configuration for some nodes but this seemed not to be working. What is working is the following invite: Name = test_invite NetName = test_VPN ConnectTo = test_hub01 Ifconfig = 172.16.1.4/24 Subnet = 172.16.1.4

...ports 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 > > -- ___ {~._.~} ( Y ) ()~*~() mail: alex at corcoles dot net (_)-(_) http://alex.corcoles.net/