Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daemon causes connection loss. #1761

Closed
doei opened this issue Sep 27, 2015 · 12 comments
Closed

Daemon causes connection loss. #1761

doei opened this issue Sep 27, 2015 · 12 comments

Comments

@doei
Copy link

doei commented Sep 27, 2015

As discussed on #ipfs I can't run the ipfs daemon for more than a few minutes without getting kicked off. The issue looks similar to this one, however having had this problem for a few days already, my ISP did not contact me for any port scanning problem.

@whyrusleeping advised me to filter a few IPs (from this list), which seemed to delay the connection loss for a bit, but didn't fully solve the issue...

Hope it helps, tell me if you want some more logs and/or info for whatever...

@ghost
Copy link

ghost commented Sep 27, 2015

Maybe this is generally an issue with the number of open connections? You could ipfs swarm peers | wc -l >> peercount.log until the connection drops?

@jbenet
Copy link
Member

jbenet commented Sep 28, 2015

@doei what's your ISP? they may be throttling anything that looks like p2p.

@doei
Copy link
Author

doei commented Sep 28, 2015

@lgierth tried it a couple more times with this in mind, got disconnected after around 125 peers each time.
@jbenet I doubt that cause bittorrent works fine.
I also tried deactivating the router's ipv6 firewall, but it didn't seem to change anything...

@cryptix
Copy link
Contributor

cryptix commented Sep 28, 2015

@doei I had weird issues with my ISP for month where daemon startup crashed and rebooted their supplied modem. BT and other P2P also worked fine, too.

@doei
Copy link
Author

doei commented Sep 28, 2015

@cryptix so how did that stop?

@cryptix
Copy link
Contributor

cryptix commented Sep 28, 2015

@doei hour(s) of calls and two holiday-days to get a support "techie" from them to run speedtest.net at my home.. I had to demonstrate them the crash twice until they changed something. I still think that it was the ISPs crappy carrier-grade NAT but... Just saying that you shouldn't factor out the ISP too soon.

@doei
Copy link
Author

doei commented Sep 28, 2015

@cryptix so they didn't tell you what they changed exactly? I'm not factoring out anything, but filtering p2p traffic alone can't be the reason. Anyway thanks for the answers, i'll post here if anything ever changes.

@jbenet
Copy link
Member

jbenet commented Sep 29, 2015

@doei that's painful, either way. After 0.3.8 lands this week, you'll get a udp based transport (UDT likely), so that might help.

@cryptix
Copy link
Contributor

cryptix commented Sep 29, 2015

@doei you should come over to irc so we can discuss more - maybe it's worth a try to give you a patch that inserts sleep intervals between bootstrapping nodes.

@doei
Copy link
Author

doei commented Sep 29, 2015

@cryptix i'm around :) just checked-in IRC

@Alephnaught27
Copy link

Did anybody find a solution to this problem? I'm having the same exact issue with my connection for whatever reason.

@whyrusleeping
Copy link
Member

This has been resolved since 0.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants