No connection between nodes on same LAN

Eric Estabrooks eric at urbanrage.com
Sun May 9 17:12:35 CEST 2010


On 05/09/10 07:09, Daniel Schall wrote:
>> Thanks for the diagram  -  what did you use to create it?
> 
> The diagram was made using Microsoft Visio 2007.
> 
>> First, what version of tinc are you using on your nodes  -  is it 1.0.13?
> 
> I am using tinc 1.013, the pre-compiled version from the website. All the
> nodes are running windows.
> 
>> A third option that might work is when doing PMTU discovery after
> exchanging
>> session keys between Node1 and Node2 (via their meta connections with
> Node3 of
>> course), that they also send some MTU probes to the broadcast address. The
>> receiving node will update the known address of the peer when it receives
> a
>> valid UDP packet, whereever it came from.
> 
>> I think the third option is easiest to implement, I don't know if it will
> work
>> though. I'm a little busy this month so if you or someone else wants to
> try to
>> implement it, please go ahead :)
> 
> I am curious to implement it, but I am also rather busy.
> Currently, I am studying the sources to evaluate, what to implement:
> a) a broadcast discovery algorithm to find all nodes in the same network
> segment OR
> b) making each node send its endpoints to all other nodes to let them choose
> what endpoint they want to contact the node
> 

I'd guess you'll have to go with option a.  Because even though their
ips may appear to put them on the same lan, it's not a guarantee that
they are and you might have one or more nodes that have them same
internal ip but are at different locations.


Eric

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5598 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20100509/a5f7fd66/attachment.bin>


More information about the tinc mailing list