NEW R2 FIRMWARE: 3.0.205

[yoguzturk]

9 hours ago, Kfetish said:

Should have been more specific. Not reset. Reboot. As in unplug and then plug back in. I factory reset after firmware upgrade, but a min ago I rebooted it and lost everything except port forwarding rules. It happened last time I rebooted as well but didn’t think much of it since I had not denied any servers yet. This time is was kinda brutal lol. 

I've had the same problem. I learned how to solve. I installed the old version and installed the new version again, those problems are gone. only now my port forwarding is not working in-game

[yoguzturk]

14 hours ago, Netduma Fraser said:

Everything looks fine there, the issue you're having is being unable to get an open NAT on cod?

my port forwarding is not working in-game

6.bmp

[Kfetish]

Since switching to the latest firmware my constant internet disconnects have subsided, but now I’m afraid to reboot my router for fear of losing all my settings again. I’m just assuming my port forwarding is working. I don’t know how to tell exactly. Even on the old firmware when I had ports forwarded I still had a moderate nat, as I do now with them forwarded on the new firmware. 

[Netduma Fraser]

3 hours ago, yoguzturk said:

my port forwarding is not working in-game

6.bmp 399.15 kB · 1 download

Disable the Geo-Filter, then boot up the game again, it's likely causing a misreading.

1 hour ago, Kfetish said:

Since switching to the latest firmware my constant internet disconnects have subsided, but now I’m afraid to reboot my router for fear of losing all my settings again. I’m just assuming my port forwarding is working. I don’t know how to tell exactly. Even on the old firmware when I had ports forwarded I still had a moderate nat, as I do now with them forwarded on the new firmware. 

Unplugging the power from the router and then plugging it in again isn't the proper way to reboot, the sudden loss of power will clear the memory. If you have access to the interface always reboot from there. If you want to unplug/plug to reboot then reboot from the interface first - that should then save your settings even after power loss.

[Kfetish]

Duly noted. Thank you. I wasn’t aware that wasn’t the proper way to reboot. ☺️

[yoguzturk]

47 minutes ago, Netduma Fraser said:

Disable the Geo-Filter, then boot up the game again, it's likely causing a misreading.

Unplugging the power from the router and then plugging it in again isn't the proper way to reboot, the sudden loss of power will clear the memory. If you have access to the interface always reboot from there. If you want to unplug/plug to reboot then reboot from the interface first - that should then save your settings even after power loss.

I do all but stay same

[Netduma Fraser]

10 minutes ago, yoguzturk said:

I do all but stay same

Do this:

1. Quit the game and client - including from the System Tray
2. Remove the device from the Geo-Filter
3. Flush the cloud
4. Re-add the device to the Geo-Filter
5. Setup your settings and location/radius over the area you want
6. Wait 2 minutes
7. Boot up the game

[yoguzturk]

1 hour ago, Netduma Fraser said:

Do this:

1. Quit the game and client - including from the System Tray
2. Remove the device from the Geo-Filter
3. Flush the cloud
4. Re-add the device to the Geo-Filter
5. Setup your settings and location/radius over the area you want
6. Wait 2 minutes
7. Boot up the game

I do but stay Moderate

[yoguzturk]

25 minutes ago, yoguzturk said:

I do but stay Moderate

I was foctory reset. I finished all settings again. nothing has changed thanks for helping 

[Netduma Fraser]

47 minutes ago, yoguzturk said:

I was foctory reset. I finished all settings again. nothing has changed thanks for helping 

Try putting the device in the DMZ, it should be fully open then.

[yoguzturk]

55 minutes ago, Netduma Fraser said:

Try putting the device in the DMZ, it should be fully open then.

I add my netduma İP in the DMZ,

3.bmp

[Netduma Fraser]

6 minutes ago, yoguzturk said:

I add my netduma İP in the DMZ,

3.bmp 2.63 MB · 1 download

I mean on the R2, put your device IP into the DMZ and see if it changes to open.

[yoguzturk]

10 minutes ago, Netduma Fraser said:

I mean on the R2, put your device IP into the DMZ and see if it changes to open.

I do still same1.bmp

2.bmp

[Netduma Fraser]

47 minutes ago, yoguzturk said:

I do still same1.bmp

2.bmp 4.85 MB · 0 downloads

Okay can you start a new topic please, then we can focus on your issue. In that post can you also include your exact physical setup, i.e. the model of the modem/router you have the R2 connected to please.

[yoguzturk]

20 hours ago, Netduma Fraser said:

Okay can you start a new topic please, then we can focus on your issue. In that post can you also include your exact physical setup, i.e. the model of the modem/router you have the R2 connected to please.

 

 

[Alan]

On 2/26/2021 at 8:52 AM, Netduma Liam said:

Thanks for the update, let us know how you get on with testing tonight.

Go ahead and do the reset through the GUI if you're going to upgrade again, though either method will work. If you do go back to .205 and have issues, let us know and we'll be here to help!

So over the weekend .179 was better for online gaming. No rubber banding and was getting into 30-40ms latency games on COD servers. The game would sometimes spike to around 60ms, but I think since the last update for COD something has happened that is causing that.  So last night I upgraded back to .205 and the rubber banding returned and had high spikes and also was put into games that had 130ms+ with the same geo filter settings I had set on .179. I also noticed that when having CC on always I was running speed tests and was getting my full download/upload speed when testing on our phones and laptop on WiFi. I than checked the speed on my Xbox which is hard wired to the R2 router and the download/upload speed was throttled like every device should be when CC is set to always with my percentages. 

