TP-Link ER8411 | Enterprise Wired 10G VPN Router | Up to 10 WAN Ports | High Network Capacity | SPI Firewall | Support Omada SDN | Load Balance | Lightning Protection | 5 Year Manufacturer Warranty

Very poor Tech support

If you have multi gig internet, you need an er8411. Powerhouse router, easy to use with Omada software controller. Link other Omada devices with ease

Had a issue with bell new giga hub. It has a software glitch. Tech's at bell know this and are waiting for a update. I had tried to use the ethernet 10gig jack. Bypassing the router. Using it as a modem. Had to call bell to down grade to bell hub 3000. Once it arrived bell tech showed up next day with the sfp adapter. Used the bell hub for one day making sure no dropping of internet. Once all was good I installed the sfp into the er8411 router. Had to update firmware and the speed jumped to above 1.5 gbe. Hit 1800 download and 1100 upload. Wow. It has sfp+ input and multi wan configurable inputs. I can use the tc4000 dual link wan connection. Trying to get my cable provider to allow this. This router is fantastic. Only wish it had a qsfp output. A 40 gbe lan. You can use the multi wan as a 4 link aggregation to a tp link switch and really move data from point to point. The unit also has usb 3.0 for printer or better yet a USB lte stick. Wish tplink has a USB lte 5g coming soon. If you want me to test one i am happy too try.

بائع محترم

Works very well, was relatively easy to set up. I'm using Wireguard and I'm getting 500u/d on gigabit fiber.

This is a great core switch for both small office / home office and residential to help take advantage of multi-gig internet connectivity. I've had the switch installed for about 10 days now and it has been functioning seamlessly. My only complaint is that the switch is configured default for private IP 192.168.0.1; I failed to catch this fact during the initial installation, and it crashed my network due to an IP address conflict with my router, which has the same IP address. After realizing this, I disconnected the switch from the network and connected a computer directly to it (manually configured for IP address on the 192.168.0.x network) and logged into the switch's web interface to change the switch's IP address to one that is available on my live network; and then reconnected the switch to my main network. After doing this, I was able to easily adopt the switch via Omada SDN controller (OC300). TP-Link should have this switch default to DHCP for IP addressing, which I believe the majority / all of their other Omada SDN switches do.