Business Community > Routers > DHCP address reservations for Clients - multiple VLANs and subnets
< Routers

DHCP address reservations for Clients - multiple VLANs and subnets

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

DHCP address reservations for Clients - multiple VLANs and subnets

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
DHCP address reservations for Clients - multiple VLANs and subnets
DHCP address reservations for Clients - multiple VLANs and subnets
2022-04-16 20:42:54
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2

Our environment is one ER605 connected to two SG2008s with an OC200 controller.  We also use multiple VLANs - LAN/GUEST/SERVER/IOT/LOT with different IP address ranges.

 

We were having trouble setting Fixed IP Addresses in the config screen for clients. The application seemed to require an IP reservation in the same subnet to which the ER605 belonged, even though the client had (and properly needed) an IP address for a different VLAN/subnet.

 

The work-around to get a Fixed IP Address was to change the Network/VLAN in the config drop-down, followed by changing the Network back to the correct Network/VLAN, and then finally the application accepted a Fixed IP Address in the proper Network/VLAN without error.

 

 

  0      
 
  0      
 
#1
Options
2 Reply
Re:DHCP address reservations for Clients - multiple VLANs and subnets
2022-04-18 06:24:21

To all,

 

Yes, it is designed to be like that, you need to choose the correct Network first:

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  1  
  1  
#3
Options
Re:DHCP address reservations for Clients - multiple VLANs and subnets
2022-04-21 03:42:13

  @Hank21 

 

Thanks very much for the reply.

 

In my case the clients in question were joined to subnets other than LAN/default native. Therefore, when the Config menu is accessed the Network dropdown is not empty as in your screenshot. In my case the clients Config menu was pre-populated with IOT (or another appropriate Network). At that point it looked like I could key in an IP address appropriate to that Network/subnet and Apply. However, the masking/error checking on the IP address was apparently still set on the LAN subnet and therefore generated an error when keying an IP address for the Network which was displayed in the drop down.

 

The solution to allow the correct IP to be entered was select any other Network, reselect for the correct Network (which was originally displayed), and then the masking/error checking on the IP address is apparently updated to the proper subnet and the IP address in that subnet can be applied.

 

Thanks again for your reply.  

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 458

Replies: 2

About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.