CPE510 issue with WPA
I am trying to set up a point-to-point wireless bridge using CPE510.
Everything works fine except for one thing. The issue is that when encryption is enabled, the devices fail to connect.
Even when the two devices are directly facing each other, they still do not connect, so it seems like it's not a distance or interference problem. Of course, when encryption is disabled(It means "Security Mode" is set as None), the connection is established immediately.
An interesting point is that when I repeatedly power cycle the devices, they sometimes connect, but this is very rare.
I have tried various methods like disabling DFS channels, turning off MAXtream, and so on, but the issue persists.
I found a forum thread with a similar problem.
https://community.tp-link.com/en/business/threads/topic/645304
What should I do?
Thank you.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
To build a wireless bridge with two CPE510, we need to manually configure them, one as access point mode, and the second configure as client mode.
When configure the client mode, you need input the SSID & password info of the access point mode.
That is to say, if you change the encryption of the access point, you need to login to the client interface and input the password again. Did you do these?
Below are some guides for your reference:
How can I set up the AP + Client topology successfully?
- Copy Link
- Report Inappropriate Content
It seems that there is a misunderstanding due to the translator.
I don’t think the issue is distance. Even though the two devices were tested indoors with a 1-meter gap, the same result was obtained. They are now installed about 300 meters apart, and the signal strength is showing -54 / -56.
After many tests, although not precise, I was able to find a slight workaround. It’s not certain, but I hope it helps other users.
-
First, the AP should not use Auto for the channel. In the case of Auto, it seems to run some background tasks, that may cause delay.
-
After changing the wireless settings on the AP (include encryption, channel, ssid, etc), the client side needs to be rebooted. Changing the configurations causes the connection to be lost, I assume that the client memorize some kinds of "fail" state, when in this state, client does not try connecting immediately after connection lost.
-
Based on the 2, the client’s power should be turned on only after the AP’s power is completely on.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
To build a wireless bridge with two CPE510, we need to manually configure them, one as access point mode, and the second configure as client mode.
When configure the client mode, you need input the SSID & password info of the access point mode.
That is to say, if you change the encryption of the access point, you need to login to the client interface and input the password again. Did you do these?
Below are some guides for your reference:
How can I set up the AP + Client topology successfully?
- Copy Link
- Report Inappropriate Content
Hello, Thanks for your reply.
I did not read that article in detail, but in my configuration, the two devices are actually connected "rarely" when encryption is set as WPA-PSK.
so "ping" was successful across each CPE510 devices. The problem is, it really only "rarely" connected regardless of distance between devices.
Is there any method for grabbing some logs from device?
Thank you.
- Copy Link
- Report Inappropriate Content
No logs.
So the issue is: the wireless bridge can connect, but it will disconnect?
Please refer to the following link to make sure they are properly installed:
Long distance wireless connection concerns when using outdoor access point
- Copy Link
- Report Inappropriate Content
It seems that there is a misunderstanding due to the translator.
I don’t think the issue is distance. Even though the two devices were tested indoors with a 1-meter gap, the same result was obtained. They are now installed about 300 meters apart, and the signal strength is showing -54 / -56.
After many tests, although not precise, I was able to find a slight workaround. It’s not certain, but I hope it helps other users.
-
First, the AP should not use Auto for the channel. In the case of Auto, it seems to run some background tasks, that may cause delay.
-
After changing the wireless settings on the AP (include encryption, channel, ssid, etc), the client side needs to be rebooted. Changing the configurations causes the connection to be lost, I assume that the client memorize some kinds of "fail" state, when in this state, client does not try connecting immediately after connection lost.
-
Based on the 2, the client’s power should be turned on only after the AP’s power is completely on.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 104
Replies: 5
Voters 0
No one has voted for it yet.