Version/Platform/Processor information (from ipfs version --all):
ipfs version 0.4.2
OSX 10.11.6
2.3 GHz Intel Core i7
Type (bug, feature, meta, test failure, question): bug
Area (api, commands, daemon, fuse, etc): daemon
Priority (from P0: operations on fire, to P4: functioning): P4
Description:
When I started IPFS daemon with the go version, my whole home network will crash down. I can't ping from the machine running IPFS and I can't even open webs from my phone through WIFI. Please help to fix this.
We had already report of similar issue (https://github.com/ipfs/go-ipfs/issues/2234), you can start trying to pinpoint it by disabling mDNS in config: ipfs config --bool Discovery.MDNS.Enabled false,
Yes, what @Kubuxu said -- in addition:
(gonna mark this with the NAT label just for now)
ping, but i can check my messages through Wechat, which is not using http protocol to connect. I didn't try the ethernet and the it's not happening all the time. Now i'm running ipfs daemon in a docker on my Mac, until now, everything is still fine.but i can check my messages through Wechat, which is not using http protocol to connect.
This sounds like it might be a problem with the firewall's connection tracking / flow control?
Now i'm running ipfs daemon in a docker on my Mac, until now, everything is still fine.
Are you still getting about the same number of peers? ipfs swarm peers | wc -l. If you're getting fewer, it might just not be enough to trigger the issue
@lgierth I'm not sure if it's firewall or something, since I don't firewall opened on my MacOS and router.
I don't get fewer peers. after running swarm peers, still got a lot of peers.
Duplicate of https://github.com/ipfs/go-ipfs/issues/3320.
Most helpful comment
We had already report of similar issue (https://github.com/ipfs/go-ipfs/issues/2234), you can start trying to pinpoint it by disabling mDNS in config:
ipfs config --bool Discovery.MDNS.Enabled false,