NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Dynamic QoS not working with PPPoE connection - Does this affect all Netgear routers?
Hello, I wanted to buy the XR700 to optimize Internet access for gaming purpose on my local network. As I own the X6 R8000, I first set up a basic configuration on this one to test a first co...
You will not have double NAT if you have the router in the DMZ of the hub and will then be able to use QoS as well assuming the hub handles PPPoE itself.
Hello,
Thank you for responding to my message.
My main question is "does this affect all netgear routers"?
Can you confirm that this is a known bug?
If this was not a bug, I expect at least that the Dynamic QoS function will be inaccessible when PPPoE is enabled and that the information will be present in the documentation with a sentence like "Attention: Dynamic QoS does not work with PPPoE enabled".
As this information is not present.... I classify this as a bug.
So, is it present in all Netgear router OSes? Do you think it is also present in Duma OS?
Regarding the elements of your answer....
When you put the your router in the DMZ of the hub, it will receive a local and non-public IP address... so it's a double NAT. Are you okay with that explanation?
Only PPPoE allows you not to do double NAT or am I wrong?
Thank you very much for your follow-up.
- I can only speak for the XR routers so I couldn't say if it was a bug in other Netgear routers. Currently on the XR routers if PPPoE is used then upload QoS may not work correctly.
By putting the router in the DMZ of the hub you're telling the hub to pass ALL traffic to the router, therefore it's essentially like having a modem > router setup. If the hub can handle DMZ and PPPoE then you should be able to use QoS effectively and have an open NAT on the router.Thank you for this workaround and confirmation that Dynamic QoS on PPPoE is not currently supported in Netgear XR series routers.
I'm not a specialist. Is it a big challenge to make this functionality operational or just a matter of priority in developments?
Even if it is difficult to give dates in the forums... is this a correction planned for the short term or beyond 2020?
Thank you.