I've been running this router for about 1 month. It was relatively easy to install and get going and has worked without issue since. A few things to make note of:This device has both a 'stand-alone' mode (typical web UI) and a controller mode for management. You cannot easily switch from standalone mode to controller (or back); doing so resets the entire device. The software controller runs on a Java platform so it requires a JRE. I found lots of issues with the software controller (it wouldn't display correctly on my laptop) and I didn't care for the experience. However, if you're new to Omada hardware decide early on whether you're going to run in standalone or controller mode and stick to whichever. Ideally the controller mode gives you a 'single pane of glass' view of your network infrastructure to let you configure your router, switches, access points etc... from a single interface.The vlan port tagging UI on this router is extremely un-intuitive in stand-alone mode.Wireguard VPN server was extremely easy to configure and is very fast. Dynamic DNS updater was also extremely easy to configure. I think for the price this is very capable gear for a small office or home enthusiast use. An average home user would be better of with an 'easy-button' router.

بائع محترم

After struggling with networking issues In our office I decided it was time to upgrade the network. Fully committed to the Omada ecosystem with switches, router and access points. Auto configured and was up and running in min. Tons of features for vlans etc.

It takes some time to get used to the configuration of Omada gear. It's not normal and doesn't quite make sense. I've worked on networks and routers and switches for over 40 years, so I know what i'm talking about. Overall this gear works great, just a bit weird to configure, some of the controls and how and where you setup things, example: like static DHCP clients, sucks. I still don't think I could find where you set up a static DHCP, without going through 20 screens. All the normal network concepts are there for a business, but just in some odd places and the flow of the config doesn't always make sense. Once this is set up it working it's great. I put in this ER7206 and it has double the throughput of my old Meraki (end of life MX64). So I got a nice speed increase on my home internet using the Omada. Overall I prefer business grade equipment for my home use and I'm happy I went with TP-Link Omada great price for performance, but at the cost of odd configuration and setup.

I purchased the ER7206 April 2022. I upgraded software this Spring starting with oldest and working through all recommended patches sequentially. Still working perfectly. I use WREGUARD VPN which also works perfectly on this device. The router is connected to two switches and a wifi 6 router located various places in the house connected by CAT6 cable. All interface perfectly. Port forwarding of my TABLO as well as security cameras and weather station (kitchen oven last week) and minisplit ac unit allows viewing snd control of all of these anywhere in the world. I just checked in here to see the ER7206 appears to still be the one to buy.

Facile da installare e configurare

I used this to replace a Fortigate, which was 20x the cost plus annual subscriptions of at least $300.00This unit is faster, much easier to configure and far less complex. It doesn't have the same power as far as firewall capability, but it doesn't need it and it does the job perfectly!I've split my home into 3 subnets, a general use LAN, a VoIP LAN, and a Video LAN, so as to avoid issues with VoIP calls, and this allows me to prioritize VoIP packets. Phone calls have perfect clarity, even while I've got extensive video traffic on my security cams, and across the general LAN, with Netflix running on multiple devices.It packs a lot of features and power into a small/inexpensive box!Their technical support was amazing as well!

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.

I'll start by saying that I'm a geek and my network needs aren't that of a typical household. I segment my network with VLANs, I occasionally host services from infrastructure in my house, etc. I've used so many different routers, it's hard to keep track... but I've been wanting to simplify and go back to more of an "appliance" than a computer running a firewall/router operating system like PFsense, OPNsense, or Untangle.I originally tried the cheaper version of this the ER605 but it lacks the ability to apply ACLs that permit traffic from one VLAN to another, while restricting the inverse (very important for those wanting to isolate their IoT devices). The ER7206 just received this capability in a November firmware update, so I thought I should give it a try.Of note, I also have two TP-Link Omada Wireless Access Points and liked the thought of consolidating the management interfaces for those with that of my router.I've been up and running on the ER7206 now for a couple of weeks and it's been rock solid. I have isolated my IoT network but still have access to it from the LAN. Very good. I have my guest network in place. I have my DMZ when I need it for hosting. Another benefit of this device as a Bell fiber subscriber is I am able to plug my fiber connection directly into this router thus eliminating the need for Bell's Home Hub 3000 or some other fiber to ethernet converter box.There is still a gap you should be aware of. There doesn't seem to be a way (yet?) to permit traffic from one vlan to another, on a specific port or to specific hosts. A common use case for me would be to host an instance of Pihole (DNS) on my LAN and allow my IoT devices to access Pihole for name resolution. I currently can't do this.Another common IoT network requirement is to use mDNS so devices on your LAN can communicate across to the IoT network (say an iPhone using Airplay to cast a video onto a TV set top box). I can say this works very well on this device. It's literally one toggle and a choice of the networks involved. Very easy.All in all, this works well enough that I'm going to deal with the minor limitations and watch the product mature through firmware updates. Recommended if you have intermediate or better knowledge of networking.

