Adopting TL-ER7206 to an 192.168.68.x network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Adopting TL-ER7206 to an 192.168.68.x network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Adopting TL-ER7206 to an 192.168.68.x network
Adopting TL-ER7206 to an 192.168.68.x network
2021-05-19 17:18:04
Model: ER7206 (TL-ER7206)  
Hardware Version: V1
Firmware Version: 1.01

Just received the TL-ER7206 to replace a non-omada router in my existing SDN network. I am running the latest controller and firmware, and my native network is 192.168.68.0/24.

 

Trying to adopt the router causes chaos, for starters I cannot specify my 192.168.68.0 network, a fixed IP on the LAN and it starts with a DHCP server enabled.

 

How do I integrate this device into an existing network?

  0      
  0      
#1
Options
5 Reply
Re:Adopting TL-ER7206 to an 192.168.68.x network
2021-05-19 19:40:39

@phillip_mcmahon 

 

Try this guide at the beginning of the following link and it might help to read through the comments.  Link

  1  
  1  
#2
Options
Re:Adopting TL-ER7206 to an 192.168.68.x network
2021-05-19 22:11:33

@1207 

 

yep, I read it and I don't have the option of rigging the address of the controller as I am running this on docker. I see no other officially supported way, and trying the timing hack to get the config on is not what I expect for such basic config. Funny that no one from product management assumed we all aren't using 192.168.0.1/24 as our network...

 

I would rather @tplink announce something workable and that doesn't involve messing around with kludges.

  0  
  0  
#3
Options
Re:Adopting TL-ER7206 to an 192.168.68.x network
2021-05-19 23:20:22

@phillip_mcmahon 

 

Yes, they need to release an update to allow an easy path for the router to be added to an existing network.  Is it that hard to change the controller's IP address in a docker?  My controller was running in a Linux VM container and it was just two clicks and type in the new IP address.  I was able to isolate the controller and change its IP address,  adopt the router, change the IP addresses to the desired range, and then adopt the other switches and EAPs in 15 minutes. Later I bought an OC200 mainly because it was much easier to update and didn't have to leave the VM container running 24/7.

  0  
  0  
#4
Options
Re:Adopting TL-ER7206 to an 192.168.68.x network
2021-05-20 06:57:04

@1207 

 

Changing my current docker controller IP requires a change of its hosting platform IP, not going to mess around to do that. Or I could set up a macvlan to expose the container directly etc. It's easier to spin up my OC200 and start a new controller off and re-adopt and set up my devices again. Which of course isn't tough just a pain, takes time and involves downtime on the network, but it's total crap to expect people to have to frig around with their existing networks, simply to add an Omada SDN router into the mix.

  0  
  0  
#5
Options
Re:Adopting TL-ER7206 to an 192.168.68.x network
2021-05-24 11:29:56

When I first bought my 7026 I connected it to a pc with no network, made the changes needed and installed it on my network. Thsi approach worked fine till I tried to adopt the router using the OC200 controller. The controller erases everything and resets the network at 192.168.1.x.

The only solution for my was to reset both the router and controler to factory defaults and connect them to the non network pc. Then I entered the router to find the ip of the controler and used the controler to make all the changes needed and adopt rhe router. After that  I changed the ip range of the lan, the ip of the controler and reseted the network of the pc to get a new ip.

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 1482

Replies: 5

Related Articles