
banjo22
R3 Early Access-
Posts
162 -
Joined
-
Last visited
Everything posted by banjo22
-
Done, will see how it gets on, probably be at the weekend
-
See attached. The R3 is connected to a Draytek modem, no config or anything, the ISP details then input into the R3 PPPoE. Attached, the DOSSAL is the NAS downloading.
-
-
Hi, see the start of my post it was already disabled, must have been by default, I don't recall ever seeing it.
-
Hi mate, XR1000 was for most a good experience however I did experience a fair whack of disconnects that were often down to DHCP releases, I eventually had enough of it and changed to the R3 hoping all my issues would go away. I no longer get disconnects just lots of none responses followed by speed up lag If you are a EAFC player then you'll know how stressful Champs is on a weekend, can't be doing with lag for them!
-
IPv6 was already disabled for the record. I have emailed about returning the device, not sure what the point of having PPPoE on it if it doesn't work correctly. You mention QOS on the XR1000 but I never had this issue over 2 years using it..
-
Been pppoe on the R2 and Xr1000…..seems like an easy get out clause to blame that. if it’s pppoe then how long do I have to send the r3 back?
-
PppoE. I can try that tonight and report back
-
There is certainly something not right. I have followed that guide. When not flooding the network the ping was consistent at around 20ms. I started downloading and regardless of what I set the % to whilst having 'Always On', on, the NAS (what was downloading) was using all 30mb of my bandwidth, it never changed from 50% to 90%. (My speeds are 30 down, 7 up) Help! Just to add to this. I will go into an online EAFC game, start the download going on the NAS again and all 30mb is dedicated to the NAS despite me being in an online game, my PS5 being in devices in Smartboost (the only device) and only having Gaming under priorities. (Always on, on)
-
Can you explain the percentages please? I played around with them and didn't see much improvement, its also hard to test as its just random spikes
-
Yep. Exact same setup as I had with the XR1000, which had many problems but prioritsing traffic never one of them
-
This still happens, I know it's devices on the network triggering spikes as I was in a game then when my wife turned on her laptop on and my game stopped responding and the speed up lag occurred. This NEVER happened on the XR1000 but consistently happens on the R3, so what technology has changed? The whole point with speed boost and prioritising traffic is that it protects me from these other devices. Is this going to be resolved?
-
More I’m playing COD I’m noticed a lot of lag now too. I’ve played around with the percentages, not much is making a difference. what is the router doing here? My upload is 8mb!
-
For the record I set this. Still happens, only on EAFC. Never has this on the XR1000 ever, it’s becoming unusable.
-
I have this issue every few days or so, probably rebooted the R3 more times since getting it than routers in the past 10 years Any reason for it?
-
Where's congestion control? ANy guides to set that up?
-
I'll keep an eye on that next time. It happened in the game straight after the one I uploaded. have turned on ping and connection monitoring within EAFC. I have someone in the house watching Netflix which is taking a lot of bandwidth, but like I said, everything is set to the PS5 to prioritise for traffic so it shouldn't affect it.
-
For anyone wondering what I mean, see the video I uploaded below: When I lob passed to the player (Sawa) my game stopped responding, then caught up. I'm assuming something on the network did something at that moment, and when this happens, but I thought the whole point of prioritising traffic is that my PS5 shouldn't be affected by anything else on the network uploading/downloading. My PS5 is the only device listed in Smartboost, as is Gaming. For anyone who plays EAFC and Champions this is quite a big issue 😛
-
Hi, I've seen this many times to log it to see if anyone else has experienced it. My game will stop responding for about 5 seconds, then the game will catchup; always online games and only EAFC is affected. I play a lot of COD and have not noticed it on that game. PS5. Anything I can check for to prevent it?
-
I've had the R1, XR1000 and now the R3 and considering the ability to do that still isn't here, I doubt it ever will. I'm in the same boat, I have reserved and renamed around 50 devices, considering the DumaOS is so good at tracking devices and what they are doing, you'd think a priority would being able to to save such a config.
-
Definitely the same device as the same MAC address that im renaming. I noticed after upgrading to .41 last night my PS5 was renamed to PlayStation again and this is an Ethernet connected device
-
Hi all, last night, I couldn't find any online opponents and assumed it was a matchmaking issue on EA's end, so I gave up; it's the same problem today, though, so I can only imagine my R3 is blocking something. I don't have Geo-filter enabled; what else can I look for? I have barely configured anything since getting it, so I need to figure out what's going on. My PS5 is a priority device in smartboost and that's it Any ideas?
-
Out of the box the router's IP is 192.168.77.1, and the DHCP range 192.168.77.100. I reserved a load of IPS whilst in this setup. I then changed the router to 192.168.1.1 and the DHCP range to 192.168.1.100 The rules I set in DHCP still exist; if I delete it it says the following "Delete Reservation Are you sure you want to delete this DHCP rule? Without a reserved IP, any Port Forwarding rules for this device may stop working." But they all stay there and won't let me reserve new IPs
-
I reserved loads of IPs when the router was on the old DHCP range of 77.100+, I have since change the range to 1.100 and all the old reservations are in there as rules and I'm unable to delete or edit them, meaning I can't reserve on the new range. Is this a bug?
-
I restarted through the web interface, nothing unexpected for the router. some smart plus, PlayStations, Amazon devices had gone back to default, but a number I had changed were fine.