@KPejman 

1.0.2 is the latest, but it will work in 1.0.1 as well. 
 

the key is to enable flow control on your computers NIC, switch ports and uplinks, and firewall uplinks. 
 

also, you want to limit bandwidth on the egress side of wan port 

  @8411guy my issue with download speed is resolved with 1.0.2 and turning on flow control on my switch ports. 

now the issue is my new devices (specially if I do a DHCP reservation) it won't work and my devices can't obtain an IP!.

  @KPejman 

Hello,

Did you set up DHCP on the ER8411 or another switch / device?

In Network \ LAN you can enable the DHCP and configure the settings.

Make sure you specify the Default Gateway on the same subnet as the IP Address of the LAN Interface.

On the Network \ VLAN, make sure you have your WAN / LAN Ports marked properly as TAG / UNTAG, and that your PVID is set correctly based on your network.

As long as the network subnet your users are on, exist on the ER8411 as a LAN subnet, you should be ok.

  @BladeComputers 

Did you set up DHCP on the ER8411 or another switch / device?

ER8411

In Network \ LAN you can enable the DHCP and configure the settings.

I have the DHCP Server enabled on Vlan1 and it gives the IP address only the first time the device connects. if you delete the device from DHCP Lease table, it won't get an IP again.

Make sure you specify the Default Gateway on the same subnet as the IP Address of the LAN Interface.

Default Gateway was set to auto and I changed it to manual but didn't make a difference.

On the Network \ VLAN, make sure you have your WAN / LAN Ports marked properly as TAG / UNTAG, and that your PVID is set correctly based on your network.

I'm not taging any vlaan, everything is set to vlan1

As long as the network subnet your users are on, exist on the ER8411 as a LAN subnet, you should be ok.

  @KPejman 

If you are getting an IP Address the first time a device connects, then things should be working well.

Everything on VLAN 1 definitely makes that side easier.

Your Lease time will define how long that client will keep the IP until it's forced to get a new one.

So on your client if you open command prompt and perform an       ipconfig /release       

then a    ipconfig /renew

You should query for a new IP Address.

Deleting the IP from the ER8411 is not going to make your device request a new IP.

  @BladeComputers thanks for all your help. 

I was reading the log of my ER8411 (in omada portal) and I noticed for some reason it shows my computer was blocked for some reason. I went to oamada app on my phone and unblocked the my Mac and everything started working. 

I have no idea how it got blocked but finally everything is working as expected. 

So, found this thread and tried a few things, but it never got to a good result. The following equipment:

• ER8411 1.0 (1.02 FW)
• BGW320-500
• 2000/2000 AT&T plan

I had the BGW320-500 attached to the SFP+ WAN1 port of the ER8411 with everything set to auto initially. Behind the ER8411 I have the LAN SFP+ connected to a 2.5GB NIC on my workstation using CAT7. Going through the ER8411, downloads would be around 280-400, uploads maxed out at 2000-2300. If I attached the workstation directly to the BGW, I would get max 2300/2300 consistently. If I iperf speed checks across the ER8411 to a host on the BGW subnet (so only testing the router), full speed.

It was only when traversing both to an Internet host that the download would suffer. I tried flow control, but could not get it maxed out with that either (although it helped a little). Now I am using Omada, so its not an option.

Some things I tried:

Instead of flow-control, I set the link speed on the BGR from Auto to 2.5G. With that setting, the 2.5G workstation can get 2300/2300 (or close). But now other internal gigabit hosts suffered (they suffered a bit before too). Those hosts can only get 300 download and 950 upload. In other words, I could optimize for one or the other, but not both.

Also tried three different brands of SFP+ ethernet tranceivers, including the TP-Link ones. All acted the same.

The solution:

Finally I remembered the ER8411 was a multiple-WAN device. I use it for a backup cell WAN right now, but why not add another one. So I made two WANs going to the BGR, one on the 2.5G link, and another on the 1G link. I set up two VLANs, one for 2.5G hosts, and a default VLAN for everyone else. I then set up two routing policies, which route the 2.5G VLAN to the 2.5G WAN link, and the other VLAN to the slower 1G link. Sure, that 1G link is double-NAT'd, but I don't care and neither do the devices. Ingress still comes in on the 2.5G link anyway since that is the one that is bridged, and that is the only time the double-natting would be problematic.

No flow-control setup anywhere with this setup, and now 1G hosts get 950/950 or so, and fast hosts get 2300/2300 using speedtest.net. It seemed hacky as hell, but I think maybe it works really well. Still have the backup cell WAN in case the two BGR links fail.

Still testing this, but maybe this helps someone... or maybe someone has a better way.