<div dir="ltr">Hi Etienne,<div><br></div><div>I tried the patch, no change at all. Attached is a new log and also strace log. There is a FD 7 opened (the UDP socket), used and yet "ss -nlptu" doesn't see it.</div><div><br></div><div>I have a suspicion now there is something wrong with the distro/kernel. As a test:</div><div><br></div><div>netcat -ul -p600<br></div><div>ss -nlptu | grep netcat</div><div><br></div><div>gives me no output...</div><div><br></div><div>Petr</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 14, 2016 at 8:27 PM, Etienne Dechamps <span dir="ltr"><<a href="mailto:etienne@edechamps.fr" target="_blank">etienne@edechamps.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">You might want to try with <a href="https://github.com/gsliepen/tinc/pull/120" target="_blank">https://github.com/gsliepen/tinc/pull/120</a> - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket isn't functional.<div><div class="h5"><br><div class="gmail_extra"><br><div class="gmail_quote">On 14 July 2016 at 05:10, Petr Man <span dir="ltr"><<a href="mailto:petr@madnetwork.org" target="_blank">petr@madnetwork.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Good morning,<div><br></div><div>Here is the log, I don't see anything unusual. I took the same tinc binary and tried on two other machines and it works fine - binds to 655/UDP without issues:</div><div><div>udp UNCONN 0 0 *:655 *:* users:(("tincd",18872,7))</div><div>tcp LISTEN 0 3 *:655 *:* users:(("tincd",18872,6))</div></div><span><font color="#888888"><div><br></div><div><br></div><div>Petr</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 14, 2016 at 12:18 AM, Rob Townley <span dir="ltr"><<a href="mailto:rob.townley@gmail.com" target="_blank">rob.townley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p dir="ltr">Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all.</p><div><div>
<div class="gmail_quote">On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <<a href="mailto:etienne@edechamps.fr" target="_blank">etienne@edechamps.fr</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">That's strange. Can you post a detailed log from the affected node (run tincd -d5 -D), especially the initialization phase?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 13 July 2016 at 16:17, Petr Man <span dir="ltr"><<a href="mailto:petr@madnetwork.org" target="_blank">petr@madnetwork.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear all,<div><br></div><div>I have been successfully running for quite some time a tinc 1.1 network in switch mode. I recently added a new node, that refuses to communicate over UDP.</div><div>Running "tinc info mynode" from a different box returns:</div><div>Reachability: directly with TCP<br></div><div><br></div><div>It appears that tincd is not listening on UDP port 655 on "mynode". Running "ss -nlptu | grep tincd":</div><div>tcp LISTEN 0 3 *:655 *:* users:(("tincd",pid=10097,fd=6))<br></div><div><br></div><div>In the log there is a large number of these messages:</div><div>Received UDP packet from unknown source 123.321.123.321 port 655<br></div><div><br></div><div>I am puzzled how is tincd getting the packets if it is not listening on 655/UDP.</div><div><br></div><div>When I start netcat on the node on port 655/UDP I can see garbage coming in from the other nodes trying to initiate an UDP connection.</div><div><br></div><div>Would you have any hints where to start debugging this? All machines are configured the same way and work fine (various linux versions, windows). This particular box is on Ubuntu Xenial kernel 4.3.5.</div><div><br></div><div>Best,</div><div>Petr</div></div>
<br>_______________________________________________<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-bin/mailman/listinfo/tinc</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<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-bin/mailman/listinfo/tinc</a><br>
<br></blockquote></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<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-bin/mailman/listinfo/tinc</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>