@jmole  The TP-Link Omada switches do LACP/LAG.  I have my Synology NAS running LAG to my 2210 switch with no problems.  And my Netgear modem can do LAG so perhaps someday the router will as well.  Not that my ISP side does more at this point...

I have also requested this feature for both gateway router and for OC300 controller. Currently I connect gateway two LAN ports to two ports (which are trunk ports with multiple VLANs) on same or two different switches trunk ports with one switch port to have a high STP cost. This way both ports are in UP / UP situation, but only one carries the traffic, so they are like hot standby set up, especially if I have a a switch fail, then second switch keeps services up for rest of devices via surviving switch.

But definitely a portchannel / LACP aggregate is much needed for a business product.

  @jmole LAGG on the ER605 would be a waste of time and energy because the hardware cannot handle more than 1Gps throughput anyway.  I am certain that is why they didn't bother to add the feature in the firmware.  If you want more throughput, you will need something more powerful.  The ER7206 is slightly more powerful than the ER605, but not enough to support LAGG.  Unfortunately, TP-Link doesn't offer any other more powerful routers currently.  Which is a huge hole in their lineup since 2.5Gbps and 10Gbps routers are the standard for business class hardware now.  

  @jmole 

LAGG is for more of resilient connection than bandwith aggregation here. And I agree that this feature will be mostly useful in ER7206 (that is all I have used so far and have about 12 purchased so far) and mainly for high speed local traffic load balancing, and not really to Internet.