My internet keeps dropping. I'm not sure what the culprit is yet however.

My theory is that my modem is bad, or my ISP connection, but I am going through the process of elimination.

I have an arris SB8200 that is connected to my Mikrotik 4011.

At random times, my internet connection is dropping. Its only down briefly, maybe 2-8 minutes most of the time. When this occurs, the lights do not go off on my modem. All 4 stay lit, as to say no connection has been lost. The majority of the time this occurs, my connection just restores when it comes back on. But other times, it does not. On the times it does not, I usually have to hard reset the modem, then reboot the router, THEN reboot my pc (otherwise it never reconnects to the internet, but does the network), then reboot any wireless access points, and other devices on the network.

I'm not sure why I have to reboot the devices, this leads me to wonder if my router isn't re establishing connection to them? But I can access the network still from them, so I don't think thats it. They just can't get out to the internet until I restart them. Which, to me, sounds like something in the router is preventing them from connecting out, but I really don't know.

When I got up this morning, the modem lights were on, but the internet was down. I used MTR ping prior to rebooting anything, and the results were:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.1.1 - 17 | 537 | 449 | 0 | 0 | 6 | 0 |
| 142.254.148.41 - 11 | 497 | 447 | 6 | 11 | 244 | 10 |
| agg63.ldtsoh0101h.midwest.rr.com - 11 | 497 | 447 | 9 | 47 | 422 | 29 |
| agg64.clmkohpe02r.midwest.rr.com - 11 | 497 | 447 | 11 | 16 | 34 | 18 |
| be27.clmkohpe01r.midwest.rr.com - 11 | 497 | 447 | 11 | 16 | 29 | 16 |
| bu-ether31-vinnva0510w-bcr00.tbone.rr.com - 10 | 493 | 447 | 21 | 22 | 39 | 24 |
| bu-ether11.chcgildt87w-bcr00.tbone.rr.com - 10 | 493 | 447 | 21 | 23 | 40 | 24 |
| 72.14.209.252 - 10 | 493 | 446 | 20 | 22 | 35 | 24 |
| 216.239.56.119 - 10 | 493 | 446 | 18 | 22 | 34 | 24 |
| 72.14.232.169 - 10 | 493 | 446 | 21 | 22 | 37 | 24 |
| dns.google - 10 | 493 | 446 | 20 | 22 | 34 | 24 |

It was showing 17% at the router, but somehow was managing to ping out, despite having no internet connection.
I think at the end of the day, the issue is going to be my modem needs to be replaced, but in the mean time, what would be causing the router to struggle with re connection, and then all the devices needing to be rebooted?

My internet keeps dropping. I'm not sure what the culprit is yet however.

Gravity!!

Looking at the config.............

These rules are problematic in that they are wrongly placed (dst nat rules belong in the NAT chain, not forward chain) and all these rules are in the order AFTER (in both forward chain and input chain) you have put in place the excellent DROP all else rules. Not clear is if this is the root of the problem but something to clean up.


/ip firewall filter
......................
add action=accept chain=forward comment="COD TCP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=3074,27014-27050 protocol=tcp
add action=accept chain=forward comment="COD UDP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=3074,3478,4379-4380,27000-27031,27036 \
protocol=udp
add action=accept chain=forward comment="WOW TCP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=1119,3724,6012 protocol=tcp
add action=accept chain=forward comment="WOW UDP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=1119,3724,6012 protocol=udp
add action=accept chain=forward comment="XBL TCP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=53,80 protocol=tcp
add action=accept chain=forward comment="XBL UDP" connection-nat-state=dstnat \
dst-address=192.168.1.2 dst-port=53,88,500,3544,4500 protocol=udp
add action=accept chain=input comment=UPNP in-interface=bridge1 protocol=udp
/ip firewall nat


In plain english, delete all the above rules, not required as you have them also entered in DST NAT I believe.
However they are all to one IP address. Personally I have people here that play WOW without any firewall rules or destination nat rules for that specifically but they use PCs, not stupid playboxes.

Here they are in their long winded glory........... see below in code block

Doing it such a crappy unorganized mess leads to errors.
For example
add action=dst-nat chain=dstnat comment="COD TCP 27014-27050" dst-port=\
27014-27050 in-interface=ether1 protocol=udp to-addresses=192.168.1.2

Will assume you meant TCP there...............
What it could look like, just for giggles, need only two rules..........

add action=dst-nat chain=dstnat comment="sillygamer" dst-port=53,80,1119,3074,3724, \
6012,27014-27050 in-interface=ether1 protocol=tcp to-addresses=192.168.1.2

