Jump to content

lllRL

Members
  • Content count

    1,134
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by lllRL

  1. lllRL

    PS4 SDD broken?

    I haven't really played BO4 because of connection issues but the game seems a laggy mess either way. The menus are even worse than BO3's... I tried to play on a fairly new PS4 Pro with a brand new Samsung 860 SSD and the menus are disgusting, it takes forever to pull up the share menu to save a clip and my PS4 sounds like a jet trying to take off. I don't see any of those issues in other games... Maybe your fan could use a clean though. I cleaned my PS4 Pro out (I think the method for accessing the fan is a little different) and because there was only a little dust inside, it didn't seem to make much difference. That could be your problem if the console hasn't been cleaned out after five years.
  2. Since upgrading to DumaOS I haven't had many problems with my R1's WiFi. On the old firmware it would randomly drop out, especially if I had both the geofilter and port forwarding in use simultaneously, but upon upgrading all those issues disappeared. Tonight I was trying to watch a pal stream on Twitch and noticed random buffering every minute or so. Nobody else in the stream had any issues and the streamer wasn't dropping frames or having any internet issues, so I assumed it was just a blip. A few hours later my WiFi started dropping out just like the grim old days on 1.03.6. I checked my QoS, tried to run a speed test and it gave me an error. The WiFi then disappeared for about 20 minutes, giving me "saved", "disconnected" and "disabled" statuses despite it clearly being there, before I could get on long enough to disable QoS and then reboot the router. It didn't make a difference. So I got my laptop out and wired up to my ISP router to turn its WiFi on for comparison. When I could finally do a speed test on the R1 WiFi it looked like this: On the other hand the TalkTalk router WiFi gave me this: I also did a wired test on the laptop while it was on, and it was working just fine. I turned the TalkTalk WiFi off again to try another test on the R1 (to prevent any interference between the two), and after changing WiFi channels and then many painful minutes waiting for it to connect it looked like this: The TalkTalk WiFi, again, on the other hand: I've since tried changing channels four times, rebooting again, and finally resetting to factory defaults, and it's still effed up. Any ideas? Sitting around waiting for it to return to normal is driving me mental. Edit: it gets worse LOL
  3. lllRL

    R1 WiFi dying

    I've only had mine 18 months, if that...
  4. lllRL

    R1 WiFi dying

    A fix for this absurdity would be marvellous ๐Ÿ˜‚
  5. lllRL

    R1 WiFi dying

    R1 is on one again, which is just typical after I decided to put my modem/router behind it back into bridge mode. Woke up and the WiFi symbol is visible but no Internet (cross symbol). Took 45 minutes to reconnect, and then I changed the WiFi channel. 5 minutes later it's out again for another 2 hours. Reconnected itself, changed the channel again, and then it started disconnecting and reconnecting every 30 seconds for about an hour. Changed back to the default channel (7) and it's stayed online for the last hour or so. I'm gonna sling it in a cupboard if it drops out again tbh. I had enough of this on old firmware and thought DumaOS fixed it, but suddenly it's randomly dropping out again ๐Ÿค”
  6. lllRL

    R1 WiFi dying

    Alright cheers. Please post here when you have any updates so I get the notification.
  7. lllRL

    R1 WiFi dying

    None of those apply to me already plugged directly into the wall, no other devices near it, out in the open (signal is fine when it's actually working, better than my TalkTalk hub) and nowhere near a microwave lol
  8. lllRL

    R1 WiFi dying

    Yup, it just started again. Only difference is there's now zero internet access instead of it coming and going with 0.1Mb
  9. lllRL

    R1 WiFi dying

    I haven't downloaded anything from a PC BTW ๐Ÿ™„ lol
  10. lllRL

    R1 WiFi dying

    Sorry for the late reply (trying to fix my broken sleep pattern lol)... No I didn't have anything like that set up at the time. The WiFi just randomly started working again yesterday afternoon ๐Ÿคจ
  11. lllRL

    R1 WiFi dying

    In the words of Limmy... I don't get it *sad confused face* ๐Ÿ˜‚
  12. lllRL

    R1 WiFi dying

    Mine did pretty often. I went back to the old firmware a few weeks ago before ping assist wasn't working on DumaOS, but then I remembered the WiFi dropouts and they pissed me off more so I upgraded again lol. I just wish they'd justified the time it took to release DumaOS by giving us a fully working product ๐Ÿ™„ Haha nah it's TalkTalk fibre to the cab. Should be 80/20, modem stats claim I can get anywhere from 70-74 down, and over WiFi it's normally 67 tops. Bit strange considering the cab is a stone's throw away, but I'm paying less than I did for BT 50/10 so I can't really complain about that. I'm not really gaming anymore because the connections I get are shite despite constantly low stable pings (6ms to London for example). The average game gives me a good 300ms of UDP latency and I can't even run custom games with bots without lagging so I'm not exactly getting any use out of the R1. However it would be nice if the rest of my devices could use the bandwidth at least...
  13. lllRL

    R1 WiFi dying

    My log mostly says this: Sun Mar 3 18:20:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:20:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:20:01 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:48 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:40 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:19:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:18:32 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:17:45 2019 kern.info kernel: [198622.428000] send: nf_ct_get failed Sun Mar 3 18:17:45 2019 kern.info kernel: [198622.428000] recv: nf_ct_get failed Sun Mar 3 18:16:05 2019 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Mar 3 18:16:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout Sun Mar 3 18:16:02 2019 kern.info dpiclass-daemon: Kill flow due to timeout I managed to stay connected to WiFi long enough to do this lol: That's with QoS disabled ๐Ÿค”
  14. Just hit the three lines here. There's a window that lets you type in your bandwidth values. Edit: nvm, misread this lol On second thoughts, I see you've played around with bandwidth allocation. Make sure share excess is ticked by clicking the three lines next to bandwidth allocation, for both download and upload separately
  15. I use the GUI with my phone, laptop, tablet or whatever I have handy at the time. Settings kick in straight away if I change QoS or filter rules, traffic prio or whatever else. Ping assist just allows whoever it likes, even if I reboot the router after setting it up. Refreshing the page (or rebooting the router) shows settings are being locked in.
  16. Nope, no bueno. Factory reset again, used a small (400~ mile) radius around my home in the south of England which the Call of Duty profile defaults to, changed ping assist from 0 to 30ms, then hooked up my PS4 and added it to the geofilter. First game host is in Saudi on 80ms. A few other random dots appeared with the ping assist symbol including Poles and Romanians, and a guy in Central Russia. All >30ms.
  17. Strange cause whenever I've upgraded or reset it starts out at 0ms, but yeah I'll give it a try tomorrow.
  18. Oh, yeah I've used the first two firmware versions that didn't have it. I accidentally went back to the second one (prior to the ping assist release) a while back so apparently that didn't help. I also factory reset yesterday before adding everything back. Again no joy.
  19. I've factory reset a few times, as well as trying and retrying all three DumaOS firmware versions.
  20. I get this all day long with ping assist enabled. Every single dot on the world map has the "ping assist allowed" icon with the dotted lines, and that often means Americans or people from the middle east. How could it possibly be working if a limit of 8ms allows a Saudi or Iranian over 130ms, or someone in the US? I mean Sarasota Florida is 4400 miles away and Mashhad Iran is 4000 miles away. You can even see my ping assist setting and someone in Asia being allowed via ping assist side by side in the third screenshot. Normally I'm asked if I've ticked fast search but the answer to that is obviously no. It's even been suggested that the ping started out low and simply spiked (to a constant high level of latency?) but that seems unlikely (impossible) unless the Iranians or Americans have figured out how to smash the speed of light with their internet. Actually I'm kinda scared to imagine how dreadful matchmaking would be with fast search enabled ๐Ÿคจ Meanwhile ping assist works flawlessly on the old firmware ยฏ\_(ใƒ„)_/ยฏ I mean it's annoying that preemptive chops off more bandwidth than the sliders would suggest, and you can't use port forwarding and the geofilter simultaneously without the GUI becoming unusable as it takes 10 minutes to load a single page, but at least the filter works well as standard. Deny/allow doesn't work for DumaOS either, and in order to use UPnP on it you have to roll back to old firmware and enable it there before reupgrading, leaving it stuck on. I'm pretty surprised these things haven't been addressed yet. Does DumaOS work out of the box on the XR routers?
  21. Unfortunately ping assist just doesn't work at all on DumaOS. I've gone back to the old 1.03.6j firmware for now so I can use it.
  22. lllRL

    Question on dns R1 duma OS

    Yup, red is on. There are problems with entering the DNS and MTU either way though, and the same goes for UPnP working - everything has to be set up on the old firmware before upgrading for it to stick for some reason. And if you do that, then decide you want to port forward and disable UPnP, the latter will remain enabled ๐Ÿคจ
  23. I upgraded back to DumaOS today and my first game on 7ms was crispy lol. I don't know what's happening anymore ๐Ÿ˜ญ
  24. I tried again today. Same old nonsense... forced one single server and I got 2 games that were normal in around 2 hours. The weird lag is actually getting worse... it's like playing on a one bar. Had PingPlotter running alongside (obviously my PS4 had the priority with hyper lane) and it was flawless, yet in game I'm getting hitmarkers after turning 180 degrees and running away, dying half a second around corners, and just generally getting joked. The final straw came when I used this ability called FTL Jump (I don't know if you've played IW but it's like a short burst of super speed where you can fly over/past someone) over someone's head, flicked back on to them instantly on max sensitivity, engaged and got three shots off before dying (with hitmarkers after I died, naturally). The killcam shows a guy from Russia with no quickdraw on his gun, PACKET LOSS ICONS and what looked like 3 sensitivity reacting late, turning and wildly hipfiring with thumb spasm aim. The best part? From his perspective, I turned like a snail. He saw me turning on what looked like 1 sensitivity. On my screen I went over his head at the speed of light and snapped back to start firing at him before he had even turned 90 degrees, and he was firing off to my right hitting me. I was facing him a good half a second before he turned to me, yet on his screen he was the one to turn 180 degrees first on what was a quarter of my sensitivity at most. How many hundreds of milliseconds of lag would there have to be to see that much desync, with that large a discrepancy, while I'm on a 7ms ping to this server? I just don't know anymore...
×