Jump to content

KneeOnSign

Members
  • Posts

    14
  • Joined

  • Last visited

  1. Only 8 downlink channels. Need 16 for the speed/tier I'm at. Also, doesn't appear to support any 3.1 modems which blows my chance of upgrading my speeds with my ISP. Again, I appreciate all the suggestions but it doesn't seem that this is going to be a good fit for me anymore.
  2. Thanks, all. Sadly that wasn't the answer I was hoping for. Seems very few supported modems none of which I'll be switching to due to quality and ISP support. I'll have to stay with my new setup and try to con someone into buying my NetDuma...try to salvage some of the cash dropped on it.
  3. Hello: I want to preface this with, I'm sorry for the story, but it's the only way to describe what's happening. Back in June of 2016, I changed service providers. I went from 40m/5m VDSL provider to 150m/20m cable provider. Nothing internally has changed with the switch over, only the outward facing modem. Both scenarios were bridged to the Netduma. At the time of the conversion and random times since, whenever the network is stressed (maxed out), it begins to lag out. The only solution is to reboot the cable modem. Items tried and points to keep in mind: Never an issue with the DSL line (noted a lower speed) Tried two different modems Arrius (Motorola) SB6183 Netgear CM600 Tried two different PCs Tried a new router to replace the Netduma (Ubiquity Edge Router X) Cable service was upgraded by the provider to 200m/20m, still an issue The issue never appears when using the EdgeRouter. The only similarity is whenever I use the Netduma, I may or may not have an issue. I can ALWAYS repeat it whenever I max out the connection via a speed test. The only thing that will restore the pings and stability of the site is to reboot the cable modem which makes me point to the modem. However, the issue happens with both modem brands and the issue NEVER happens when the EdgeRouter is in place of the Netduma. This clearly points to an issue in the Netduma. The way it acts, it's almost like there is a buffer that fills up on the Duma and can no longer process traffic at the speed it should introducing latency. I'll include graphs to see if they help, just note that when it spikes, we're not talking 10-20ms spikes...they are 400-1500ms spikes. The connection is utterly unusable. Ideas?
×
×
  • Create New...