Netduma Fraser

Ho risposto ai tuoi post qui - I've responded to your posts here https://forum.netduma.com/topic/32489-new-r2-unable-to-set-up/?do=findComment&comment=263935

Just to clarify, do you both have your Geo-Filter enabled over different areas or the same area?

Prendi l'IP WAN dalla pagina Informazioni di sistema su R2, quindi accedi all'hub Vodafone e inserisci l'IP nella sezione DMZ. Disattiva anche il WiFi su Vodafone in modo che tutti i dispositivi si colleghino a R2. - Take the WAN IP from the System Information page on the R2, then access the Vodafone hub and put the IP in the DMZ section. Also disable the WiFi on the Vodafone so all devices connect to the R2. I've sent you a PM, see if that helps please.

Don't add manually like that as it won't use game data that way which is required to get a ping response. Ping Warzone and then if you want to add one to your custom list click on the IP so it opens the panel at the bottom, then click the Add to list button. Yes that will be the server, so you found a mislocated server, if you add it here we can fix it in a cloud update: https://forum.netduma.com/topic/29742-found-mislocated-servers-let-us-know-here/ That shouldn't be the case, if you use the normal radius are ones you blocked being allowed? That's great to hear, it's certainly possible but unlikely as they're all flashed in the same way before shipment. Glad it's working now though, let us know if you encounter it again.

Hey, welcome to the forum! You don't need a separate modem, you can plug the R2 directly into your existing BT Hub.

You can access it here: https://forum.netduma.com/forum/130-dumaos-30-beta-netduma-r1/ You can access it here: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-DumaOS-3-0/bd-p/en-home-beta-npg-duma

Apologies, you can manually update from here, we don't upgrade the router for you: http://support.netduma.com/en/support/solutions/articles/16000085793-upgrading-your-netduma-r1-to-dumaos-from-the-original-r1-firmware

Yes you will need the fix sent to you, I'll get Alex to do this when he can.

You will have to wait for an invite from Netgear, we tried to get you up the waiting list.

As above I can confirm Ping Heatmap is working as expected: We will add a message when adding IPs manually regarding this to make it more clear. Thanks, will see what is occurring once screenshot is provided.

I talked to a developer about this and this was their response: So I'm assuming you wrote the IPs manually instead of 'Adding to List' which is why it didn't work. Could you provide a screenshot of what you're seeing on the Geo-Filter Map when you're seeing a host outside the radius please?

Yes it does.

I can't give you access to the XR500 beta as that is up to Netgear. Check our forum for the beta section for R1, you should have access. Netgear betas will be on their community site.

I've made a ticket for the developers to have a look to see if it is a bug, if they can reproduce it/know why it is happening then they will implement a fix.

Short answer - Yes! Take this with a grain of salt but new build should be within 2 weeks. Depending on the stability of that build we can open it up to get more people trying it.

I just added a few of the servers in your list to my Ping Heatmap as well and they didn't ping, this can happen sometimes if they're unpingable. I checked using command prompt and I couldn't get a ping response either so I don't think you've done anything wrong, they're just not pingable right this moment. Could you provide a screenshot of a blocked server you've connected to?

Hey, welcome to the forum!

You don't have to do that at all, that is entirely up to you. 3.0 will come to all DumaOS supported routers. It was optimized for the R2 and that is what we have developed on, porting it to other router architecture is the tricky part. Signing up to take part in the beta doesn't guarantee entry. There is a new build for the XR500 very soon and depending on that we will look into getting more people involved and we'll be starting the other betas soon as well.

Take a look at the main forum and you should see you have access to the beta section.

Remove the Device from the Geo-Filter. Then go to Device Manager and change your PC to the Device Type of a console. Then go back and add it back to the Geo-Filter. Does it work better that way? Make sure the game and client is shutdown before doing it. Where did you see the error and how often do you see it?

I don't think it's related to this issue, if it's not in bridge mode then nothing needed to change and should work just fine.

What is your Netgear community username? It's not guaranteed that everyone will get in. We;'ve got a new build coming out soon that we think will be quite stable, depending on how that goes we will look into rolling it out to more people.

Nevermind about that, I'm sure it's not related. I'll make a ticket for the devs to investigate this further.

We will have a new firmware soon so hopefully you won't see it again. If you do there will be more information we can gather from that version to help debugging.

I've boosted you up the list.