@GDU 

Here's the issue. You need a DHCP server for the VLAN. ER605 does not support a VLAN+DHCP server like Ubiquiti.

In the TP-LINK VLAN setup, you are gonna use the switch to be the DHCP server for the VLAN2. You have to own a model that supports the DHCP server while config this.

https://www.tp-link.com/us/support/faq/3091/

Step2.2 will be the place where you stop config-ing 'cause the reason above.  

@John1234 

Thanks for reply.

Now I configure ER605 in standalone mode with 2 VLAN (port 1-2-3-4 VLAN1 and port 4 VLAN2) and all work fine, also the two DHCP server inside ER605 work.

I see the same guide that you reported me, but the solution describe need an Omada swith. At this moment I don't have Omada switch but a normal managed switch, I want to connect the ER605 to Omada controller and make the some configuration that I describe.

I try but on the controller when I want to modify the VLAN1 port, I can't, I receive a message report that "not possible to modify to default VLAN". I can modify only the VLAN2...

I try to assign VLAN2 only on port 3 of the ER605 and VLAN1 on all port (I can't modify), than I connect a managed switch on port 3 of ER605. The switch is configure with port1 (where is the link with er605) with VLAN1 untagged and VLAN2 tagged. Port 2 VLAN2 untagged and VLAN1 excluded.

I try to connect my pc on port 2 but can't receive an IP and don't work... all other port work fine on VLAN1.

Where is the mistake? I don't understand how the ER605 configure the VLAN when is receive the configuration from Omada controller.

Thanks....

@GDU 

That's right. In standalone mode, you can do a lot of stuff. But, with the Controller, everything's integrated and they work together to achieve a function.

Default VLAN1 is not modifiable!!!! Don't even think about this.

So, for TP-LINK, you are gonna set up a DHCP server on your switch. And tag the DHCP server as VLAN2. Refer to the guide: https://www.tp-link.com/us/support/faq/887/

The setup for the switch, port #2 should be untagged, PVID2. Not tagged. PC cannot accept tagged packets. 

That's super important for you to own a DHCP server-supported switch. Or you fail the setup. 

@John1234 

Thanks, I try to make your solution, I don't know if my switch can made DHCP server.

I try and I update you...

@John1234 

Hi check but my switch don't have possible to enable DHCP server. I think will be buy a TL-SG2008P this is full compatible with Omada SDN. 

In that way I can make the solution describe in this guide https://www.tp-link.com/us/support/faq/3091/.

In your opinion if I want to create my network and only one guest network, I'm forced to create two LAN in addition of default LAN like the guide? Or is possible to create just guest lan and use the default for me?

If I compare to the guide I want to use LAN 192.168.0.x/24 form me and 192.168.100.x/24 for guest; is possible? The LAN 192.168.200.x/24 I don't create it.....

Thanks

@GDU 

About the IP stuff, you can create your own. Default LAN IP can be different.

192.168.0.X/24 for the main network, 192.168.100.X/24 can be another network. That's do-able. No worries. You can set it up like that. If you want to know all available private network IP range, you can search it on google. There are three sections for the private IPs

  @John1234

I'm curious about the assertion earlier that the ER605 is not the device handling DHCP requests for all VLANs.

That goes against my current understanding which could easily be incorrect since I started with this equipment a few days back.

I have ER605, 2x SG2008 (actually one of them is a P), OC200, EAP245.

After going through the steps of FAQ 3091 (minus the ACLs for now), I have a few VLANs.

The reason I was under the impression that the gateway handled all DHCP requests across all VLANs is three-fold:

• The router properties includes a tab called Networks, which doesn't exist for my switches.
  
• The LAN Interface creation UX includes a selection of ports to be included that match ports of the gateway only (WAN/LANx & LAN).
• In case switches were connected to several of the gateway's LAN ports, and a VLAN spanned more than one of these ports, which switch would handle DHCP?
  It seems desirable to centralize on a single device...

Or maybe something changed since your replies earlier and now.

@John1234 

Actually, per Omada SDN Controller User Guide | TP-Link, during network creation:

The gateway/router seems to be hosting the DHCP server for each network.