I used to be pretty tech savvy…back in the day I upgraded RAM, added a secondary hard drive, partitioned a hard drive to run two different operating systems, and set up a home network with router, hubs, and switches.Notice I said used to be…over the last 10 years or so I haven’t had a need to do any of those things. I bought my computers configured how I wanted them. I used the router provided by my ISP.Last year, we were running in to signal/coverage problems with our home Wi-Fi. I’d been reading about the mesh Wi-Fi systems, and when I found a killer deal on Woot, decided to give the Deco system from TP-link a try. The setup was easy, and it solved our coverage problems.In the last 3 years our ISP has had two major outages due to lines being cut by construction crews. These were both multi-day outages. The first time was annoying. The second time was a problem because I was working remotely that day, and had to get ready and drive in to work in the middle of my shift.After the second time I decided to sign up for a secondary ISP. Overkill? Probably…but I hated always worrying about whether the internet would go down again.With two inputs, I wanted a way to be able to use both of them, without having to physically disconnect one and plug the other in. I’d read about load balancing routers. I did a lot of research, and finally decided on the TP-link ER7206. It looked like it would do everything I needed. Well…it kind of did…Once it came and I started to install it, I discovered that you need a controller to utilize the load balancing and multiple input features. You can either use a physical controller, or the cloud-based software. I was going to opt for the software, but then discovered you had to run it on Windows or Linux…and I have a Mac 🤦🏼‍♀️So…I got back on Amazon and purchased a hardware controller (TP-link OC200 in case you wanted to know). The main difference between the OC200 and OC300 is the 200 is POE (power over Ethernet…I.e. no power cord…it gets its power from the Ethernet cord).Ok, sounds like I have everything I need…router, hardware controller, and mesh system. We finally got the second ISP installed today, and I decided (on 3 hours of sleep) to bite the bullet and set up the new router. I started plugging things in, and was confused when the hardware controller didn’t power on when I connected the Ethernet cable…. Yeah, about that…the hardware controller can be powered by POE, but the new router ports aren’t POE.I thought I was going to have to buy yet another piece of equipment and was getting quite frustrated at this point. Then I noticed there was a micro USB port in the back of the hardware controller…hooray! I tracked down a cord, and realized I didn’t have any outlets left in the install area. That was an easy fix though, I grabbed a power cube and got everything plugged in! Whew! I called my first ISP to approve the new router, and had one input running through the setup.Next came the truly mind numbing steps, because I was about to jump off into the unknown…setting up the router and hardware controller. I ended up in a 3 hour long chat with TP-link tech support. During that time I also had to call my second ISP to authorize the new router. And I had to change the configuration of the primary Deco from router mode to access point mode.But, after more than 4 hours total, we now have TWO internet services, running in to one router, with load balancing controlled by the hardware controller, and a mesh system for coverage. If the first ISP goes down, within 30-60 seconds the load balancing will automatically switch the network to the second one.I knew I’d be sailing into uncharted territory, and didn’t expect things to go smoothly, but I’d hoped that I’d watched enough YouTube videos that I’d be able to figure it out...notsomuch. Huge shout out to TP-link tech support for literally walking me through the set up and making sure everything was working as is should be!