Business Community > WiFi > eap225 outdoor (with oc200) - clients can't get DHCP ip address
< WiFi

eap225 outdoor (with oc200) - clients can't get DHCP ip address

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

eap225 outdoor (with oc200) - clients can't get DHCP ip address

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
eap225 outdoor (with oc200) - clients can't get DHCP ip address
eap225 outdoor (with oc200) - clients can't get DHCP ip address
2019-09-09 13:58:35
Model: EAP225-Outdoor  
Hardware Version:
Firmware Version:

I have a problem with the eap225 outdoor. I have two eap225 v3 models that have been working great with the oc200 Omaha controller.

 

i just got the eap225 outdoor. When I adopt it into the Omaha cluster, any client connected to it can’t get an IP address. They can get an ip address no problem when connected to either of the other access points. If I drop the eap225 outdoor out of the cluster and give it its own sid, clients can get an IP address just fine. it just doesn't work when it's in the omada cluster

 

is this a known issue?

 

will it be addressed in the next firmware release?

 

 

  0      
 
  0      
 
#1
Options
4 Reply
Re:eap225 outdoor (with oc200) - clients can't get DHCP ip address
2019-09-10 01:23:10

Hi,

 

We have never received such feedback. Here are some suggestions for you to have a try.

1. Please check if you have managed the EAP successfully. Normally when we manage the EAP successfully, we will see the AP in the "Connected".

2. When the Omada Controller manages the EAP, please check if the EAP gets an IP address successfully. 

3. When the client devices connect to the EAP, can you see the client status in the Omada Controller?

 

 

  0  
  0  
#2
Options
Re:eap225 outdoor (with oc200) - clients can't get DHCP ip address
2019-09-13 13:00:25 - last edited 2019-09-13 13:03:27

@forrest 

 

i've done some more experimenting. 

  • with a wired connection to the outdoor ap, clients will briefly show as connected, but they don't get an IP address and drop and show as not connected in omada.
  • with a mesh connection to the outdoor ap, everything works properly.

 

Though it is working with a mesh connection, i'd much prefer the wired backhaul. I'll keep things in a mesh connection until a fix for this is included in a new version of the firmware.

 

one more piece of information, with the wired connection to the outdoor ap, setting the client to a manual ip didn't even work.

  0  
  0  
#3
Options
Re: eap225 outdoor (with oc200) - clients can't get DHCP ip address
2019-09-13 13:30:32 - last edited 2019-09-13 13:42:05

 

BigEric wrote

@forrest 

 

i've done some more experimenting. 

  • with a wired connection to the outdoor ap, clients will briefly show as connected, but they don't get an IP address and drop and show as not connected in omada.

 

There is definitely a problem with your cabling or with your network setup if you use VLANs.

 

Our customers use EAP225-Outdoors wired to an Omada controller running on OC200 or running on servers without any problems. Clients get an IP and won't be disconnected until they disappear. Look at the "Active time" column (last one):

 

 

 

You wrote the EAP225-Outdoor works when meshed. I suggest to check your cable for loose contacts. Also make sure to use properly shielded cables and grounding as required for any outdoor device.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re: eap225 outdoor (with oc200) - clients can't get DHCP ip address
2019-09-13 15:08:11

@R1D2 

 

Thanks for the tip. I had a vpn configuration problem. Working great now.

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 3620

Replies: 4

About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.