Jump to content

Azlios

Members
  • Content count

    46
  • Joined

  • Last visited

Everything posted by Azlios

  1. I can be happily playing Rocket League on PC with a solid steady 24 Ping and then as soon as the Fire TV is turned on I have the worst lag ever with my ping fluctuating to over a 100 and then back down. I've tried literally everything I can to fix this, I've tried manually forwarding the required ports for Rocket League on PC, it had no effect. I've reclassified my PC on the duma as an xbox and it didnt change anything. I tried giving the Fire TV 0 priority in the flower but it literally changes nothing as it continues to pull absurd amounts of bandwidth. The only way I've found to stop it causing me to lag is to turn off share excess and give it .01Mbps of internet up and down. As you can understand this isn't ideal as I immediately get moaned at that the TV is now buffering. any help would be appreciated. Edit - its all PC games actually. getting the same on Siege as well.
  2. 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.
  3. 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.
  4. unfortunately being connected straight to the router didn't make much difference, if any at all.
  5. It was indeed through a powerline adaptor. I can try and give it a go tomorrow straight from the router.
  6. no port forwarding or UPnP enabled on the hub, only device connected to the hub is the duma.
  7. Yup R1 in DMZ, WiFi on hub completely turned off along with the silly BTFon WiFi turned off too.
  8. I just have the standard st up. Wall socket > BT Smart Hub > Netduma > Everything Not really sure what’s going on with it. Thinking I might just replace the amazon tv with another chrome cast.
  9. Yeah, I have no wifi direct thing as its the wrong type of fire tv. I've tried before with classified games turned off and it didnt help.
  10. IPv6 has always been turned off as i've never known how to properly use it. I also found this, my amazon tv doesn't have the wifi direct thing though
  11. some of the device names are wrong, so where it says "Jack Desktop" its actually an xbox my PC is set up as a PC
  12. My general experience with the Duma and Destiny 2 is that Ping Assist doesn't really work if at all. I normally just have it set at 0 due to this. As for the Geo-Filter radius, it will normally only filter the fireteam leader. For example me being in the UK I have my radius to only cover the UK, so if I'm going up against a team in quickplay and their fireteam leader is from the UK but the other 5 plays are from America, it will let them through as the fireteam leader will be connecting with me through peer to peer only and the 5 others from the US are going through a mixture of dedicated servers and peer to peer to connect to me.
  13. Try clicking on the main server coming from Bungie, it's a dedicated server in Washington, Top left of america on the geofilter map, see if it still reads as that low. The duma has generally been spotty with Destiny 2 due to their ridiculously complicated matchmaking system. I hop from dedicated servers to peer to peer all the time.
  14. So done some digging into this with PingPlotter, definitely something up with the fire tv. Max Down - 80Mbps Max Up - 20Mbps I actually get these speeds to, averaging between 76-79mbps and 17-19Mbps I hope this image makes sense to you guys, tried to make it as simple as possible.
  15. Just out of curiosity would I be able to still use the Duma if I turn off DHCP on the Smart Hub
  16. I have anywhere between 10-20 devices connected at a time, I can try and give them all static IPs and turn off the DHCP server when I get some time.
  17. So WiFi just dropped on the seventh day like usual, even devices with static IPs dropped too. Simple fix like always, a quick change of the wifi channel and all back up running again. I starred out what I'm guessing are mac addresses to some of my devices. Log for when the WiFi dropped - Thu Jan 3 22:48:12 2019 kern.err kernel: [184230.688000] ath: phy0: Failed to stop TX DMA, queues=0x00c! Thu Jan 3 22:48:08 2019 kern.err kernel: [184226.104000] ath: phy0: Failed to stop TX DMA, queues=0x00e! Thu Jan 3 22:48:03 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:03 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:47:52 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Thu Jan 3 22:47:51 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** IEEE 802.11: disassociated Thu Jan 3 22:47:40 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Jan 3 22:47:40 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Log just after it came back after channel change - Thu Jan 3 22:58:37 2019 daemon.info dnsmasq-dhcp[19874]: read /etc/ethers - 0 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: read /tmp/hosts/dhcp - 0 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: read /etc/hosts - 2 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using nameserver 192.168.1.254#53 Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using local addresses only for domain lan Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: reading /tmp/resolv.conf.auto Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using local addresses only for domain lan Thu Jan 3 22:58:37 2019 daemon.info dnsmasq-dhcp[19874]: DHCP, IP range 192.168.88.100 -- 192.168.88.249, lease time 7d Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP conntrack no-ipset no-auth no-DNSSEC Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: started, version 2.71 cachesize 150 Thu Jan 3 22:58:36 2019 daemon.info dnsmasq[1155]: exiting on receipt of SIGTERM
  18. Had a full drop out today, wired included. I was at work though so couldn't grab the log for when it happened, all the log said when I got home was the good old kill flow to timeout. I think its just my duma is getting old and has taken a couple too many knocks and is beginning to struggle.
  19. mine used to drop near enough everyday, got advised to increase my DHCP lease time in the duma so I put it at the max 168 hours, 7 days. Nearly always on that 7th day my wifi drops and I have to do a manual change of the wifi channel to get it back.
  20. I get this roughly once a week. My log looks exactly the same. I've managed to narrow it down to being something wrong with when the DHCP lease renews.
  21. sliders at 70%, playing on TP-Link TL-PA9020PKIT power line adaptors.
  22. I have tried this but I feel like I'm doing it wrong, do I put both numbers into both the source port and destination port boxes or do I only put 7000 in the source port and 10000 in the destination port?
  23. Been told I don't need PPOE when using a BT Smart Hub. Any time I've tried to use PPOE on the Duma with the Smart Hub I couldn't get a connection.
  24. my geofilter doesn't show any symbols at all when I'm playing Destiny 2 on xbox. It doesn't ping a host either. It basically doesnt show anything except sometime shows an allowed player that I've tried to block but it never does. Id of allowed player - 25a289543fc4f9fe
  25. ignore me I'm an idiot on my last factory reset the duma got my pc and xbox mixed up in the auto name thing so i thought I was putting my xbox in the filter when really i was putting my PC. all fixed now and back to working perfectly.
×