your isp router should show a local ip rather than a public one from the wan side in the router overview if it is cgnat.
From my experience if your ip has been given a bad rep especially on cloud services which you often see on vpns and cgnat, you will have alot of these vague problems with connectivity, imagine you stream a video or a peer to peer multiplayer game and every 2min the stream gets from a different server from amazon aws or akamai and then randomly one server blocks your connection, the packet drop site does kinda the same thing here.
This is what it kinda sounds like to me, if that is not the case then I'm afraid we need more info.
like how is your network defined, are there more routers and switches, is your wan fiber or goes it via satalite?
how is the quality of the ethernet cable, no exposed core wiring?
no, i'm afraid this is not the case. i have tried multiple ethernet cables and versions of firmware. i do not have a cgnat. the line to my house is so old that it has its own cable tap with one thing
and again, when i do not use the beryl, i do not have these problems
the iperf test that i ran was from my phone to the local ip of my computer. this completely removed the other network (of which this one is nested inside) from the equation, and i STILL had packet loss
so yeah, this has absolutely nothing to do with the ISP and everything to do with the router
edit: thank you for replying and giving me the time of day. sorry about my tone, i'm just frustrated right now. i wasnt directing it at you
edit2: i have a modem, which connects directly to a linksys velop mesh router. there's a cable from there that enters a splitter, and goes off into different parts of the house. from an ethernet port elsewhere, i have the beryl router plugged in, with the lan port serving ethernet to my computer
You can streamline the topology to check this issue.
For example, MT3000 connects directly to the Linksys primary router, or MT3000 connects directly to the Modem, so that test the wired and wireless packet loss situation of the MT3000.
the MT3000 wont connect directly to the modem. it doesn't work when i do so... kind of a running theme with this device
anyways, i have it directly connected to my primary router in access point mode
remember how i said im starting to think the product was defective? well i received a replacement unit. it does the same shit!!!!
i have determined that all routes that go through the router experience packet loss. this is absurd that you would release a product and its software and have it STILL be in this state a year later
i have removed all networking and isolated the device down to just my computer, the beryl, an ethernet cord, and a cell phone. packet loss out the ass still