Jump to content

Azlios

Members
  • Content count

    75
  • Joined

  • Last visited

About Azlios

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Azlios

    R1 WiFi dying

    So my wifi dropped for the 900th time this month. Managed to see it in the system info and it just said a whole lot of this - IEEE 802.11: disconnected due to excessive missing ACKs and - deauthenticated due to local deauth request At this point do you guys think its just hardware failure?
  2. is this the R1? because that does not come open easily. I've been trying to figure out how to open mine to give it a good clean for ages.
  3. Happens for me with my Xbox One too, only had it happen once though.
  4. Azlios

    Ok Netduma!

    With the way both Destiny 2 and the Duma are working at the moment it's a bit difficult. I have had times where I have had people in my fireteam from america and it's done its job, but its more common for it to fill the lobby with people outside my radius. When I match it pops up with me connecting to a dedicated server for when everyone is connecting (When the ship begins to fly) and then whilst in flight I go back to peer to peer matchmaking for the game. So I think thats where the Duma gets tripped up.
  5. Azlios

    Ok Netduma!

    Fireteams basically screw the whole process. Back in D1 it worked flawlessly, regardless of if you had a fireteam from across the globe. For D2 they added this hybrid dedicated server and peer to peer matchmaking which screws it all up.
  6. Azlios

    R1 WiFi dying

    It is quite a trooper, I've moved it to a different part of the house now to see if it improves.
  7. Azlios

    R1 WiFi dying

    Could that mean mine is dying too? Had it since October 2015.
  8. Azlios

    R1 WiFi dying

    This is basically identical to my experience too.
  9. Azlios

    R1 WiFi dying

    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.
  10. Azlios

    R1 WiFi dying

    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.
  11. 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.
  12. Azlios

    R1 WiFi dying

    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.
  13. Thanks Jack, I'll sit tight for now then but if I find anything else I'll let you know.
  14. Azlios

    R1 WiFi dying

    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.
  15. 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
×