Netduma Fraser

The interface does not work properly with https, however, it's a local address, inaccessible from the internet (unless you enable the option to make it accessible) and so https isn't needed

No worries, that's exactly what this kind of support is for so you can answer when it is convenient for you, we'll keep answering if you do. What do you mean by "picture of the speed test run from my cellphone, after being able to get online via Ethernet port, but not via WiFi" are you saying you have an ethernet adapter for your phone that you were using?
The firmware doesn't go back if you factory reset, it will stay on the one you're on but you won't be able to miss that you've factory reset correctly if you see the setup wizard instead of the normal interface. Okay keep us posted!

Added

Thanks for the comments, I'll pass them on the team for when this is considered

General errors like that I don't always trust because all it's really telling you is it wasn't able to connect and there could be another reason for it BUT If you're getting a DNS issue then that is a problem, basically DNS is what turns a URL for example netduma.com into the IP address that you use to connect to that website. So if that's not working properly then it means that entering google.com into your web browser for example it wouldn't know what IP to connect to/access to then display the correct information back to you. If that is the case the ISP should be able to sort it quite easily, either from a new modem (if this is the issue then wiring is less likely and now more likely the modem) or something they can sort remotely. 
I understand your frustration on that, they have their script they have to go through and they will go through it regardless of what you say. Your best bet is to go through the motions, tell them the issue, do/feign doing if you've done their suggestions before (make sure to leave enough time in between so they can be certain you've done it) and let them go through all the steps they're required to ask you. If they can't fix it with those basic suggestions which is likely then they will either want to send a tech out which as you've mentioned isn't viable, hopefully explaining that they will (or ask to be) escalate(d) to a tier 2 or 3 tech. They will have more knowledge and should hopefully provide more targeted support/be able to identify the cause and solution. Also absolutely do not mention another router - it's vital you're clear that this issue is experienced when directly connected via ethernet from your PC to their modem - not saying they will but some may use that as the excuse to get you off the call if they don't know what the problem is. 
Good luck, I hope you can get it sorted and would be interested to hear an update on how you get on!

That's great to hear, thanks for the update! I would suggest staying on your current version as I cannot guarantee the kind of stability for your issue that you're looking for on that version at the moment.

We don't give out any ETAs but if we were to release .645 publicly it would be using the exact same version of the firmware you're on now. If we made any changes to it we'd release it with a new firmware number.

You don't need PPPoE to connect the router to their ONT, you can just connect them and it should work unless they've specifically put measures in place to ensure you use their router connected to the ONT. You can just connect the R3 to their router otherwise.

@JOSHR3ll try this command as one command please instead:
await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_web_setup_done",params:[true]});
await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_setup_done",params:[true]});

ok thanks!

The ID is: 1FD984N Las Vegas. Ok i was wrong but its 27ms now. Not sure if still need ID. Its weird, when i connect to atlanta server it saids las vegas for a split second then after game start its Atlanta Server. So not sure if this is an issue or not. If need anything else let me know or more info. Thank you for your time.
 

They use new servers every so often, they've done it for every game, sometimes it's obvious there is an update needed, other times not

I will reply there shortly

Haha don't worry, there will be a new firmware in your lifetime! Progress is going well as far as I can see. In the meantime though there is a newer firmware you haven't yet tried which I've just given you access to: https://forum.netduma.com/forum/151-netduma-r3-early-access/

It's always a good idea to get clarity! Good advice above but that could be it. Fingers crossed they'll be able to sort it out for you. Do keep us updated!

As above the DoS attacks are rarely attacks and are usually showing connections you've made, for example some of IPs from your logs are:
3.169.149.83 - Amazon
69.147.65.251 - Yahoo
142.251.41.78 - Google
185.146.173.20 - Shopify/Cloudflare
100.52.165.89 - Amazon
The others look to be reputable as far as I can see. There is something that potentially by the looks of the MAC addresses and the fact that they don't show as legitimate device on lookups you can solve which may help, is that you're likely using iPhone(s)/Android(s)/Windows PC(s) via WiFi that are using Private/Randomized MAC addresses which would explain the constant reporting of them in the logs. If you disable this option on each of those devices it should remove the entries from the logs and hopefully if that's the cause stop the issue you're having. If not then I would suggest connecting a PC directly to your modem and see if you get the same issue, if you do then that's something you'll need to contact your ISP about.

Will check out tomorrow and report back!

Yes but won’t be able today. Ill
make note for tomorrow 

It seems as though technology is advancing very quickly. I am just trying to keep up. lol

I don't know specifically though with the features we're making e.g. ACC we wouldn't need it for that aspect at all. I suspect we would want/need better hardware if we were going to do things like this though as we push it to the hardware limits as is most of the time. Good suggestions though, I will pass it onto the team!

It just affects how you connect to people but as most games use servers now, even for chatting this is less of an issue. If you do play with people frequently and you do notice issues connecting to not having an Open NAT may be the issue. For example if you both have a moderate NAT.

Port forwarding/triggering is really only required for NAT purposes, it won't specifically improve your connection to the game. 

I'll let others comment of course but one of the reasons you don't see too many setup posts etc is because there are so many variables when it comes to networking that a configuration that works well for one person may work terribly for another. I'd always suggest experimenting yourself to see what works best, as long as you don't expect 100% of your games to be perfect then you'll find settings that work well for you.

No worries! Congestion Control should definitely be used to eliminate any existing or potential future issues caused by other devices on your network - all it takes is one singular download on your network to use all your available bandwidth and start causing issues. We usually suggest starting at 70% and fine tuning from there - you could have it set to Always or Auto Enable if you just want it to apply when gaming and then you get full speeds at all other times - this does require Traffic Prioritization which I'll come to. Bandwidth Allocation you can leave at the defaults, you won't really see any benefits from adjusting it with your speeds. 
For Traffic Prioritization you don't need to prioritize all gaming consoles - if you disable DumaOS Classified Games it will only then apply to the specific devices you add. You may be referring to adding these devices with the Games Console service/rule - this does not mean it applies to all gaming devices in your home, it just means it covers the necessary ports that gaming uses per the device you add it for. This is particularly helpful for a PC for example if say Valorant when specifically added isn't prioritizing (it uses a different method to prioritize which is susceptible to becoming out of date). By selecting your PC with the Games Console service it will prioritize the game and won't ever become out of date like the specific Valorant service will. By selecting this it won't prioritize downloads or streaming, regular web browsing etc so you won't see any issues from a stray download getting prioritized for example. If you so choose you could just add your PC to Traffic Prioritization, you don't need to add all consoles. This should then in theory give you the edge if all gaming devices are being used at the same time.
That's fair enough, doesn't sound like you need the Geo-Filter at this stage.

I'll give it a few days as it is a brand new line