Jump to content

Fawhs

Members
  • Content count

    10
  • Joined

  • Last visited

  1. I ended up unplugging it and didn't use it until 3 days ago for the BO4 beta and it seems to be the netduma is over heating because when the internet stops working i unplug it and plug it back in after a couple of minutes and it wont work but if i wait for it to cool down it works as soon as i plug it back in it is in a open area on top of a wooden box with nothing hot near it. Is there a way to tell if this is the reason? (my super hub 3 tells me if its too hot in the settings or a light comes on) also the high packet loss problem hasn't happened since i have been using it again.
  2. Like i said i have tried 3 different cables and all of them get the same thing when plugged into my R1 but if i plug them into my xbox or pc i never lose packets or lag at all. And it isn't the super hub 3 because it hasn't been doing it the whole time which it would be it has started happening within the past couple of weeks and nothing has changed within the settings to make it start happening.
  3. It may be the correct method but the wifi on the netduma is worse then the super hub 3 so not everyone can connect to it and if it worked fine for 2 months why would it just get bad like that it doesn't make sense that after a couple of months it just decides to give me packet loss because of it is in router mode. and the massive issues to do with the Puma 6 chip have never been a problem for me gaming on it for 8 months now the only time i have had issues with lag spikes/packet loss is with the netduma
  4. It was working perfectly fine for a month or 2 without it being in modem mode so why would it just change?
  5. my internet diagnostics information: Ping Jitter Spikes Packet Loss Exceptional Good Exceptional Lost 13 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=2 ttl=58 time=9.949 ms 64 bytes from 8.8.8.8: seq=3 ttl=58 time=14.865 ms 64 bytes from 8.8.8.8: seq=4 ttl=58 time=9.778 ms 64 bytes from 8.8.8.8: seq=5 ttl=58 time=9.895 ms 64 bytes from 8.8.8.8: seq=7 ttl=58 time=10.921 ms 64 bytes from 8.8.8.8: seq=10 ttl=58 time=18.501 ms 64 bytes from 8.8.8.8: seq=16 ttl=58 time=12.402 ms 64 bytes from 8.8.8.8: seq=19 ttl=58 time=10.314 ms 64 bytes from 8.8.8.8: seq=20 ttl=58 time=11.793 ms 64 bytes from 8.8.8.8: seq=21 ttl=58 time=11.579 ms 64 bytes from 8.8.8.8: seq=22 ttl=58 time=10.870 ms 64 bytes from 8.8.8.8: seq=24 ttl=58 time=11.420 ms --- 8.8.8.8 ping statistics --- 25 packets transmitted, 12 packets received, 52% packet loss round-trip min/avg/max = 9.778/11.857/18.501 ms Trace traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets 1 192.168.0.1 1.626 ms * * 2 10.13.144.1 11.475 ms 25.568 ms * 3 62.252.71.85 10.372 ms 12.574 ms 11.887 ms 4 * * * 5 62.254.85.145 15.861 ms 14.575 ms 13.751 ms 6 212.250.14.6 16.928 ms * 18.595 ms 7 * * * 8 * 216.239.43.210 13.106 ms * 9 216.239.47.195 16.025 ms * * 10 8.8.8.8 12.588 ms * 13.550 ms
  6. every single day my netduma randomly gets high packet loss and or randomly disconnects the internet from all wired and wireless devices multiple times. This only ever happens when i am connected to my R1 i have never had packet loss or internet disconnects while on my ISPs router (Virgin Media Super Hub 3) and i am connecting to it with the same ethernet cable as the R1 I have tried factory resetting the R1 multiple times, 3 different ethernet cables, moving the router, changing which ethernet ports i am connected to on my ISP router and my R1, restarting both my R1 and my Super Hub The only way i can fix this when it happens is to unplug the R1 for a while then plug it back in and reboot the router from the dashboard multiple times until internet diagnostics finally says no packet loss.
  7. My netduma R1 keeps randomly booting me offline and i need to reboot it 3 or 4 times to fix it? it has been happening all week atleast once a day and i can't find a fix. There is no problem with the Ethernet cable that supplies my internet to my netduma i have checked. I haven't changed any settings in about 2 weeks either
×