After a period, stops accepting new connections (when using IP tables)
See original GitHub issueI have a linode server which is running dat right now. When I first run it, it works as expected. After some time period (>5 minutes, not sure how much) it stops working. The CLI continues to display:
Downloading in data
Share Link: 6d12454b46d77ff4af801c7e40ee8f48595cdb62e147814e9952d8d356590567
The Share Link is secret and only those you share it with will be able to get the files
[=============================>] Downloaded 53 items (639.19 kB/645.34 kB)
Waiting for connections.
So nothing appears to be wrong.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
After a period, stops accepting new connections (when using ...
I have a linode server which is running dat right now. When I first run it, it works as expected. After some time...
Read more >Stop accepting new TCP connections without dropping any ...
I use the Reselect Tries option and Inband monitor, so it always retries to connect to another server if a connection fails. But...
Read more >42.9. IPTables
The Linux kernel uses the Netfilter facility to filter packets, allowing some of them to be received by or pass through the system...
Read more >IPtables: Connection tracking - Rigacci.Org
This often happens with http entries, where the server sends an RST after a period of inactivity. ICMP. In iptables parlance, there are...
Read more >2.8.9.2.4. IPTables Match Options Red Hat Enterprise Linux 6
NEW — The matching packet is either creating a new connection or is part of a two-way connection not previously seen. You need...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@maxogden @joehand this might be a great addition to a ‘troubleshooting’ section of the dat readme
@deed02392 probably the issue was that I wasn’t listening on port 3282, which is used for discovery