CPE510 Rogue DHCP Issues and EAP115 Slow Throughput
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.CPE510 Rogue DHCP Issues and EAP115 Slow Throughput
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello TP-Link Communnity,
I have a head scratcher. At least it is for me. My Daughter's school was in dire need of a network upgrade to support this new schools year remote students. As part of the upgrade I added two CPE 510 (One in AP Mode and One in Client Mode) to extend the LAN network outside and to another building( less than 500 FT) not wired to the LAN. Additionally I added a EAP 115 inside the main building to replace an 5 year old Airport Extreme.
Initially everything seemed to be working fine. When I came back onsight, After a day of letting the network run without interference, the wireless connection became intermittent and the network thourput would vary significatly from 30 MBps to 300 MBps.
My Current Setup is:
WAN Port Eth0
Ubiqiti Edge Router 4
LAN Port Eth2
Netgear 24 Port Switch
CPE 510 AP
CPE 510 Client
Switch in 2nd Building
Also
Netgear 24 Port Switch
TP-Link 4 Port POE
EAP 115
It seems to me that the CPE 510 is acting as a rogue DHCP Server. Everytime I remove it from the network, everything behaves normally. When I plug it back into the switch I see this behavior when I ping the edge router.
PING <IP> (<IP>): 56 data bytes
64 bytes from <IP>: icmp_seq=0 ttl=64 time=6.537 ms
64 bytes from <IP>: icmp_seq=1 ttl=64 time=9.229 ms
Request timeout for icmp_seq 1787
Request timeout for icmp_seq 1788
Request timeout for icmp_seq 1789
64 bytes from <IP>: icmp_seq=1 ttl=64 time=9.229 ms
Request timeout for icmp_seq 1791
Request timeout for icmp_seq 1792
64 bytes from <IP>: icmp_seq=1 ttl=64 time=9.229 ms
Request timeout for icmp_seq 1794
64 bytes from <IP>: icmp_seq=0 ttl=64 time=6.537 ms
64 bytes from <IP>: icmp_seq=1 ttl=64 time=9.229 ms
64 bytes from <IP>: icmp_seq=0 ttl=64 time=6.537 ms
64 bytes from <IP>: icmp_seq=1 ttl=64 time=9.229 ms
Request timeout for icmp_seq 1799
Request timeout for icmp_seq 1800
Request timeout for icmp_seq 1801
Request timeout for icmp_seq 1802
Request timeout for icmp_seq 1803
Request timeout for icmp_seq 1804
THis is what lead me to think that the CPE510 was acting as a DHCP server. When I setup the device as a AP and when I logged into the Pharos UI to check the Device was set to have a Static IP from the WAN and DHCP was NOT enabled. I checked t se if the Static IP I Assigened was being shared with another device and it was not. I really don't know what to do here. My Thought is that Maybe I do not want the device to be an AP, but a repeater? I don't really know. What I do know is I need this device to work so that the Client 510 can bridge LAN to the other building. Any suggestions or Ideas would be greatly appreciated.
The other issue is that the EAP115 will not speedtest past 65 - 70 MBps download. I'v tested the speed wired itno th switch that the EAP is connected to and I get 250+ MBps on the switch with an ethernet connection. I'm not sure why the EAP 110 is slowing down the connection , but it is rated for 300MBps so Any thoughts hear wuld be helpfule as well.
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
JonathanSK wrote
1) My first question is how does a device decide which WAP to use? From my research this is based on detected signal strength and there is little I can do to affect that on the nework side correct? Some of the devices are prefering the outside signal to the inside signal.
2) How can I tell which AP I'm connected to if they share the sam SSID and they are bridging the LAN side of the network.
3) My third question is I am recieving low throughput connected to the Main Building 2.4 SSID when I'm inside the building. Any thought as to why the speeds might be intermittenty slow coming from the WAPs? I've tested wired into the switch and speeds remain stable 300/300 after the DNS fix, but connected to the AP I sometimes get 80/80 more often I get 3 to 4. Should I assign them static IPs? Could the Wifi signals be interfering with each other?
1) Client devices most often use signal strength, signal-to-noise ratio, available WiFi rates and maybe other parameters. You can't do much on the AP's side to influence this behavior.
2) You can check the BSSID (MAC address) of the AP to which the device is connected to.
3) 80 to 95 Mbps is maximum (full-duplex) throughput you can achieve over a 300 Mbps (half-duplex) wireless link of an N300 EAP. Actual throughput depends on many environmental influences and clients constantly negotiate a WiFi rate with an AP which allows for stable communication. Interferences such as caused by obstacles between client and AP or by reflections or by nearby WLAN / non-WLAN devices (DECT, Bluetooth, Zigbee etc.) can greatly reduce the throughput.
Yes, any stationary device such as switches or APs always should be assigned a static IP. Whether you assign those static IPs by DHCP MAC/IP mapping or by settings in the device doesn't matter, but there is no reason to assign stationary devices dynamic IPs through DHCP (except probably lazyness).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2528
Replies: 11
Voters 0
No one has voted for it yet.