add action=dst-nat chain=dstnat comment="sillygamer" dst-port=53,88,500,1119,3074,3478,3544,3724, \
4379-4380,4500,6012,27000-27031,27036 in-interface=ether1 protocol=udp to-addresses=192.168.1.2

.

I added the filter because of this post here

viewtopic.php?t=154176

But I don't think this is related to the issue.

Well delete all the firewall rules after the DROP all else rule in the forward chain and see if that helps.
Fix the port forwarding rules, (which I still state you should not need if you are using a PC for gaming).
Other than that nothing stood out for me in the config??

the modem lights were on, but the internet was down. I used MTR ping prior to rebooting anything, and the results were:

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.1.1 - 17 | 537 | 449 | 0 | 0 | 6 | 0 |
| 142.254.148.41 - 11 | 497 | 447 | 6 | 11 | 244 | 10 |
| agg63.ldtsoh0101h.midwest.rr.com - 11 | 497 | 447 | 9 | 47 | 422 | 29 |
......

You can PING without problems. So your internet is UP. It does PING and even resolves DNS addresses. So the line, modem, router, AP, client are connected and transmitting.

What makes you claim "but the internet was down". Something clearly is not working for you. Can you explain exactly what is not working ?

What was not working was the internet, on any device. I couldn't connect to hulu on my tv, I couldn't connect to facebook on my pc. Everything on the network was connected to the network, but nothing would connect to the internet outside of it.

I think its the modem because it was doing the same thing with a previous router, when I had to hard reset the modem, and then reset the router as well. Plus the arris sb8200 seems to be having an issue, according to other users that are experiencing the same thing I am.

What was not working was the internet, on any device. I couldn't connect to hulu on my tv, I couldn't connect to facebook on my pc. Everything on the network was connected to the network, but nothing would connect to the internet outside of it.

I think its the modem because it was doing the same thing with a previous router, when I had to hard reset the modem, and then reset the router as well. Plus the arris sb8200 seems to be having an issue, according to other users that are experiencing the same thing I am.

OK! But you could ping. Where did you PING from?

Modem could indeed block new connections (except PING). But the router not reconnecting is not expected. Does the router still have it's IP address on ether1? Is the IP default route still there ? (It should, as you can ping). Are the DHCP-server leases for the client devices still there? (Well they look static, so probably this is not enough as verification , and should be status "bounded" as well, I think.). Can your devices reach each-other in the LAN ? What's in the IP/Firewall connections table? Anything in the "log" ? What happens to all this when you reset the modem ?

As I do not (yet) expect double causes for the problem, resetting one device should fix it, it could be the modem, it could be the router with ROS 6.47.8. ("stable" is not the most stable version: viewtopic.php?f=21&t=169553#p831834 ). Downgrade to LT 6.46.8 as test if you want to exclude RouterOS bugs.

I don't have all that information available. When it happens again, as it has been rather often, I'll run through this check list and gather the info for you. Could be a day, could be a couple, but I'll have it up soon.

These threads keep coming back and you can use search for lengthy explanations (and rants in my case) about solutions.

Some simple advice:

- Use a default config and only add rules that you really need to avoid issues.
- You only need to forward UDP 3074 for COD if you must have an open NAT type (test for other games to see which ports are used) - this is done with 2 rules.
- Downgrade your ROS version to avoid bugs.
- Look into isolating your gaming clients once you have a stable configuration if you forward ports (lots of knowledgeable users here).

A faulty modem or router is very unlikely.

I started testing CW since I replied to your other thread and it is also a one port solution for open NAT. Forwarding all those other ports doesn't change anything. As I suspected, CW on PC still connects to IP ranges from gameservers, even for crossplay (those console players are using the same servers). Custom games would be the only reason to open ports, but even then, it would be over UDP.

https://ibb.co/vByfD3y

Well, I made a change on Sunday. Haven't dropped internet since.

I can tell you guys what it was, or I can give you a chance to guess what the problem was. I'll reply here shortly with what it was just in case you wanted to take a swing at it.

I can tell you guys what it was, or I can give you a chance to guess what the problem was. I'll reply here shortly with what it was just in case you wanted to take a swing at it.

Haha any chance you remember what you changed? My issue sounds similar

Well, I made a change on Sunday. Haven't dropped internet since.

I can tell you guys what it was, or I can give you a chance to guess what the problem was. I'll reply here shortly with what it was just in case you wanted to take a swing at it.

What a crock of sh*t. You never did tell, did you?

Well, I made a change on Sunday. Haven't dropped internet since.

I can tell you guys what it was, or I can give you a chance to guess what the problem was. I'll reply here shortly with what it was just in case you wanted to take a swing at it.

What a crock of sh*t. You never did tell, did you?

Lol! 100% crock of shit, I'm back trying to fix this still since december...