Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 13 of 13
  1. #1

    Exclamation CPE 210 (V1) Wifi Repeater works fine, after about 48 hours no wifi network available anymore

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Hello together,

    at first the details:

    Model : CPE210

    Hardware Version : V1

    Firmware Version : 1.3.3 xy, now updated to TP_PharOS_2.0.0_170301

    Powered with PoE-Power-Adapter with shielded cable RJ45.

    As mentioned in the title, after starting the device everything works fine. The CPE210 in repeater mode connects to the configured wifi. Everything works fine for about 48 hours. Suddenly only the power led is on, no more wifi network activity. Rebooting the CPE210 via browser or by unplugg/plugg the PoE-Cable let the device work again for another approx. 48 hours.

    Does anyone has any suggestion?

    Many thanks in advance

  2. #2
    What's your detailed topology? Actually, repeater is not recommended mode for CPE as I know.
    Since CPE concentrates wireless signal in a direction, which means the signal in backward is not very strong. So actually it can not bridge signal much further...

    Anyway, for your issue, would reboot schedule function on pharos control be a workaround for you?

  3. #3
    Hello ZaiZai,
    thanks for your reply.
    The Topology just contains a router with wifi and the CPE210 for wifi range extension.
    I did not used pharos control yet. The CPE210 is not connected to LAN via cable.
    Is the reboot schedule function a configuration option for the CPE210 itself or do i have to establish a permanent connection between pharos control and the CPE device?

  4. #4
    This isn't about topology
    Repeater mode works like that ever
    Buy a timer and reboot every 24 hrs
    Or go the hard way, leave a Laptop 24/7
    And use Pharos Control and set auto reboot
    Or go to the limit, flash Lede install the interface,
    Use Cron 0 3 * * * reboot that will reboot everyday at 3 am

  5. #5
    Are we really suggesting that repeater / bridge mode on these CPEs works as such (i.e. expires every 48hrs)!?

  6. #6
    i have tplink cpe 210 repeaters and what i know is that if you do a restart on the repeater you should also do restart on the main router.Also make sure your repeater settings are in order i.e disable dhcp settings,wds

  7. #7
    Quote Originally Posted by RTouris View Post
    Are we really suggesting that repeater / bridge mode on these CPEs works as such (i.e. expires every 48hrs)!?
    Not at all. Repeater mode is just another combination of client/AP mode, which is a mixed STA/Master mode of the WiFi adapter, pretty much like in bridge and AP client router modes. It's not supposed to "expire" after some time.

    But repeater mode often is the cause for problems of any kind, most notably the hidden node problem and degradation of the link's overall throughput, the latter by nature of this technique.

  8. #8
    Quote Originally Posted by RTouris View Post
    Are we really suggesting that repeater / bridge mode on these CPEs works as such (i.e. expires every 48hrs)!?
    Buy one, use Repeater mode
    If you have no issues after 48 hrs.
    Bill me
    Same device, or even a cheap router like 740, flash it with any third party firmware, DD-WRT, OPENWRT, Gargoyle or Lede, and will work on Repeater mode 24/7
    The Point, Tp-Link hardware has no issues
    It's the software.

  9. #9
    It's a pitty, that this is still a software problem because the device is sold to be able to be used as repeater.
    Maybe a later software version will solve this problem.

    Many thanks, using a timer to reboot would be a useful solution.

  10. #10
    Quote Originally Posted by volker71042 View Post
    It's a pitty, that this is still a software problem because the device is sold to be able to be used as repeater.
    Maybe a later software version will solve this problem.

    Many thanks, using a timer to reboot would be a useful solution.
    I did set up a CPE yesterday in repeater mode, routing complete traffic from my office over it. So far, there are no problems after 27 hours.

    Lets see wether this can be re-produced on other CPEs. Tomorrow we will know.

    Just a question: do you use DHCP on the repeater or did you set up a static IP? We had many problems with repeater mode on OpenWRT devices when DHCP was used. Since PharOS uses the same software base (Linux) as OpenWRT does, changes are that this could be the cause of problems with disconnects.

    And no, a reboot is not considered a bug fix in the Linux ecosphere.
    Last edited by R1D2; 05-15-2017 at 12:38.

  11. #11
    As a half-baked remedy you could try setting up a ping watchdog rule on the repeater-CPE to ping the AP's IP and reboot when it fails to get 2-3 replies after 5 mins each (given that it probably doesn't get one due to whatever reason makes it act up on the first place).

    FWIW I've recently setup a CPE510 in bridge mode but after 3 days uptime have yet to experience these specific ill-effects.
    Last edited by RTouris; 05-15-2017 at 20:53.

  12. #12
    Two days have passed, CPE still working fine in repeater mode. No issues whatsoever.

    Name:  Untitled.png
Views: 0
Size:  113.3 KB

    No errors or warnings in SYSLOG, WiFi network did also not disappear. AP is running fine:

    Code:
    # 80211stats
    4067 rx w/ wrong direction
    39 rx discard 'cuz sta !assoc
    172 rx discard mgt frames
    1013 rx discard ctrl frames
    31 rx required element missing
    6505 rx frame ssid mismatch
    469 rx assoc from wrong bssid
    2 rx action mgt
    30184 tx failed for no node
    	**** 80211 unicast stats **** 
    718144 frames successfully transmitted 
    2306937513 frames successfully received 
    718130 rx w/ incorrect keyid 
    62 rx decrypt okay 
    11330 rx TKIP countermeasure activation count 
    	 **** 80211 multicast stats ****
    4451 frames successfully transmitted 
    1552666 frames successfully received 
    76 rx w/o wep and privacy on 
    4451 rx w/ incorrect keyid 
    5 rx ICV check failed (TKIP) 
    11 rx seq# violation (CCMP) 
    950 tx dropped by NIC 
    0 rx TKIP countermeasure activation count 
    #

  13. #13
    Many thanks for your replies.
    Setting up a watch dog rule is the solution within the software i was looking for.
    Thx


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.