this post was submitted on 24 Nov 2023
1 points (100.0% liked)
Home Networking
198 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
. While that could have a number of causes, if it really only happens to Internet connections (the "connection to raids" comment is confusing me) then what you are seeing may be consistent with a NAT table overflow in one of the routers. The NAT table in a router tracks what it thinks are your currently active connections to Internet destinations but tends to accumulate a lot of cruft when it can't tell, or doesn't process, when a connection closes and is no longer in use. When the table fills and the router needs to find space for a new connection it responds by blowing out some of the existing stuff in the NAT table. If some of the stuff it dumps is currently active this causes incoming packets for those connections to be dropped until the internal host sends something that reestablishes the table entry, which may take some seconds.
To determine if this might be the cause one would look at the state of the NAT table in the router to see how close to full it is running, but many consumer routers don't show this. To make it work better one would increase the size of the NAT table and maybe tune its other parameters, but most consumer routers don't support that. Failing this one might buy a router with a bigger NAT table, but most consumer routers don't tell you how big theirs is. There are fairly inexpensive routers that do let you manage the NAT table but they tend to be ones that can be deadly difficult to configure.
Note that if this is your problem the problem could be either in your router or the router that is in "bridge mode" (what it is actually doing can be a mystery; the routers AT&T makes everyone use famously keep their NAT table in use not only in the "IP passthrough" modem emulation but also when you buy extra IP addresses so no NAT is necessary). If you can replace the modem/router with a real modem you could eliminate that as an issue. As for the other router, with no NAT configuration all you could do is replace it with another that you hope works better. All this is a lot of hardware to buy if the current routers don't give you a way to determine that the NAT table, and not some else, is in fact the problem.