[Q] dcping tcp connect/read timeout
RoLex opened this issue · 3 comments
currently we have a problem pinging a hub with Error: dial tcp 137.74.6.25:411: i/o timeout. but web browser successfully connects to a website with port 80 on same host. also dc++ succesfully connects to same port 411 on same host. so firewall block possibility is eliminated. the only question left is:
how many sec/ms is dcping connect/read timeout? (the default golang tcp socket connect/read timeout in case custom is not set).
i think this is in pinger settings *5 sec by default.
I have it set to * 7 before building - but it fails to ping above w timeout error.
you think?
also i want to know both timeouts. connect and read. better that dev himself answers that question.
Sorry for being away for this long. This issue is related to the dcping repository, so moving it there.