Jump to content

Azlios

Members
  • Content Count

    79
  • Joined

  • Last visited

About Azlios

  • Rank
    Member

Profile Fields

  • DumaOS Routers Owned
    Netduma R1

Recent Profile Visitors

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

  1. Would either of you be able to confirm for me if the xr300 has auto wifi channel? I found out the xr500 has it but want to make sure the xr300 has it too. Also does the xr300 still need the BT smart hub like the r1 does?
  2. unfortunately I have already done this but due to being in such a congested area the channel gets filled pretty quickly and my WiFi drops. Having it change automatically for me would be great. Been considering the XR300 for a while now but don’t really want to deal with Netgear.
  3. Any possibility of adding an automatic wifi channel changer that can change the channel when it becomes congested?
  4. Any chance you can see WiFi connections named BTWifi-with-FON or BTWifi-X?
  5. 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?
  6. 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.
  7. 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.
  8. 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.
  9. It is quite a trooper, I've moved it to a different part of the house now to see if it improves.
  10. Could that mean mine is dying too? Had it since October 2015.
  11. This is basically identical to my experience too.
  12. 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.
  13. 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.
  14. 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.
×
×
  • Create New...