TP-Link ER605 V2 Wired Gigabit VPN Router, Up to 3 WAN Ethernet Ports + 1 USB WAN, SPI Firewall SMB Router, Omada SDN Integrated, Load Balance, Lightning Protection

I'm using this router without the Omada controller. The TP-Link EAP610 Ultra-Slim Wireless Access Point went on sale so I got that and then decided to also get this router.I have AT&T fiber and wanted to use VLANs to segrate my guests, IoT, and main devices from each other.This router is working great so far for this purpose.The ER605 router has 5 ethernet ports. I'm using the first port for WAN, so I connected that directly to the AT&T gateway. It is the only device connected to the gateway. I set the gateway to IP passthrough so that it's supposed to provide the ER605 with the internet/public IP address and sort of not use the AT&T gateway's firewall. I'm not sure if this is exactly how it works or if I set it up correctly, but it's working for me.Port 2 is untagged with my main VLAN. I connected an 8-port Netgear unmanaged switch to port 2. Connected to the switch are my main devices: desktop PC, two NAS, and a server. All of those devices automatically get assiged IP address to the main LAN since the switch is connected to port 2.Port 3 is also untagged with my main LAN, but I haven't connected anything to it.Port 4 is untagged with IoT and I connect my Philips Hue Bridge to it. It gets assigned a IP address within the IoT VLAN.Port 5 is tagged with the main VLAN, IoT VLAN, and Guest VLAN. I connected the EAP610 Access Point to port 5 so I can connect WiFi devices to the router.Within the EAP610, I created a main 2.4gz and 5gz SSIDs that gets tagged with main VLAN, so all devices that connect to those SSIDs automatically get assigned an IP address within the main VLAN. I also created a IoT 2.4gz and 5ghz IoT SSIDs and all devices connected to them are auto assigned IP addresses with the IoT VLAN. I created a guest 2.4gz and 5ghz SSIDs that gets tagged with Guest VLAN. I also set those SSIDs to be "guest network" within the EAP610 settings so that those devices only have access to internet and can't even see/ping each other even within the same guest VLAN. So the EAP610 can create multiple SSIDs and can tag VLANs. It is working great with the ER605 router. I'm using six SSIDs so far.On the ER605 router, I set it so the IoT VLAN can't connect/ping devices on the main VLAN. I only use the guest VLAN with wifi and the access point already sets them up as a "guest network" so those devices are unable to see/ping IoT or Main VLAN devices.This set up is working great so far, but I've only had these devices for a few days and finished setting things up the way I like them today. Time will tell if these Omada devices will last. Once I have the funds, I plan on getting the Omada controller and an Omada compatible switch.

I purchased the TP-AX3000 Fest FR365 because I need VPN for a business to Cloud connection for a new cloud application implementation.I setup a new account for the cloud management which was easy and put in the Serial Number of the new AX3000, but I was initially unable to get it Imported into the TP-link management cloud.I tried the online chat for support and once I got past the AI question and asked to chat with a real human, I got connected to Edemer. I typed what we were seeing with the AX3000 being imported, but not connected. Edemer pointed me to the step where I needed to enable the device to be cloud managed. That step did not exist on the quick start guide, but it was in the user manual. I connected to the Web UI on the AX3000 directly and checked the setting to enable management from the TP-Link Cloud. I then needed to FORGET the device and re-import it. Within 5 minutes is was imported properly and manageable from the TP-Link Cloud management portal.The online support chat experience was quick and efficient and Edemer pointed me to the correct solution. The problem was fixed with 5-10 minutes after already spending 2-3 hours trying to get it to import on my own.The product itself seems good. I configured a few port forwards already and will be working on the VPN in the future. The port forwards even have the ability to limit the external source addresses using the port forward, so that is a helpful security feature.Thanks again Edemer for your help on the online support chat.

Bought to connect with my Spectrum modem. Plugged the modem into the Wan port - express setup didn't work. REBOOT the modem, works like a charm. I'm not using any of the advanced features, but I'm sure they would be good too. TP-LINK makes great stuff!

I am using this load balance and failover for two isps. It has good speed when doing this however there are some odditiesIt supports 802.1q trunks and vlans but it is confusing when you set them up. You have to create additional "lans" that create the vlans as part of the setup automatically, you cant create vlans and associate to the SVIs like you would on any normal network device. If you create a vlan fist you cant create the SVI for it, If you create a "lan" and tell it to use a vlan it will create them both and work fine. Its confusing on the screen because it looks at first glance to just be where you setup DHCPIt will not run ANY routing protocol - this is one of the biggest down sides for mebuilt in DHCP is very clumsy and limited. You cant set scope options (like DNS for example) differently on IP reservations. looking through the DHCP list is also very difficult because it wont sort it.If you want to run your own DNS server to get this options you will fine it also cannot set DHCP helper address on subquent vlans so you have to physically put a DHCP server in each one you want real DHCP in.It does not support any routing protocol so everything has to be static routes. Its not very good that wayWhen using multiple isps they expect an odd situation where each ISP has its own transit network instead of being on a single layer 2 and just having multiple next hops. if you try to force it to do that it flakes out. You have to set each one in its own IP space and vlan (it auto creates the vlan)Some settings like wan changes require you to reboot the router to set. This isnt a huge deal but it does take an exceedingly long time to do so. 3-5 mins. You will seriously thing its broken while you wait for it to come backThe policy based routing seems to have a VERY detrimental impact on speeds through the router. This is a nice feature but don't turn it on unless you don't have allot of wan bandwidth to start with. At 250M/S connections it cuts the speed down to around 100 for all clients - even when this is turned on for just a single IPThe isp circuit up tracking and failover seems to work but is slow like every 30-45 seconds it checks. It is unclear if you need static routes to force internet traffic for checking purposes or not. I put them in anyway because I monitor and alert on uptime via a script running on a host internally. There are no controls to change this behavior, only a place for an IP for icmp and dns tracker. The failover process itself is very hard on IOT devices. PCs and phone seem to handle it fine but anything that calls home for instructions like Echo Dots, Smart plugs etc, just dont do well. the only real way to get them to behave is to reboot them each individually, or force a wireless re-association or reboot the router completely, I suspect this is a nat refresh problem - the router is not force resetting the existing NAT translations. This corelates to the comment i had above about not supporting multiple next hop routers on the same layer 2 transit network, if they either force refreshed the Nat translations or would allow all the wan links on the same layer2 network then i think it would work much much better for most peopleThere is no way to not run nat for the wan side on these which can be problematic if you are also forced to have nat running on the next hop.There is no route tracking on these, so you can't have static routes turn on or off based on the wan link tracker which is a less intensive way to achieve some of the results of PBROverall these are nice units and seem to get full line speed on the connections I'm using (dual 250s/50).These are high performance routers that have nice features but certainly not everything you're looking for implemented. They are most definitely not designed for anyone who has a strong networking background. Price point against comparable performance routers however is very attractive and for a home user that is not all that technical would do reasonably well with these