DanologyUK

MTU is to do with your ISP and nothing to do with the servers. This site will explain everything - https://homenetworkgeek.com/mtu-size/

You have been saying "Shouldnt be long" since mid February, almost 2 months! That is long

Almost 5 months since released. That is too long to have "patience" on issues which should have been resolved before it was even released. They shouldnt need to be fixing so many issues after release!

Your R3 wont lock into anything the other side of the VM router, only your VM router will handle this as your VM Router is performing the modem part of this job (those frequencies etc are from Virgin's network). You need to speak to Virgin Media if there is a fault, your R3 wont influence any of this and will only use the WAN sent to it from your VMRouter/Modem (depending on what mode you have it in).

Remember your ISP could be to blame for the packetloss as well. Set up a free "Broadband Quality Meter" - https://www.thinkbroadband.com/ping once set up, let it run for a few hours (it runs a ping from their server to your router) and it'll plot out your connection in a heatmap. See mine below. If you were to have true packetloss caused by your ISP then you will see a red spike/spikes from the top of the graph.

You can see on Twitter / X, they are clearly talking about resyncing the cloud and nothing to do with the update! Of course they will see an update as they are currently dragging their heels in releasing an update so will be testing.

4.0.41 Is the latest. Would suggest you update and retest. Link to the download is pinned to the top of the forum.

No it's not out. You will see a post pinned in this forum once it is out.

You do realise this is the THIRD router they have released and look at how the release has gone so far for this? Doesn't look like theyve learnt any lessons from the past 2 releases. You wouldnt go and build a house if you didnt know how to lay bricks, do the wiring, install the windows etc etc, so why are they releasing stuff like this if they dont know how to fix it? Basically Netduma got too greedy and wanted to release before Christmas in a broken state and then fix forward which is a poor excuse. The router has been out for almost 5 months and look at all the issues still being experienced. The issues are basic functions of any router as well so nothing specialised.

You were clearly on your PC so why even use your phone? Taking a picture of a screen to then upload from your phone screeen is just strange.

The guy can play COD on PC but doesnt know where the Screenshot button is. Hahaha

Turn this off and then retest

Ok, the answer is no

It really depends on what you are trying to achieve like Toddzilla has asked. If you have other devices in the house that may need ports to be opened then keep upnp enabled whilst also using DMZ. I suspect you may be getting confused with opening ports and UPNP being used at the same time which you cant, especially if you have devices trying to use the same port as you will see an error.

Put the IP Address of your console into the DMZ. Goto Settings - Port Forwarding - Add device DMZ

Open port 3074 on the R3 (or whatever port shows when you going into Network Settings on the Xbox)

I have already uninstalled the game as it was just a preview game. If i install again, i will test to see if this happens again and will follow the instructions above

Cant see any dot to show where the server is located. Is this a bug?

That is the lastest

Isnt it 1492 - 28 (20 are reserved for the IP header and 8 bytes needed for the ICMP Echo Request header)?

I can tell you a Mod with that "Company style" response. Beta Tester: - How are we NOT beta testers??.... Just look at the forum. It's full of faults being raised to Netduma and basic faults too! Why couldnt your "Active beta tester team" spot the majority of them?! You are clearly blind to it. You mention that "all problems mentioned on the forum are known". So basically you have admitted that the router is very broken and was released early?! Thanks for confirming that. Yes basic router functions are broken like the local management function AKA DHCP and even loading the router GUI. I have just compared like for like. Please stop trying to defend the faults as you won't win against all the clear evidence on the forum.

The link is 2 posts above your post (pinned to the top).

A lot of the "issues" posted on here, are not because of different ISPs though. A lot of the issues are down to the base software on the router not functioning. Look at the DHCP issues listed. This is basic function of even a $30 router but yet Netduma cant get this right so why should be trust them to fix all the other functions not working correctly? This router was released way too early with way too many bugs that their QC team either haven't spotted or simply ignored so they could release the router before Christmas. I totally get if their own "Netduma" functions need tweaks but the faults you can see all over the forums are more than this. I know Netduma want to take their time to fix all of these issues but answer this... why didnt they take their time to test and discover these issues and then fix these issues before releasing this? No where on the purchasing screen did it advise all of the current consumers of the R3 will be beta testing the router for them, having to provide logs for them, having to switch off functions for the router to work.

You seem to be missing the point.... TVs release and normally the basic functions of a TV (to produce an image and produce audio) is working without waiting for updates. For a starter, this router can not provide a stable DHCP service which is a basic function of any router. Ive had this router for 4 months and this is still not functioning.

There are posts on the 1st page asking when an update is coming but yes i totally agree with you. Fraser has already responded to multiple posts asking when the update is coming to advise "it's being worked on and will be coming soon". They wont give out dates.