Jump to content

Azlios

Members
  • Content Count

    94
  • Joined

  • Last visited

Everything posted by Azlios

  1. Could that mean mine is dying too? Had it since October 2015.
  2. This is basically identical to my experience too.
  3. Mine is already set at a week that's why it drops every Thursday. Tried giving everything static IPs before and it didnt help. As bbursley said I can fix it nearly every time too just by switching channels.
  4. Mine just went down now, wasn't downloading anything as far as I am aware. Thursday is generally the day it drops though. This is my log: Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:18:11 2019 kern.info kernel: [557319.408000] send: nf_ct_get failed Thu Mar 14 17:18:11 2019 kern.info kernel: [557319.408000] send: nf_ct_get failed Thu Mar 14 17:18:10 2019 kern.info kernel: [557318.544000] send: nf_ct_get failed Thu Mar 14 17:18:10 2019 kern.info kernel: [557318.544000] recv: nf_ct_get failed Thu Mar 14 17:18:10 2019 kern.info kernel: [557318.544000] send: nf_ct_get failed Thu Mar 14 17:18:10 2019 kern.info kernel: [557318.544000] recv: nf_ct_get failed Thu Mar 14 17:17:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:17:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:17:34 2019 daemon.warn dnsmasq[1187]: Maximum number of concurrent DNS queries reached (max: 150) Thu Mar 14 17:17:27 2019 daemon.warn dnsmasq[1187]: Maximum number of concurrent DNS queries reached (max: 150) Thu Mar 14 17:17:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:17:07 2019 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted) Thu Mar 14 17:17:01 2019 kern.info kernel: [557249.644000] send: nf_ct_get failed Thu Mar 14 17:17:00 2019 kern.info kernel: [557248.496000] send: nf_ct_get failed Thu Mar 14 17:17:00 2019 kern.info kernel: [557248.492000] recv: nf_ct_get failed Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:43 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:13 2019 kern.info dpiclass-daemon: Kill flow due to timeout Thu Mar 14 17:16:10 2019 kern.info kernel: [557198.200000] send: nf_ct_get failed Thu Mar 14 17:16:10 2019 kern.info kernel: [557198.200000] recv: nf_ct_get failed Thu Mar 14 17:15:57 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Mar 14 17:15:57 2019 user.info com.netdumasoftware.neighwatch: DHCP old event.
  5. I play with my filter set to roughly around 200 miles with a ping assist of 0 and I too find matches quickly when playing in Quickplay. It does make it take forever when matching in comp though.
  6. That could make sense actually. I'm constantly downloading game updates, driver updates and updates for design software. Next time I have a large download I'll see if it triggers a wifi drop.
  7. Thanks Jack, I'll sit tight for now then but if I find anything else I'll let you know.
  8. Yes, I have to put my PC in traffic prio as a games console to get QoS to work, but it doesn't help much with that either, but that's a separate topic. When I have it in traffic prio it initially drops my wifi more but then goes back to the once a week drop after a couple days.
  9. Back again, this time with a Roku. Streaming sticks that go in the TV just seem to completely ignore anything the R1 is trying to do. This is me playing Rocket League with my sliders at 30/30 and my computer set as a games console in the traffic prioritisation along with the Roku having 0 on the flower and my PC having 50. You can see how unstable it is based on how much its changing and the constant connection error symbol on the right.. As soon as the streaming stick is turned off I drop back down to a steady 18-20 ping even if I was watching a 4k video on my computer whilst playing. I ruled out it being my PC as I get the same connection issues when playing on my xbox too. I simply cannot play online games if someone in my house is watching something on a streaming stick that goes into the TV, other than a Chromecast. That works fine. https://plays.tv/s/M6kX0g5H0rV0
  10. Welcome to the club, mines exactly the same, with near enough exactly the same log. They aren't sure what causes it.
  11. No worries, completely understand how difficult this would be to sort. It's just reassuring knowing you're attempting a fix. I appreciate the update.
  12. I don't mean to derail this thread but, is there any modem you recommend so I can remove my Smart Hub from my set up. I tried an Openreach Huawei HG612 but it cut my speeds in half. I've been eyeing up a TP-LINK AC1600 Wireless Gigabit VDSL/ADSL Modem Router, Archer VR600, V2 but not sure if it's any good.
  13. These are all from a quick search on the forum with similar issues across all platforms. There was even a firmware for the xr500 to help alleviate this issue. Granted they may be completely different issues and its not as simple to say here look everyone else has the same problem as me but I do think there are quite a few people out there having the same WiFi issue, and probably don't understand whats causing it, me included. Lots of people like me too that have had it since the 1.03.6 update. Like I said before though, I'm sure it's not a simple fix and will probably take some time, but now its on your radar I'm happy to think you'll have it fixed soon. ^^"They're different platforms and therefore different issues. This one is for Netgear to fix. If once DumaOS is released on the R1 WiFi issues continue we will be able to look into it further and have a fix."
  14. It used to have a static IP but since it didn't help the situation its all set up to be automatic again. I'll try keep an eye on the system info page as much as I can on Thursday next week to try and see whats happening when it drops.
  15. nope I tend not to change anything like that as I don't really understand any of it. Only thing I changed was the lease time to a week when asked to.
  16. I've kinda accepted it at this point, can't even imagine where you guys would even consider to start, so many possibilities as to why this is happening. I have to be honest my Duma is pretty beat up, its been dropped a couple times and is still battling through. I also don't think this is just a Duma issue. I reckon it might have something to do with BT too if George is also on BT? The Smart Hub really is a dreadful piece of kit. Knowing you guys are aware and looking into it is some piece of mind though, just thought I'd let you know its appreciated. Just to add to this as it may help. Just had my brothers xbox not connecting to wifi, the xbox network test said it couldn't connect to the DHCP server. I proceeded to hard reset the xbox one by holding down the power button. Once it came back on it knocked all the wifi out when it tried to connect again. Might be nothing, or could be that the Duma is trying to assign an addess outside of the DHCP range or not assigning one at all, then it ends up knocking everything off.
  17. That's what I have mine set at that's why its every Thursday. I have had this issue since the last Original R1 update 1.03.6j This was my original thread. Everytime it goes down that "user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory." is always there along with DHCP issues and RSN handshakes being incomplete.
  18. yeah, gave all 24 devices static IP's it didn't make a difference. The weirdest part about it is I don't even need to restart the Duma or anything to fix it, all I do is change the WiFi channel and it comes back. I end up rotating through channels 1,6 and 11.
  19. Just wanted to add mine is still having this same issue. Every Thursday, WiFi drops.
  20. It's fixed it yeah, will try and see how high I can raise it though until the issue returns.
  21. New update, if I put anti bufferbloat to 10% it finally starts doing its job.
  22. so another update on this, got rid of the firestick, replaced it with a Roku. Same issue, QoS is doing nothing to stop it. Tried reinstalling 2.1.3 to see if I had a bad install, didn't make a difference.
  23. There was nothing on the hub. I seemed to have fixed it though. I changed the video quality on the fire tv from best to better and its gone from using around 15-20Mbps to using like 0.4-2Mbps when in use. Now it's not using enough bandwidth to cause me to lag.
  24. unfortunately being connected straight to the router didn't make much difference, if any at all.
×
×
  • Create New...