# IPFS daemon resets my Internet modem **URL:** \ **Category:** Help\ **Created:** [July 11, 2024, 7:16pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252 "2024-07-11T19:16:13Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![meeuw](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@meeuw](https://discuss.ipfs.tech/u/meeuw)\ **Post date:** [July 11, 2024, 7:16pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/1 "2024-07-11T19:16:13Z")
Hi! When I run the IPFS on a couple of systems on my network and peers start to connect my Internet modem seems to panic and reset. The modem is a DOCSIS one, provided by my cable company (Ziggo Netherlands). I cannot purchase/connect a different/better modem. The modem is configured as a bridge so it doesn’t do any routing (I have my own Linux based router for that). IPFS seems to be a really good fit for the problem I’m trying to solve but crashing my modem and Internet connection is really annoying. Is there a way to drastically lower the amount of peer connections? (I presume this is the problem). I don’t want to completely disable the peer discovery/swarming as I think it’s quite convenient. According to the documentation Swarm.ConnMgr.HighWater only disconnects peers (those will still try to connect to me). Setting Swarm.AddrFilters only disables outgoing connections, not incoming connections (flooding my ISP/modem). I hope someone can help me. ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [July 11, 2024, 8:53pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/2 "2024-07-11T20:53:04Z")
The typical problem people run into is the fact that low end consumer routers usually have a small state table, so they can’t handle the firehose of connections an IPFS node generates (they actually hang). But, you say it’s in bridge mode and not routing, so it really shouldn’t care how many connections are happening. My first question has to be: is it really in bridge mode, or do you have a double NAT situation? With double NAT, you are still using the state table and the problem stands. If not, is it doing any kind of intelligent work on the traffic, like SPI? This can lead to similar problems and should be turned off. You want the modem to be just that, and your Linux router to do the work. Turn off its firewall entirely, if you can. If not, I’m really not sure what else it could be, other than not being able to handle the traffic rate, but that’s very unlikely. Basically, by this stage, you are dealing with a dumb modem (and a switch, if it has multiple ports), it should just work. ---
**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\ **Post date:** [July 11, 2024, 9:05pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/3 "2024-07-11T21:05:25Z")
I’ve had this issue. Router would reset as soon as ipfs daemon is started. Even with low number of connections (not sure how the small state table theory applies). Mine was also in “bridge” mode. 1. You can use only tcp or only quic/udp in your swarm settings and see if that helps. 2. What I didn’t try, is to use the resource manager as an effective way of really limiting the number of connections: [kubo/docs/libp2p-resource-management.md at master · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/blob/master/docs/libp2p-resource-management.md#levels-of-configuration) Set MaxMemory to 50MiB and that should only allow 50 connections. Maybe that helps, maybe not. ---
**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\ **Post date:** [July 11, 2024, 9:57pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/4 "2024-07-11T21:57:04Z")
One thing I meant to mention as a last resort, and then completely forgot about: launch your node in client mode, instead of server mode (that just means it won’t act as a DHT server, but it will still be a bitswap server). This will crater your number of connections to a ridiculously low number. See if that helps. ---
**Author:** ![meeuw](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@meeuw](https://discuss.ipfs.tech/u/meeuw)\ **Post date:** [July 12, 2024, 7:44am UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/5 "2024-07-12T07:44:16Z")
Thanks a lot for the replies! I’ll try the client mode. I do get an Internet IP address on my router (213.93.0.0/16 range) and ports aren’t mangled, but something might still be tracking connections for some stupid reason I cannot disable. ---
**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\ **Post date:** [July 12, 2024, 8:32am UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/6 "2024-07-12T08:32:03Z")
The routers of this ISP are bugged, other peoples had success `LIBP2P_TCP_REUSEPORT=false ipfs daemon` that should work without having to limit the numbers of connections. > > > You can't access the internet when running Kubo ? > Your router periodically stop…s for a few minutes when running Kubo ? > Your internet is very slow when using Kubo ? > You are in the right place ! > > You are puzzled by the amount of background connections and or traffic ? > This is not here, please see \[discuss.ipfs.io\](https://discuss.ipfs.io/). > > Replaces https://github.com/ipfs/kubo/issues/3320 > > \# Known workarounds > > \## No Reuseport > > Try running with \`LIBP2P\_TCP\_REUSEPORT=false ./ipfs daemon\` and see if that is still happening. > > \## No TCP > > Try running with thoses config: > \- \`ipfs config --json Swarm.Transports.Network.TCP false\` > \- \`ipfs config --json Swarm.Transports.Network.Websocket false\` > \- \`ipfs shutdown\` \*\*\*restart your node for the new config to take effect\*\*\* > > \# Doing a report > > Please copy paste this template and fill in inside your message (feel free to omit unknown fields, just fill best effort thx): > \`\`\` > \- Router model: > \- ISP: > \- What OS are you running: > \- Kubo version: > \- Symptom experienced: > \- Number Kubo open connections when the crash happen (number in ipfs-companion or \`ipfs swarm peers | wc -l\`): > \- Did Disabling Reuseport fixed it: > \- Did Disabling TCP fixed it: > \`\`\` > > \# Table > > | router model | ISP | OS | Kubo version | open connections | reuseport fix | TCP fix | > |-|-|-|-|-|-|-| ---
**Author:** ![meeuw](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@meeuw](https://discuss.ipfs.tech/u/meeuw)\ **Post date:** [July 14, 2024, 11:00am UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/7 "2024-07-14T11:00:37Z")
Yes, that is my fear as well, not sure why my modem resets though. Ziggo promised me to send me a new modem so I’ll check that first. ---
**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\ **Post date:** [July 14, 2024, 2:41pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/8 "2024-07-14T14:41:02Z")
I doubt this will solve anything, this looks a lot like a software bug and unless the new modem has a newer firmware version I don’t see why a different unit would solve the issue. ---
**Author:** ![meeuw](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@meeuw](https://discuss.ipfs.tech/u/meeuw)\ **Post date:** [July 14, 2024, 2:48pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/9 "2024-07-14T14:48:47Z")
It’s a new type of modem, my current modem has a “puma chipset” which is known to have issues at high load. ---
**Author:** ![meeuw](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@meeuw](https://discuss.ipfs.tech/u/meeuw)\ **Post date:** [July 19, 2024, 6:18pm UTC](https://discuss.ipfs.tech/t/ipfs-daemon-resets-my-internet-modem/18252/10 "2024-07-19T18:18:57Z")
Allright, I installed the new modem and did some tests and it looks like the problem is solved.