[Netduma Fraser]

3 hours ago, Alan said:

So over the weekend .179 was better for online gaming. No rubber banding and was getting into 30-40ms latency games on COD servers. The game would sometimes spike to around 60ms, but I think since the last update for COD something has happened that is causing that.  So last night I upgraded back to .205 and the rubber banding returned and had high spikes and also was put into games that had 130ms+ with the same geo filter settings I had set on .179. I also noticed that when having CC on always I was running speed tests and was getting my full download/upload speed when testing on our phones and laptop on WiFi. I than checked the speed on my Xbox which is hard wired to the R2 router and the download/upload speed was throttled like every device should be when CC is set to always with my percentages. 

Did you factory reset after you upgraded and setup from scratch with the same settings? Where were the servers compared to .179?

[Alan]

2 hours ago, Netduma Fraser said:

Did you factory reset after you upgraded and setup from scratch with the same settings? Where were the servers compared to .179?

Yes I did factory reset after I upgrade again and the settings were the exact same. Um that I am not sure I didn't have my laptop by me but it would say searching for a match <34ms and all of a sudden would jump me into a match with very high ping. I did resync the cloud on both ping heatmap and geo filter and all the servers were in the same location on .179 and .205 if that matters at all..

[Netduma Fraser]

14 minutes ago, Alan said:

Yes I did factory reset after I upgrade again and the settings were the exact same. Um that I am not sure I didn't have my laptop by me but it would say searching for a match <34ms and all of a sudden would jump me into a match with very high ping. I did resync the cloud on both ping heatmap and geo filter and all the servers were in the same location on .179 and .205 if that matters at all..

Did you play at the same time of day/same game modes etc? It doesn't make sense to me why it would be worse on this version

[Alan]

28 minutes ago, Netduma Fraser said:

Did you play at the same time of day/same game modes etc? It doesn't make sense to me why it would be worse on this version

Yeah its usually at night around 7:30pm I am on playing warzone. Yeah I am stumped and I want to stay on the new version because WiFi range does seem better and more stable. Do you know why when having CC on always and sliders set to 70% that any WiFi devices when testing speed it receives full speeds, but my Xbox being hardwired is the only device that has its speeds throttled correctly? Makes me wonder if this is a reason why I am getting rubberbanding etc as the WiFi devices are not being affected by CC.

[Netduma Fraser]

59 minutes ago, Alan said:

Yeah its usually at night around 7:30pm I am on playing warzone. Yeah I am stumped and I want to stay on the new version because WiFi range does seem better and more stable. Do you know why when having CC on always and sliders set to 70% that any WiFi devices when testing speed it receives full speeds, but my Xbox being hardwired is the only device that has its speeds throttled correctly? Makes me wonder if this is a reason why I am getting rubberbanding etc as the WiFi devices are not being affected by CC.

Are you using IPv6, PPPoE or DHCP identifiers at all? What option are you using for CC - Always, Auto-Enable, Never? What are your Traffic Prioritization settings?

[Alan]

1 hour ago, Netduma Fraser said:

Are you using IPv6, PPPoE or DHCP identifiers at all? What option are you using for CC - Always, Auto-Enable, Never? What are your Traffic Prioritization settings?

No IPv6. No PPPoE or DHCP identifiers. And for options I turn on CC always when gaming. On .179 it would limit down/up speeds according to what I had my sliders set to for all devices when a speed test was run. My traffic prio is for xbox source 1 65535 and destination is 1024 65535. Also have tried Dumaos classified games.

 

So update.. I had my bandwidth allocation set so it was default and all devices had the same allocation for down/up. I put the xbox allocation to 70% just to match the CC slider percentage which I have at 70%. And now I test down/ up speeds on phones and laptop and they all read 70mbps down as normal. My speeds are 100 down and 10 up. I use enable share bandwidth also. 

[Netduma Fraser]

It might have been then that Bandwidth Allocation just needed to be reset - if you reset it again back to the defaults does it still get limited according to Congestion Control?

[Alan]

17 minutes ago, Netduma Fraser said:

It might have been then that Bandwidth Allocation just needed to be reset - if you reset it again back to the defaults does it still get limited according to Congestion Control?

Yeah it does work after resetting that now. Wow lol. I'll be gaming tonight so we will see if its any better. I ran dsl reports for buffer bloat and I just gave my xbox 30% up and down and getting A+. When having it set to default I am getting A or just a little bit lower consistently. 

 

Should I be using bandwidth allocation at all? Usually when I'm gaming there's only a phone connected to WiFi. But would like my Xbox to get a major part of the bandwidth on our network. So is having the xbox set to 90% down/up and do not share bandwith a bad thing and would that not correlate well with have CC set to 70%?

 

[Netduma Liam]

12 hours ago, Alan said:

Yeah it does work after resetting that now. Wow lol. I'll be gaming tonight so we will see if its any better. I ran dsl reports for buffer bloat and I just gave my xbox 30% up and down and getting A+. When having it set to default I am getting A or just a little bit lower consistently. 

 

Should I be using bandwidth allocation at all? Usually when I'm gaming there's only a phone connected to WiFi. But would like my Xbox to get a major part of the bandwidth on our network. So is having the xbox set to 90% down/up and do not share bandwith a bad thing and would that not correlate well with have CC set to 70%?

 

OK thanks, let us know!

Your console won't need that much and as there's only one other device connected, you can just leave the Bandwidth Allocation at it's default distribution and that will be fine!