EAP 225 connect to trunk port on switch

EAP 225 connect to trunk port on switch

EAP 225 connect to trunk port on switch
EAP 225 connect to trunk port on switch
Tuesday - last edited Thursday
Model: EAP225  
Hardware Version: V3
Firmware Version: 5.1.6

Hi everyone.

 

I'm having difficulty getting the following situation to work:

 

I have a TL SG2428P switch, that is configured trough the webinterface, because when I adopted it in the Omada configuration, I found it a bit too difficult to get all my WLAN settings configured. When I did this with the built-in web interface, it worked easier for me.

 

On the switch I have configured port 21 as a untagged trunk port with Vlans 1(management), 20 (Lan), 60 (IOT) and 99 (Guest). I also have tried to set the port to tagged, but this also didn't work.

 

When I connect the EAP225 to this trunk port, the omada controller doesn't find the AP, when I connect it to a lan port directly it does. When I then, after configuring the AP WLAN SSID's, try to connect it to the trunk port, It just doesn't seem to work, I get the SSID's in my wireless device, but I don't get a IP from the DHCP server in that selected WLAN range

(10.10.10.x - 10.10.20.x - 10.10.60.x - 10.10.99.x)

 

Do I actually have to have the switches adopted in the omada controller for this to work? Am I missing something else?

 

If anyone needs more information, happy to oblige.

  0      
  0      
#1
Options
1 Accepted Solution
Re:EAP 225 connect to trunk port on switch-Solution
Tuesday - last edited Thursday

Hi  @Houseofdreams_ 

 

You're not required to use the controller for everything, but once you get past a little learning curve I think you'll like it.  Regarding your specific issues...

 

Adopting the AP: Put the Controller and AP on the same VLAN. If it finds the AP when connected to a "lan" (vlan 20) port, then your controller is likely also on vlan 20.  Both the controller and AP should be untagged members of the same vlan and also have the same PVID (native vlan) value.

 

WLAN-VLAN Mapping: All SSID's mapped to a VLAN would need to have those vlans as tagged members on the AP's port.

 

Assuming you want to put the controller and AP in the management vlan 1...

  • Port 21 should have vlan 1 untagged, with PVID set to 1; vlan 20, 60 and 99 are tagged.
  • Port X (where controller is installed) should have vlan 1 untagged, with PVID set to 1

 

 

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:EAP 225 connect to trunk port on switch-Solution
Tuesday - last edited Thursday

Hi  @Houseofdreams_ 

 

You're not required to use the controller for everything, but once you get past a little learning curve I think you'll like it.  Regarding your specific issues...

 

Adopting the AP: Put the Controller and AP on the same VLAN. If it finds the AP when connected to a "lan" (vlan 20) port, then your controller is likely also on vlan 20.  Both the controller and AP should be untagged members of the same vlan and also have the same PVID (native vlan) value.

 

WLAN-VLAN Mapping: All SSID's mapped to a VLAN would need to have those vlans as tagged members on the AP's port.

 

Assuming you want to put the controller and AP in the management vlan 1...

  • Port 21 should have vlan 1 untagged, with PVID set to 1; vlan 20, 60 and 99 are tagged.
  • Port X (where controller is installed) should have vlan 1 untagged, with PVID set to 1

 

 

Recommended Solution
  0  
  0  
#2
Options