<p>Bridge the tap device with the network interface. Run tinc in switched mode. All devices that will communicate need to be on the same subnet.</p>
<div class="gmail_quote">On Jan 27, 2012 6:21 PM, "Leon Merten Lohse" <<a href="mailto:leon@green-side.de">leon@green-side.de</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I still did not quite figure it out.<br>
So how exactly did you configure it?<br>
<br>
Lets assume Joe, Tim and Bob would like to play.<br>
<br>
Joe sets his LAN adapter to use 192.168.1/16? What about the tap device?<br>
Which mode do they use? I guess switch.<br>
<br>
Thanks for your help!<br>
<br>
Regards<br>
Leon<br>
<br>
<br>
Am 02.10.2011 16:52, schrieb Donald Pearson:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The method that I used to accomplish this with some buddies was with some<br>
non-standard subnetting.<br>
<br>
example:<br>
<br>
Joe configures his house to use <a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a><br>
Tim configures his house to use <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a><br>
Bob configures his house to use <a href="http://192.168.3.0/24" target="_blank">192.168.3.0/24</a><br>
<br>
All 3 individuals stand up Tinc in switched mode (there is no "subnet"<br>
setting for tinc when in switched mode).<br>
<br>
Now, any devices that you wish to participate in the VPN, you change their<br>
subnet mask from from 255.255.255.0 to 255.255.0.0 (/16 instead of /24). In<br>
that way the devices with the /16 subnet mask will consider any 192.168.x.x<br>
IP to be on the LAN, and Tinc will provide that switched fabric for them,<br>
making it work.<br>
<br>
Nothing else special needs to be done on anybody's network. Devices that<br>
you choose not to reconfigure with the new subnet mask, will still be able<br>
to communicate with your modified subnet mask devices.<br>
<br>
But there is one caveat. All broadcasts will make it across the VPN. I<br>
actually had problems where members of the VPN would pull DHCP address from<br>
*other members*. So Joe with his <a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> network would turn on his<br>
computer and when it requested DHCP, somehow Tim's router would respond<br>
faster, and Joe's computer would receive a 192.168.2.x address. So, any<br>
internet traffic from that computer would first traverse the VPN and exit to<br>
the internet via Tim's internet gateway.<br>
<br>
My ultimate solution to this that I liked very much was the "ebtables"<br>
package for linux. It's very much like IP tables but it works on frames at<br>
layer 2, and can therefore catch and drop dhcp traffic and any other traffic<br>
you may want to stop, such as UPnP requests from your friends poking holes<br>
in your firewall. :)<br>
<br>
On Sat, Oct 1, 2011 at 6:55 AM, Sich<<a href="mailto:sich@cafe-philo.net" target="_blank">sich@cafe-philo.net</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 30/09/2011 14:48, Leon Merten Lohse a écrit :<br>
<br>
Howdy,<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I would like to bring this topic up again. Gaming via tinc. We use<br>
tinc-1.0.16 on Linux, Win7 and WinXP so far.<br>
Setup was pretty straight forward. All the nodes have mode set to switch<br>
and subnet to <a href="http://10.0.0.0/24" target="_blank">10.0.0.0/24</a>.<br>
Ping works, smb shares work. Everything seems fine BUT connecting ingame<br>
only works with 1 out of 5 games.<br>
In some games, we see each other in the lobby. I conclude, that UDP<br>
broadcasts work. In some games only the Win7 machine sees the WinXP machine.<br>
But even then, most games crash, when we try to actually connect.<br>
<br>
I doubt this is a limitation of tinc. It's more likely to be a<br>
configuration problem, I guess.<br>
<br>
Any ideas?<br>
Thanks in advance.<br>
<br>
Regards<br>
Leon<br>
<br>
</blockquote>
<br>
Hello,<br>
<br>
In some games the broadcast is only send on one interface...<br>
If you want to use tinc for gaming you will need to have only 1 ethernet<br>
interface.<br>
For this you have to build a bridge between your local card and the tinc<br>
virtual card.<br>
<br>
With this you will have to setup all your local lan on the same network<br>
that the vpn (in your case <a href="http://10.0.0.0/24" target="_blank">10.0.0.0/24</a>).<br>
Take care on duplicate ip on all the network (your but the others to) and<br>
for dhcp server... The dhcp will go through the vpn, and your dhcp server<br>
can provide ip for people on other network.<br>
<br>
It's the only way I have found to be able to play on all games through LAN.<br>
<br>
Sich<br>
<br>
______________________________<u></u>**_________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="http://www.tinc-vpn.org/cgi-**bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-**<u></u>bin/mailman/listinfo/tinc</a><<a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http<u></u>://www.tinc-vpn.org/cgi-bin/<u></u>mailman/listinfo/tinc</a>><br>
<br>
</blockquote>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-<u></u>bin/mailman/listinfo/tinc</a><br>
</blockquote>
______________________________<u></u>_________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" target="_blank">http://www.tinc-vpn.org/cgi-<u></u>bin/mailman/listinfo/tinc</a><br>
</blockquote></div>