EAP653 is not able to give an IP if the VLAN is configured on a WLAN

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

EAP653 is not able to give an IP if the VLAN is configured on a WLAN

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
33 Reply
Re:EAP653 is not able to give an IP if the VLAN is configured on a WLAN
2024-01-23 08:04:34

Hi @nicolati,

 

That's great! Please feel free to reply to the support email for further follow-up.

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]*
  0  
  0  
#32
Options
Re:EAP653 is not able to give an IP if the VLAN is configured on a WLAN
2024-01-26 20:55:22

  @nicolati 

Hi all,

let me add one relevant point to the discussion, meanwhile I'm directly working with the TP-Link support.

The DHCP Server is the Router (ER605 V2) one, not the Switch one, when everything is connected through the Omada Controller.

 

Moving the EAP directly connected to the router doesn't solve the issue.

 

A partial solution is reserving the IP into the DHCP Server and also binding the IP to MAC and then reboot, but this doesn't work always.

 

Thank you,

Fra

  0  
  0  
#33
Options
Re:EAP653 is not able to give an IP if the VLAN is configured on a WLAN-Solution
2024-02-02 23:21:31 - last edited 2024-02-05 01:16:21

  @nicolati 

Hi all,

I discovered the issue by chance!

 

The problem is the Static Routing!!!

 

When I created the VLANs, the Controller created me a Static Routing, one for each VLAN, like:

192.168.10.0/24 --> 192.168.0.1

192.168.20.0/24 --> 192.168.0.1

192.168.30.0/24 --> 192.168.0.1

192.168.40.0/24 --> 192.168.0.1

 

This prevented the DHCP Server working properly when VLAN ID is assigned to a WLAN.

 

However, as far as I know, Static Routing are needed to make the routing part of the system working correctly, otherwise it doesn't know how to answer to packets.

So, it looks a bug to me, but I'm still in touch with TP-Link support for this.

 

I'll keep this thread updated.

 

Thank you,

Fra

Recommended Solution
  0  
  0  
#34
Options
Related Articles