Once again.Tinc for gaming

[Donald Pearson]

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.
On Jan 27, 2012 6:21 PM, "Leon Merten Lohse" <leon at green-side.de> wrote:

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