DumaOS 3.1 connects to Peers instead of Dedicated Servers

[munteanadrian88]

Hello Liam, Fraser,

Why does DumaOS connects to Peers instead of Dedicated Servers sometimes?

Expected Europe Central (Frankfurt):

I have tried both Polygon and Radius modes and nothing worked. Still get connected to Peers instead. Please help out guys!

Actual Peer (131.120.141.34.bc.googleusercontent.com):

Actual Peer (25.98.141.34.bc.googleusercontent.com):

Best Regards,

Adrian M.

[Netduma Fraser]

The peers will be misclassified and should show as servers, as you can see on that peer it has a domain name consistent with a google server, it will not impact you negatively, it is just a visual thing on the map.

[munteanadrian88]

Yes, but the problem is that you cannot reject a bad connection anymore since you still get matched up with that peer which is awful. Is there a way to get rid of this without re-installing the firmware? I tried to re-sync the cloud under each of views which supports it, and the map still shows the servers as peers.

 

I need that DumaOS 3.2 but Netgear are not releasing it for some reasons...

[Netduma Liam]

5 hours ago, munteanadrian88 said:

Yes, but the problem is that you cannot reject a bad connection anymore since you still get matched up with that peer which is awful. Is there a way to get rid of this without re-installing the firmware? I tried to re-sync the cloud under each of views which supports it, and the map still shows the servers as peers.

 

I need that DumaOS 3.2 but Netgear are not releasing it for some reasons...

It shouldn't matter, you should still be able to click Deny and you won't get matched with that server again. Is that not the case for you?

[munteanadrian88]

I've got this error right after logging in into the interface:

It shouldn't matter, you should still be able to click Deny and you won't get matched with that server again. Is that not the case for you?

No is not, see the snapshot below:

[munteanadrian88]

[munteanadrian88]

This Report button has never worked for me. See the snapshot below:

[Netduma Fraser]

On each page unpin any panels that have the pin icon solid white and that will get rid of the error. 

In regards to the two different servers, there are many different servers clustered in one location so blocking one in a location won't block other servers in that same location. Remove the block from Allow/deny, then block it again but give it a name, then disconnect from the server for a least 2 minutes - it should no longer appear on the map after this, then search again and it should be blocked.

We're looking into the issue some are having with reporting.

[munteanadrian88]

Hello Fraser,

I have tried the scenario described by you above plenty of times and but I still get connected to those servers I have denied previously. See the snapshot below:

 

 

Best Regards,

Adrian M.

[Netduma Fraser]

Can you show on the map where the server is and how it's appearing when it seems to be allowed?

[munteanadrian88]

[Netduma Fraser]

Interesting, looks like it may be allowed on our side which is why you can't block it, I'll double check it and if so remove it so it can be blocked. 

[gibsongilbert]

On 7/26/2022 at 9:22 PM, Netduma Fraser said:

Interesting, looks like it may be allowed on our side which is why you can't block it, I'll double check it and if so remove it so it can be blocked. gb whatsapp

Hi,

I am totally newbie here and I would like to know is this issue specific for this person dedicated server's or we all have this issue on our dedicated server's too?

thanks for your reply in advance...

[Netduma Fraser]

4 minutes ago, gibsongilbert said:

Hi,

I am totally newbie here and I would like to know is this issue specific for this person dedicated server's or we all have this issue on our dedicated server's too?

thanks for your reply in advance...

Hey, welcome to the forum!

Whitelisted servers by us would be the same for everyone, same with a server misclassified as a peer and vice versa

[munteanadrian88]

Strange things happening after several reboots today...?!

Looks like one of the reboots did not finish/execute/perform properly for some reason...?!

Can't wait to put a hand on the next firmware release greater than XR1000 1.0.0.64_1.0.49 (including DumaOS 3.2) and hopefully will be a better one:)

I have no control over the router when the reboot is taking place and logs are empty right after.

[Netduma Liam]

14 minutes ago, munteanadrian88 said:

Strange things happening after several reboots today...?!

Looks like one of the reboots did not finish/execute/perform properly for some reason...?!

Can't wait to put a hand on the next firmware release greater than XR1000 1.0.0.64_1.0.49 (including DumaOS 3.2) and hopefully will be a better one:)

I have no control over the router when the reboot is taking place and logs are empty right after.

That is very strange.

Were these reboots in quick succession or was there at least a few minutes between each reboot?

Have you since managed to successfully get DumaOS to load?

[munteanadrian88]

at least 7 minutes between them

 

yes, one more reboot:)

 

[Netduma Fraser]

If it happens again clear your browser cache/cookies then see if it loads correctly