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

    Exclamation Archer VR2800v constantly crashes (about every 2-4h)

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Hello everyone, hello TP-Link team,

    I bought the new Archer VR2800v.

    From the functionalist view, I'm very happy with this router, but sadly it seems to have a big issue:

    The router constantly crashes (about every 2-4h). I have no idea why. Also after the crash, the systemlog seems to restart (at the point after the crash), which prevents me to see whats the cause of this.

    Firmwareversion:1.1.0 0.9.1 v006d.0 Build 170502 Rel.72641n
    Hardwareversion:Archer VR2800v v1 00000000

    It would be very kind, if you could help me. I don't wan't to send it back, cause it's such a nice piece of hardware :-)


    Kind regards from Germany

    the-essay

    PS: Please let me know, if you need some more informations. Also I'm willing to try some beta firmware, if this could solve the problem.

  2. #2
    My recently purchased AC2800 (VR2800) has the following:

    Firmware Version: 0.2.0 0.9.1 v006c.0 Build 170110 Rel.33619n
    Hardware version: Archer VR2800 v1 00000000

    And when I check in the Advanced > System Tools > Firmware upgrade it says this is the current version.

    I have no crash issues with my UK model, which seems to be running on older firmware than yours so maybe the new version has some bugs?

  3. #3
    This is the software-version the router was delivered with. Therefore I can't downgrade or something like that.
    Maybe the TP-Link Support Team knows the answer.

  4. #4
    You are right as looking at the German site i see the firmware you have is the current version.

    The only suggestion I could make would be to perform a factory reset and set up again from scratch.

    Mine has been very stable so I hope it is not a bug that will be introduced with newer firmware!

  5. #5
    I think you don't have the same router. It's the VR2800v<---

    Is there any official TP-Link Support?

    By the way, I now could see the log:

    2016-01-01 01:00:33 [5] VoIP: DECT base firmware build time 0329, build version 3630, RFPI 02 8A 66 E8 E0
    2016-01-01 01:01:03 [5] System: LAN3 link down
    2016-01-01 01:01:05 [5] System: LAN3 link up 100 mbps
    2016-01-01 01:01:06 [5] System: LAN3 link down
    2016-01-01 01:01:08 [5] System: LAN3 link up 100 mbps
    2016-01-01 01:01:12 [5] System: LAN3 link down
    2016-01-01 01:01:16 [5] System: LAN3 link up 100 mbps
    2016-01-01 01:01:19 [5] DHCPD: Recv REQUEST from 60:xx:xx:xx:xx:xx
    2016-01-01 01:01:20 [5] DHCPD: Send ACK to 192.168.1.104
    2016-01-01 01:01:29 [5] System: LAN3 link down
    2016-01-01 01:01:31 [5] System: LAN3 link up 100 mbps
    2016-01-01 01:01:35 [5] System: LAN3 link down
    2016-01-01 01:01:37 [5] System: LAN3 link up 100 mbps
    2016-01-01 01:01:38 [5] System: DSL Training G.994
    2016-01-01 01:01:41 [5] DHCPD: Recv DISCOVER from AC:<MacSnipped>
    2016-01-01 01:01:41 [5] DHCPD: Send OFFER with ip 192.168.1.100
    2016-01-01 01:01:41 [5] DHCPD: Recv REQUEST from AC:<MacSnipped>
    2016-01-01 01:01:41 [5] DHCPD: Send ACK to 192.168.1.100
    2016-01-01 01:01:43 [5] System: DSL G.994 Non-Standard Info Received
    2016-01-01 01:01:45 [5] System: DSL G.994 Non-Standard Info Received
    2016-01-01 01:01:46 [5] System: DSL Training G.993 Started
    2016-01-01 01:03:00 [5] System: DSL Training G.993 Channel Analysis
    2016-01-01 01:03:01 [5] System: DSL Link Up us/ds 41659/109341 kbps Type PTM
    2016-01-01 01:03:02 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000dd8)]
    2016-01-01 01:03:02 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2016-01-01 01:03:05 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2016-01-01 01:03:07 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000dd8)]
    2016-01-01 01:03:08 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2016-01-01 01:03:13 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2016-01-01 01:03:16 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000dd8)]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [LCP ConfReq id=0x1 <mru 1480> <magic 0x20b9e489>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [LCP ConfReq id=0x41 <mru 1492> <auth pap> <magic 0x70a730fb>]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [LCP ConfAck id=0x41 <mru 1492> <auth pap> <magic 0x70a730fb>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [LCP ConfAck id=0x1 <mru 1480> <magic 0x20b9e489>]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [LCP EchoReq id=0x0 magic=0x20b9e489]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [PAP AuthReq id=0x1 user="<SnippedForForumUsage>" password=<hidden>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [LCP EchoRep id=0x0 magic=0x70a730fb]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [PAP AuthAck id=0x1 ""]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [IPV6CP ConfReq id=0x1 <addr fe80::<IPv6Snipped>>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [IPCP ConfReq id=0xde <addr 62.xxx.xxx.xxx>]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [IPCP ConfAck id=0xde <addr 62.xxx.xxx.xxx>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [IPCP ConfNak id=0x1 <addr 84.xxx.xxx.xxx> <ms-dns1 217.xxx.xxx.xxx> <ms-dns2 217xxx.xxx.xxx
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [IPCP ConfReq id=0x2 <addr 84.xxx.xxx.xxx> <ms-dns1 217.xxx.xxx.xxx> <ms-dns2 217xxx.xxx.xxx
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [IPV6CP ConfReq id=0x9f <addr fe80::<IPv6Snipped>>]
    2016-01-01 01:03:17 [6] PPP: ppp0 sent [IPV6CP ConfAck id=0x9f <addr fe80::<IPv6Snipped>>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [IPV6CP ConfAck id=0x1 <addr fe80::<IPv6Snipped>>]
    2016-01-01 01:03:17 [6] PPP: ppp0 rcvd [IPCP ConfAck id=0x2 <addr 84.xxx.xxx.xxx> <ms-dns1 217.xxx.xxx.xxx> <ms-dns2 217xxx.xxx.xxx
    2017-09-10 20:56:14 [5] VoIP: enable SIP stack due to intf(84.xxx.xxx.xxx) is up.
    2017-09-10 20:56:15 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 20:56:26 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:56:28 [5] System: LAN3 link down
    2017-09-10 20:56:29 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:56:30 [5] System: LAN3 link up 100 mbps
    2017-09-10 20:56:31 [5] System: LAN3 link down
    2017-09-10 20:56:32 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:56:33 [5] System: LAN3 link up 100 mbps
    2017-09-10 20:56:37 [5] System: LAN3 link down
    2017-09-10 20:56:37 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:56:38 [5] System: LAN3 link up 100 mbps
    2017-09-10 20:56:40 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:56:43 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 20:56:53 [5] System: LAN3 link down
    2017-09-10 20:56:55 [5] System: LAN3 link up 100 mbps
    2017-09-10 20:56:59 [5] System: LAN3 link down
    2017-09-10 20:57:00 [5] System: LAN3 link up 100 mbps
    2017-09-10 20:57:04 [5] DHCPD: Recv DISCOVER from AC:<MacSnipped>
    2017-09-10 20:57:04 [5] DHCPD: Send OFFER with ip 192.168.1.100
    2017-09-10 20:57:04 [5] DHCPD: Recv REQUEST from AC:<MacSnipped>
    2017-09-10 20:57:05 [5] DHCPD: Send ACK to 192.168.1.100
    2017-09-10 20:57:24 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:57:27 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:57:30 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:57:35 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:57:38 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:57:41 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 20:58:52 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:58:55 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:58:58 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 20:59:03 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:59:06 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 20:59:09 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:00:50 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:00:53 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:00:56 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:01:01 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:01:04 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:01:07 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:03:18 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:03:21 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:03:24 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:03:29 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:03:32 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:03:35 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:06:16 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:06:19 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:06:22 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:06:27 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:06:30 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:06:33 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:09:44 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:09:47 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:09:50 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:09:55 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:09:58 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:10:01 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:13:16 [5] DHCPD: Recv DISCOVER from DC:<MacSnipped>
    2017-09-10 21:13:16 [5] DHCPD: Send OFFER with ip 192.168.1.101
    2017-09-10 21:13:16 [5] DHCPD: Recv REQUEST from DC:<MacSnipped>
    2017-09-10 21:13:16 [5] DHCPD: Send ACK to 192.168.1.101
    2017-09-10 21:13:42 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:13:45 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:13:48 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:13:53 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:13:56 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:13:59 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
    2017-09-10 21:18:10 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:18:13 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:18:16 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1
    2017-09-10 21:18:21 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:18:24 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0
    2017-09-10 21:18:27 [5] DHCPC: Recv no OFFER, DHCP Service unavailable

  6. #6
    No matter what I would try a reset of the router to factory defaults and set it up again. If this fails then contact support directly via phone or email (see http://www.tp-link.de/support-contac...otline-Support).

  7. #7
    Agree with MikeX. Your router seems to be a localized version, it's better to contact the local support team in Germany if they have a beta firmware to try or what.

  8. #8
    Thank you for your replies. I'll report if there are any solutions.


 

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.