DHCP Question(s) / Cloud Adoption TL-ER7206 Router and OC200 Controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I am (trying) to migrate from an old router, which has ~130 entries in the DHCP reservation table. And a router LAN IP of 192.168.1.1
In standalone mode, I patiently migrated these manually (2+hrs) to the ER7206. This worked just fine.
However, I only spotted that the OpenVPN support is via the OC200 controller, so I bought one of those and tried to adopt the ER7206.
For reasons I do not understand, it changed the IP address of the router to 192.168.0.1 (default) and then failed.
I tried to access the router directly (standalone network) on the 192.168.0.1 address but it said it was now cloud-managed, so i added the controller to this standalone network.
Poof. All of the DHCP reservations are gone (they were in the 192.168.1.2-254 range obvs). BAD :-(
Now .. assuming that I can actually make this work in the cloud-managed configuration ..
1) How do I reserve DHCP address in the way I did in standalone mode. I don't see this anywhere. Is it hidden or just not there.
2) How do I actually see the DHCP reservations at *all*. I also don't see this.
3) Is there *any* DHCP reservation process supported in this configuration?
Thanks all.
Pat
Hey
1) How do I reserve DHCP address in the way I did in standalone mode. I don't see this anywhere. Is it hidden or just not there.
The only way to set a manual reservation is by selecting the device itself and under CONFIG enable use fixed IP
2) How do I actually see the DHCP reservations at *all*. I also don't see this.
Yeah its not there sadly, really should be a list of DHCP and Reservations somewhere on the SDN. This has been mentioned a few times by forum members (myself included) and I am lead to believe its on the radar for a future release version.
3) Is there *any* DHCP reservation process supported in this configuration?
See answer 1.. its there but not clear or easy.. totally agree!
Hey
The adoption process is totally controlled by the SDN, therefore anything you set in local mode will be removed in favor of the SDN config. So basically yeah its destructive, granted ive never tested DHCP reservations specifically, but cant see why it would be any different
The 192.168.0.1 thing you mentioned is again the controller setting, it defaults to that upon adoption but you can change it via the SDN. We all had that before! If memory serves me right, changing the LAN interface IP in the SDN is the way round that...
