Problem with EAP 225-Wall (DHCP)
Hi,
I think there is a thread about a 225-Outdoor with the same problem... but I'm not 100% shure.
I'm using Vlans with this AP configured with omada controller software. The switch is configured with 2 vlans (vlan 1: untagged (management via omada and office workers), vlan 2: tagged (Guests)). Guest network is ok but on office wifi I don't get a ip.
I tried a lot of things also reconfiguring my switch and ended up that if both vlans are untagged on the port dhcp on office wifi works but omada controller looses connection to the ap. So it seems that there is a problem with the EAP225-Wall software.
Did anyone of you solve this?
Thank you in advance
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
In our case the solution was to switch off "Wireless VLAN" in the Wireless section of Omada Controller because our Vlan1 is untagged and pvid on the switch ports of the APs (Just found out four weeks ago by trying it again).
What I don't understand is why this (mis)configuration worked on all other APs and just showed up on the 225-wall. (I just plugged in a EAP115-Wall in the same port and it worked with the old config)
Now everything is working as it should also with the new config.
Thanks for all answers and the provided help, and sorry for not posting back that long.
Regards
Emanuel
- Copy Link
- Report Inappropriate Content
Hi @Emanu,
Where is your DHCP "server" located? Is it in your router, part of a layer-3 switch / VLAN config, or a stand alone service on linux or windows? Does the DHCP "server" have access to both VLAN's? Are you hosting separate subnets or separate ranges for each VLAN?
Is this a new install or did you have pre-existing AP's working with this config? Are there other AP's (aside from the Wall unit) on each of these VLAN's that are working correctly?
-Jonathan
- Copy Link
- Report Inappropriate Content
Thanks for your reply.
First of all: Yes we have 9 EAP Accesspoints which work in this config. Only the new bought 225-Wall APs have this issue.
We have two DHCP servers as the work and guest networks also have an individual Internet connection. Work network is handled by a Windows Server DHCP and guest is handled by the second router. They also have separate subnets.
Emanuel
- Copy Link
- Report Inappropriate Content
Hi @Emanu,
Thank you for the added detail. @R1D2 or @Jonas may have a suggestion, but you'll probably want to submit an actual support ticket with TP-Link support since this sounds like it could be a firmware bug with this model.
-Jonathan
- Copy Link
- Report Inappropriate Content
@Emanu, please post the config settings. What VLAN does the »office« WLAN use? How is the Windows server connected, over a trunk? What are the switch settings? How do you separate the broadcast domains on Windows / on the switch?
Without those informations it's hardly possibe to help.
- Copy Link
- Report Inappropriate Content
Is there any solution available? I have the same problem.
My config:
-Fritzbox 7490 defualt lan on port1, guest-lan on port 4
-cisco sg200 with vlan 1, 10 and 11 (1 and 11=default, 10 = guest)
configuration works fine with TL-WA801ND or EAP115 controlled via OC200
EAP225 (diffrent versions) doesn't work proper, not via OC200 and not alone.
guest vlan-ssid (10) works well, on vlan-ssid 1 and 11 I don't get any ip-adress. The other APs (TL and EAP115) work well on the same switchport. So I don't have any idea what could be wrong with the switch configuration.
When I delete ssid10 and switch disable vlan for ssid 1 it works.
FW is 5.0.0 on all device ex. TL-WA
Regards
Ralph
- Copy Link
- Report Inappropriate Content
In our case the solution was to switch off "Wireless VLAN" in the Wireless section of Omada Controller because our Vlan1 is untagged and pvid on the switch ports of the APs (Just found out four weeks ago by trying it again).
What I don't understand is why this (mis)configuration worked on all other APs and just showed up on the 225-wall. (I just plugged in a EAP115-Wall in the same port and it worked with the old config)
Now everything is working as it should also with the new config.
Thanks for all answers and the provided help, and sorry for not posting back that long.
Regards
Emanuel
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2170
Replies: 6
Voters 0
No one has voted for it yet.