<div dir="ltr"><span style="font-size:12.8px">> Then I remove the “ConnectTo = B” statement from A</span><br><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">when you do this, means just the A will not setup a metadata connection to B on startup.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Please read this email from the archive:</span></div><div><span style="font-size:12.8px"><a href="https://www.tinc-vpn.org/pipermail/tinc/2010-April/002288.html">https://www.tinc-vpn.org/pipermail/tinc/2010-April/002288.html</a></span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Yes, it was 7 years ago. But if you are using tinc 1.0.x your should find your answers on that thread.</span></div><div><br></div><div>Cheers</div><div><br></div><div><span style="font-size:12.8px">Saverio</span></div><div><span style="font-size:12.8px"><br></span></div><div class="gmail_extra"><br><div class="gmail_quote">2017-06-01 4:21 GMT+02:00 Bright Zhao <span dir="ltr"><<a href="mailto:startryst@gmail.com" target="_blank">startryst@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div>Hi, All</div><div><br></div><div>Here is the case: </div><div><br></div><div>A, B, C, D all configured with "IndirectData = yes”, so connection only happens when there’s a “ConnectTo” in tinc.conf.</div><div>Arrow indicate the “ConnectTo” direction</div><div><br></div><div>Everything works fine earlier as below:</div><div><br></div><div>1. A connect to C, D connect to C</div><div>2. C is the transit node where only forward traffic between A and C</div><div>3. D advertise <a href="http://0.0.0.0/0#2" target="_blank">0.0.0.0/0#2</a></div><div>4. A can access internet from D through C, no problem at all</div><div><br></div><div>What I did yesterday:</div><div>5. A connect to B</div><div>6. B advertise <a href="http://0.0.0.0/0#1" target="_blank">0.0.0.0/0#1</a></div><div><br></div><div>Then I thought the traffic will go through B directly if B is reachable, but when B is down, traffic will fallback to D(through C), but interestingly, when the step 5 and 6 are done, I found the traffic seems goes to B though C(not directly), which is not under my earlier expectation.</div><div><br></div><div>Then I remove the “ConnectTo = B” statement from A, but interestingly, at this time, the traffic still goes to B through C. From what I know from tinc, if the “ConnectTo” is removed, and IndirectData = yes every where, this shouldn’t happen. And from the tcp connection perspective on A at this moment, it indeed only connect to C, no connection to B at all.</div><div><br></div><div>Then I investigate further, I found the advertised route from B still exist on C, where it shows something like below:</div><div><br></div><div><i>2017-06-01T09:00:29.558712+08:<wbr>00 C tincd: <a href="http://0.0.0.0/0#1" target="_blank">0.0.0.0/0#1</a> owner B <b>(That’s the reason, why C received the packet from A forward to B even A is not connected to B, in this case I have to stop the tinc daemon on B in order to make traffic goes back to D)</b></i></div><div><br></div><div>After tincd -n myvpn -kWINCH on A/C/D, then all the old unreachable info is gone.</div><div><br></div><div>So questions here:</div><div><br></div><div>1. Why in the my case, the traffic will go A>C>B path even A is not connect to B?</div><div>2. Why the unreachable info and the related advertised subnet info still exist in C even the A remove the ConnectTo statement to B(all IndirectData = yes)? Should I run a crontab to WINCH all the outdated connection regularly to avoid this? Sounds not that way…looking for advice.<br><br></div><div><br></div><img id="gmail-m_-1536574122024071590m_2869813715231865095m_5159445865130152183F9AE75C3-A641-4BBA-B76A-49137F11B3DF" src="cid:FC5D30DC-C405-408B-97E3-590386FF6DB3"></div><br>______________________________<wbr>_________________<br>
tinc mailing list<br>
<a href="mailto:tinc@tinc-vpn.org" target="_blank">tinc@tinc-vpn.org</a><br>
<a href="https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc" rel="noreferrer" target="_blank">https://www.tinc-vpn.org/cgi-b<wbr>in/mailman/listinfo/tinc</a><br>
<br></blockquote></div><br></div></div>