I'm sorry, but I was not able to get more data about this problem. That same day windows was updated automatically and I was not able to reproduce the problem.
-----Original Message----- From: tinc [mailto:[email protected]] On Behalf Of ???? Sent: dinsdag 27 september 2016 05:43 To: [email protected] Subject: Re: Receiving packet failed: (10054) (2nd post) On Mon, 26 Sep 2016 20:40:47 +0000 Henk <[email protected]> wrote: > Thank you for your response. > Yes, I know something changed, hence the smiley. > > I have looked at the code (I was able to build it under the new > windows bash). It turns out that the error was on a udp receive, not a > tcp connection. Didn't know you would get this error. > > Anyhow near the location of the error there was a remark about IPv6. > I hadn't looked at that yet. So I turned IPv6 off at the client that > could not be reached and now it works. > > Maybe I should look at when and how to use IPv6 someday, when there > are more than 24hs in a day. Now I'm happy it works. It should be interesting to know what exactly version of Windows runs at faulty client? And was any of IPv6 services activated on it (including Teredo)? Your tcpdump (or whatever on Windows, Wireshark?) should show ICMP Unreachable packets before that error. At least many people get this when they receive 10054 error on UDP sockets. http://stackoverflow.com/questions/34242622/windows-udp-sockets-recvfrom-fails-with-error-10054 http://stackoverflow.com/questions/2576926/python-socket-error-on-udp-data-receive-10054 So probably more workarounds for Windows. One of them is probably ignoring 10054 return value of recvfrom on Windows. _______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc _______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
