@Tedd404 Hello, I'm using the ER8411 in standalone mode, this is not related to Omada controller in any way (not that I really care about it either, to be honest).

PPPoE handling cannot be done in CPU alone with 10 Gbps WAN, hardware offloading/acceleration is needed. My ER8411 has been able to cope with PPPoE at 8 Gbps wonderfully using hardware offloading until I enabled VLAN for WAN1 and the performance plummeted.

That is a core feature as marketed for the ER8411 and the main reason I went with this TP-Link router.

Tedd404 wrote

  @EmuAGR 

btw, are you experience something the same as the https://community.tp-link.com/en/business/forum/topic/617012

Not related, I always use the same port, the only variable that matters to find the issue is VLAN set in WAN1 SFP+ config when PPPoE is needed. Link is always 10Gbps to the ONT.

Also, IPoE (Dynamic IP) isn't affected, at least for 1 Gbps, only PPPoE.

Tedd404 wrote

  @EmuAGR 

hardware acceleration is a feature on omada controller. i am not seeing it in standalone. 

not sure about the term "pppoe acceleration"

 

do you have flow control option on sfp wan? if yes, enable it and try again. 

 

p.s. does the CPU keep at 100% during that, quote:

PPPoE HW acceleration seems disabled (100% CPU and limited to 700 Mbps) when:

I don't know about Omada controller, I cannot help with that, sorry.

Flow control enabled doesn't help. Maybe it even increases CPU usage, cannot say for sure.

I cannot choose if hardware acceleration is enabled or not, I say it's disabled when I generate traffic with VLAN tagging enabled because CPU usage skyrockets to 100% as the same pace as the throughput.

I mean, there are two possibilities: Either the VLAN tagging is doing it in a way that PPPoE acceleration gets disabled or either the router is tagging with the CPU instead of the switching ASIC and cannot cope with the bandwidth requirements. The first way may be fixed with a FW update, but the second may be not. If in the end the issue isn't fixable, this router won't be suitable for my scenario and I would need to replace it, as I'm losing 90% of my throughput.

  @d0ugmac1 Interesting tests you asked me to do.

WAN3 (SFP) with VLAN untagging to LAN2 (SFP+):

• 940/800 Mbps and the CPU stays at ~0%. That is, max download but limited upload (considering 1 Gbps limit).

WAN2 (SFP+) with VLAN untagging to LAN3 (SFP) or LAN4 (ETH):

• 940/950 Mbps and ~0% CPU. Max download/upload (considering 1 Gbps limit).

The IPTV feature doesn't work for WAN1, I can't select it.

So, the problem is not PPPoE, it's related to VLAN untagging by port WAN1 SFP+. TP-Link doesn't provide the block diagram of the device, but I suppose ports WAN/LAN 2-11 pass through an L2 ASIC and can handle tagging seamlessly, unlike WAN1 which might go to the SoC directly.

That's troublesome for me, as then I cannot use WAN1 (SFP+) to LAN2 (SFP+) to get 10 Gbps throughput and the other way is not possible as port 1 is WAN only...

Thanks for your words, @d0ugmac1. I had committed myself to solve any (meaningful) doubts about my testing methodology and that's what I'm doing here. And we happened to reach an interesting turn of results by rejecting my claim about PPPoE.

Honestly, I really like this product, it would be best if improvements keep coming.

Feel free to ask me anything, I'm subscribed to this thread.

P.S. Now I can explain why my IPoE tests weren't being affected by the VLAN setting issue, because I was using WAN3 and WAN4 ports to test it instead of WAN1, as my secondary fiber connection is 1 Gbps.