This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.cannot change subnet in LAN via controller page
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
on the tab settings > wired networks > LAN there is a subnet that probably cannot be changed?
it is 192.168.0.1/24, but i want it to be 192.168.2.1/24.
how can i change this?
also cannot do controller settings in settings via software, while being logged in as master administrator?
what went wrong?
please advice.
Walther from the Netherlands
with OC200 and 3 EAP225's connected and trying to see my new TL-R600 safestream
Dear @walther,
If your router is TL-R600VPN, then the Omada SDN controller cannot see it because TL-R600VPN doesn't support the SDN platform.
For the LAN IP address of the network, you could access the web management page of the TL-R600VPN router to change it.
Do you mean the greyed out "Controller Settings"?
Note that Settings has two parts: Site Settings and Controller Settings. There are several submenus under the two parts.
So Controller Settings includes the settings for Controller, Cloud Access, Maintenance, Migration and Auto Backup.
What's visible under »Wired Networks« is a default LAN. But unless yo have a SDN-capable gateway it is completely irrelevant to the actual setting of a non-SDN gateway (whatever model, even from different vendors).
When Omada Controller manages a SDN-capable gateway, the »Create new LAN« menu changes dynamically.
It will allow to set the network IP range for a new network as well as let you change the existing default LAN settings:
Unless you have a SDN-capable gateway, the whole »Wired Network« settings are ignored by the Controller.
In case of TL-R600 you can set the network IP directly in the gateway, but not in SDN Controller.
In my opinion all menus and settings which are not applicable when no SDN gateway/switches are detected should be hidden. I already did suggest this to TP-Link R&D. Showing menus which are not applicable confuses users, so TP-Link should really consider this suggestion. It would also take away ballast from Omada Controllers which are intentionally used to only manage EAPs, but not switches and a gateway. Dear Fae, maybe you can add this suggestion again since you can see that those menus confuse so many users.
Dear @walther,
If your router is TL-R600VPN, then the Omada SDN controller cannot see it because TL-R600VPN doesn't support the SDN platform.
For the LAN IP address of the network, you could access the web management page of the TL-R600VPN router to change it.
Do you mean the greyed out "Controller Settings"?
Note that Settings has two parts: Site Settings and Controller Settings. There are several submenus under the two parts.
So Controller Settings includes the settings for Controller, Cloud Access, Maintenance, Migration and Auto Backup.
What's visible under »Wired Networks« is a default LAN. But unless yo have a SDN-capable gateway it is completely irrelevant to the actual setting of a non-SDN gateway (whatever model, even from different vendors).
When Omada Controller manages a SDN-capable gateway, the »Create new LAN« menu changes dynamically.
It will allow to set the network IP range for a new network as well as let you change the existing default LAN settings:
Unless you have a SDN-capable gateway, the whole »Wired Network« settings are ignored by the Controller.
In case of TL-R600 you can set the network IP directly in the gateway, but not in SDN Controller.
In my opinion all menus and settings which are not applicable when no SDN gateway/switches are detected should be hidden. I already did suggest this to TP-Link R&D. Showing menus which are not applicable confuses users, so TP-Link should really consider this suggestion. It would also take away ballast from Omada Controllers which are intentionally used to only manage EAPs, but not switches and a gateway. Dear Fae, maybe you can add this suggestion again since you can see that those menus confuse so many users.
Walther, you're welcome. Now perhaps one question remains, I'll add this for completeness:
Why can one create a wired network at all and define a VLAN even if there is no SDN-capable gateway/switch?
Because when you use a Management VLAN you need to select the VLAN in the EAP device settings using a selection box (under »Services«):
This is the only use case for the »Wired Networks → LAN« menu when non-SDN gateways/switches are being used.
Would I have to decide about the user interface, I would have used a numerical input field as it appears in »Wireless Networks« when you map a SSID to a VLAN. Then, the »Wired Networks → LAN« page could be disabled completely as is the »Wired Networks → Internet« page.
What's more, having a numerical input field for VLANs in »Wireless Networks«, but a selection box in Management VLAN settings (which requires definition of a new network elsewhere) is an inconsistency, which can also confuse users. But developers usually think differently than users and this is not necessarily always advantageous.
