CPE210 Frequent dropouts?
This is a point to point link between two buildings. It is approx 300m and line of sight. Problem is that the link drops perhaps once a minute. I have a ping runing for a computer at the other end. Most of the time the ping replies in 2-3ms, but occasionally it goes up to over a second and sometimes there is a complete break for 5..10s. When there is a break the Web UI for the closest CPE210 (slave) is unresponsive and does not reply to pings.
The link is configured as 802.11n, 20/40MHz, MCS 15 and MaxStream enabled.
Have tried almost every channel, currently on 11, noise -95dBm, S/N 44dB and quality between 80..100%
Servers -- CP201_Access_point ---air----CP210_Client---switch----Me
Any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@R1D2 OK. Thanks. I simply did not understand how it was supposed to work. I thought that changing the settings on the "master" (AP) would propagate to the Client. I have changed that now. I also changed to 40MHz fixed. Will test 20MHz again, this time changing both sides, but will do so after hours. I will also try changing to Auto.
I do have AES enabled:
- Copy Link
- Report Inappropriate Content
@AndersG, the optimization of using fixed parameters is just to avoid too much negotiation between the two CPEs which happens all the time if using alternative modes (e.g. b/g/n, channel width, key/cypher types etc.). That's not need for a PtP link, so just choose best settings on both CPEs.
- Copy Link
- Report Inappropriate Content
@R1D2 It has been stable for several days, but today it acted up again. When it happens, the CPE210 closest to me stops responding to pings as well. This clearly indicates something else is amiss.System log on unit has no entries and it shows an uptime of several says so it does not seem to be rebooting.
- Copy Link
- Report Inappropriate Content
AndersG wrote
When it happens, the CPE210 closest to me stops responding to pings as well. This clearly indicates something else is amiss.
I think the problem is elsewhere in your network if the CPEs suddenly can't be reached. On our directional links CPEs are running for years now w/o such disconnects. It's hard to find such errors in a network, could be a bad cable, mis-configured system somewhere using the same IP or a table overrun in a switch etc.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello,
exactly that action solved, as well, my conectivity problem. TPLINK should take a look into the topic and issue a firmware correction ... my network started to degradate after several hours (I even substitued one of my CPE210 by the latest V3.20); I tried everything that I could think about and no postive effect.
I was very close to drop TPLINK as a brand until I saw this hint! And it solved ...
But I see that the FW is still no solving it ...
Everytime it occurred I had to change something on the WiFi seetings and it would recover until ... some hours in the future. Quite anoying!
Here the latest:
So you can have an idea, this was the multiple effect:
I do think that TP-LINK must investigate what is going on. I am willing to send you all the config from the base AP, the client AP (ver 3.0) upgraded to the open-wrt OS (that unfortunatly doesn't exist, still for the version 3.2)
Thank you AndersG
To TP-LINK: should try to do it better, or please support other sw initiatives like openwrt ... to support your good HW.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6158
Replies: 27
Voters 0
No one has voted for it yet.