search for: option_indirect

Displaying 4 results from an estimated 4 matches for "option_indirect".

2010 Sep 17
1
friend of a friend type darknets
...2010-04-11 04:34:31.000000000 +0200 +++ tinc-1.0.13-patched/src/net_setup.c 2010-09-17 23:38:05.591481035 +0200 @@ -337,6 +337,10 @@ /* Check some options */ + get_config_bool(lookup_config(config_tree, "FriendOfAFriend"), &foaf); + if(foaf) + myself->options |= OPTION_INDIRECT; + if(get_config_bool(lookup_config(config_tree, "IndirectData"), &choice) && choice) myself->options |= OPTION_INDIRECT; diff -Nur tinc-1.0.13/src/protocol.c tinc-1.0.13-patched/src/protocol.c --- tinc-1.0.13/src/protocol.c 2010-03-13 18:53:33.000000000 +010...
2019 Sep 12
0
Details on tinc's meta protocol
...C. Question: does A also attempt to open a meta connection to C? If not how can it check that the packets to C arrive to destination? More generally I am interested in understanding how 'indirect' connections work in tinc. For instance I see in `protocol_auth.c` that TCPOnly implies 'OPTION_INDIRECT' (as documented in the doc), but it seems (according to the docs) like tinc can still try to send data via the TCP meta connection? Thanks in advance! Damien Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc-devel...
2008 Sep 30
1
Problem compiling tinc-1.0.8 on gcc-2.95
...; + myself->status.st.visited = true; + myself->status.st.indirect = false; myself->nexthop = myself; myself->via = myself; list_insert_head(todo_list, myself); @@ -213,15 +213,15 @@ of nodes behind it. */ - indirect = n->status.indirect || e->options & OPTION_INDIRECT + indirect = n->status.st.indirect || e->options & OPTION_INDIRECT || ((n != myself) && sockaddrcmp(&n->address, &e->reverse->address)); - if(e->to->status.visited - && (!e->to->status.indirect || indirect)) + if(e->to->...
2008 Jul 06
3
Routing and keying Questions
Hello! I use tincd to interconnect 3 LANs: A, B and C. So long, it works fine: everybody reaches everybody. But I want a different behavior: A and B should be allowed to talk, as should B and C. I tried to simply delete the host-files on the nodes that should not be allowed to talk to eachother: A has a hostfile from B B has a hostfile from A and C C has a hostfile from B But this is no