May I close the Port 29810 once the Devices are adopted ?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Got 2 controllers in the same Lan.
-ver.3.x to manage EAP330 on external site
-Ver.4.x to manage SDN Devices, actually only devices inside same Lan of the site can be managed
Goal is to to manage Externals SDN devices with the controller ver.4.x.
Can I move my port forward 29810 from IP controller V.3.x to the IP Controller V4.X ?
Does the Device will keep they adopted/connected state on the v3.x controller ?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
The easiest solution was to use
- dual WAN from TL-ER7206
- 2 controllers with statics IP into same VLAN 1 by default
- NAT/virtual server corresponding ports controller#1 with WAN1 & ports controller#2 with WAN2 for remotes sites (both controllers see pending device if i connect a new one into the lan, just need to choose from wich one i start adoption procedure)
NO multi VLAN at all as the settings are much complicate to manage ports interfaces properties, especially if you mix another switch non tp-link or SDN compatible into your Lan.
I'm still facing many bugs from SDN and TL-ER7206, but i will open others threads for each of them.
- Copy Link
- Report Inappropriate Content
@Pascal Currently we can only use one Omada controller in one subnet. I will report your requirement to the related department.
Temporary solution:
If possible, use your Router/switch to build a multi-nets network. Then you can put the two controllers in different VLAN network.
- Copy Link
- Report Inappropriate Content
As there was no solution to create a second VLAN with my actual TL-ER6120 + TL-SG1016PE + TL-SG2008P
I ad purchased a second Router TL-ER7206 + TL-SG2428P
TL-ER6120 act as DHCP server for VLAN1 and NAT translate to controller 1 with Wan1 ip1 isp
TL-ER7206 Got VLAN1 interface without DHCP, VLAN2 with DHCP & VLAN3 with DHCP and Nat translate to controller 2 within VLAN3 WAN2 ip2 isp
All seems to working fine to access from outside the 2 controllers.
Now I'm pulling my airs to find a way to give communication between VLAN1,2 & 3.
despite the easy way for standalone switch & router configuration and try to replicate this with Omada SDN interface
I'm only able to communicate inside a same vlan between device.
It happened during my try to got issue with infinite Adopting situation with the TL-ER7206 that forced me to reset to factory and rebuild the config.
Is there a nice explain from TP-Link to setup multi VLAN that can communicate with each other like this one but for SDN GUI ?: https://www.tp-link.com/us/support/faq/887/
Also, in the latest update firmware TL-ER7206 i see: 10. In the Virtual Servers entry of the NAT module, support for adding multiple non-
consecutive ports
but i didn't found a way to add these non-consecutive ports into the port forwarding within the SDN controller...tried with 8043-8088 or 8043;8088 or 8043,8088
and 8043 8088
but none of these separators was admitted.
Cheers,
- Copy Link
- Report Inappropriate Content
Hi, if you'd like use the latest Omada SDN, that would be great.
Per your request, you can refer to this link about Multi-SSID setup on Omada UI.
How to configure Multi-Networks & Multi-SSIDs on Omada SDN Controller
If you use the controller, it follows the format below. Virtual server is the port forwarding name in standalone mode. If you use Controller, look for the port forwarding under the Transmission.
- Copy Link
- Report Inappropriate Content
The easiest solution was to use
- dual WAN from TL-ER7206
- 2 controllers with statics IP into same VLAN 1 by default
- NAT/virtual server corresponding ports controller#1 with WAN1 & ports controller#2 with WAN2 for remotes sites (both controllers see pending device if i connect a new one into the lan, just need to choose from wich one i start adoption procedure)
NO multi VLAN at all as the settings are much complicate to manage ports interfaces properties, especially if you mix another switch non tp-link or SDN compatible into your Lan.
I'm still facing many bugs from SDN and TL-ER7206, but i will open others threads for each of them.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 806
Replies: 4
Voters 0
No one has voted for it yet.