Jump to content

Azlios

Members
  • Content Count

    94
  • Joined

  • Last visited

Posts posted by Azlios


  1. 13 hours ago, bbursley said:

    I did it with dhcp extended before. Still had drops. The only thing that ever helps is changing the wireless channel on it. Sometimes its just random too. Like today ive been on my xbox etc. and not a single wifi drop out. I think its more attributed to the channels getting congested more than anything. Im pretty sure that if you left it long enough it would eventually work fine. Its not as if the actual connection to the router drops, and the wifi doesnt disappear. You just cant reconnect to it again or itll say invalid password. Change the channel, and boom, instantly working again. Thats been my experience anyways and idk why its so sensitive like that.

    This is basically identical to my experience too.


  2. 32 minutes ago, Netduma Fraser said:

    You say it's happening every Thursday? Have you got DHCP lease set to 1 week by any chance? As I see that at the start of the log. Give WiFi devices static IPs, does it continue then? 

    Similar to above, could you extend your DHCP lease time to the maximum, I believe it's around 165 hours and see if you experience it less please? Also give static IPs to your WiFI devices

    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.


  3. 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.


  4. 1 hour ago, Dmaune said:

    Ok I'll try tonight.

    Btw i lowered my radius all the way down to 100 miles and lowered the ping to 0.  Still found matches.  I shouldn't find anything with those settings given my rural location.

    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. 


  5. 1 hour ago, Netduma Fraser said:

    Are you downloading a lot on that PC? As it will supercede QoS and could potentially cause a WiFi dropout if it's completely saturated, just a theory. 

    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.


  6. On 3/4/2019 at 11:50 AM, Netduma Jack said:

    I wouldn't put much stock in the in-game ping test; that's relying on the server quality and any input delay on top. If it hasn't been suggested already,

    I don't doubt you though, I feel like maybe there's some miscommunication going on with these streaming sticks and DumaOS. It's odd that they're recognised by the Device Manager, yet they seem to cause problems nontheless. I reckon judging by what you found on page 1 and the pingplotter results, we could probably troubleshoot this problem. I believe our testing team is aware of this but I'll make sure they see it again :)

    Thank you for your patience on this!

    Thanks Jack, I'll sit tight for now then but if I find anything else I'll let you know.


  7. On 3/4/2019 at 2:40 PM, Netduma Admin said:

    Have any of you added anything to Traffic Prioritisation? For example, your console or PC?

    If you have, could you try deleting this and then repeat your tests. Does the problem go away?

    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.


  8. 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


  9. 32 minutes ago, Netduma Admin said:

    We're working on overhauling the entire settings area to offer something more substantial and rock solid. As soon as we have a build ready for you to test, we'll get it sent over to you guys to try out. Please bare with us - we realise it's frustrating to have these drops but it's very hard for us to debug as virtually no one else is having it beyond the reports from both you and George

    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.


  10. 10 hours ago, BIG__DOG said:

    you would need an openreach modem, then connect your R1 to it and input your pppoe connection login details into the R1. The R1 does not have a built in modem where as the HH5 does. But using isp provided hardware is never a good idea as they are made on the cheap rather than quality based hardware (major isp's that is as niche ISP's often provide some great equipment).

    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.


  11. 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."

     

     

     

     


  12. 2 minutes ago, Netduma Fraser said:

    Thanks for the additional info. Your DHCP settings, have they been changed to keep LAN IPs in a restricted range compared to the default which I believe is .100-250?

    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.


  13. 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.


  14. 3 minutes ago, Netduma Fraser said:

    How often does it occur? Change DHCP lease to 1 week / 168 hours and see if that prevents it

    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.

     

     


  15. 1 hour ago, Netduma Fraser said:

    Have you tried the suggestions in this topic?

    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.


  16. On 1/15/2019 at 7:33 PM, Netduma Fraser said:

    Glad to hear you've found a workaround, looking online I can't see much of a quality difference between best and better so thats good that you're not missing out but crazy how much extra bandwidth it uses for not much improvement. QoS should still be working for it though even if it uses more bandwidth, I think it's caching future video so it's just going as fast as it possibly can

    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.

×
×
  • Create New...