New Archer VR2100 keeps restarting every few hours
I got a new Archer VR2100 (the model field doesn't have that listed so had to choose something similar) a couple of days ago and every few hours it seems to reboot. It certainly disconnects from both the internet and LAN and the wifi vanishes for a minute or so. I'm on BT Infinity.
When it reboots, the log time and date resets back to 2016-01-01 00:00:00, which makes things tricky to sort. However, here are some extracts (apology for length):
2016-01-01 00:00:20 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2016-01-01 00:00:28 [5] System: DSL Training
2016-01-01 00:00:31 [5] System: DSL Link Down
2016-01-01 00:00:35 [5] System: DSL Training
2016-01-01 00:00:40 [5] System: DSL Link Down
2016-01-01 00:00:41 [5] DHCPD: REQUEST ip c0a80067 already reserved by someone
2016-01-01 00:00:41 [5] DHCPD: Send NAK
2016-01-01 00:00:41 [6] DHCPD: Recv DISCOVER from BC:E1:XX:XX:XX
2016-01-01 00:00:41 [5] DHCPD: Send OFFER with ip 192.168.0.100
2016-01-01 00:00:41 [5] System: DSL Training
2016-01-01 00:00:42 [5] System: Enable Access Control
2016-01-01 00:00:42 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:00:42 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:00:42 [6] DHCPD: Recv DISCOVER from 98:41:5C:XX:XX:XX
2016-01-01 00:00:42 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 00:00:43 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 00:00:44 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 00:00:44 [6] DHCPD: Recv DISCOVER from 28:BE:03:XX:XX:XX
2016-01-01 00:00:44 [5] DHCPD: Send OFFER with ip 192.168.0.102
2016-01-01 00:00:45 [5] DHCPD: Send ACK to 192.168.0.102
2016-01-01 00:00:45 [6] DHCPD: Recv DISCOVER from 00:F6:20:XX:XX:XX
2016-01-01 00:00:45 [5] DHCPD: Send OFFER with ip 192.168.0.104
2016-01-01 00:00:45 [5] System: DSL Link Down
2016-01-01 00:00:45 [5] DHCPD: Wrong Server id or request an invalid ip
2016-01-01 00:00:45 [5] DHCPD: Send NAK
2016-01-01 00:00:45 [6] DHCPD: Recv DISCOVER from 78:5D:C8:XX:XX:XX
2016-01-01 00:00:45 [5] DHCPD: Send OFFER with ip 192.168.0.105
2016-01-01 00:00:46 [5] DHCPD: Send ACK to 192.168.0.105
2016-01-01 00:00:48 [5] System: DSL Training
2016-01-01 00:00:49 [6] DHCPD: Recv DISCOVER from 00:F6:20:XX:XX:XX
2016-01-01 00:00:49 [5] DHCPD: Send OFFER with ip 192.168.0.106
2016-01-01 00:00:50 [5] DHCPD: Send ACK to 192.168.0.106
2016-01-01 00:00:56 [5] System: DSL Link Down
2016-01-01 00:00:57 [5] System: DSL Training
2016-01-01 00:01:11 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:11 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:11 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:13 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:13 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:14 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:20 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:20 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:20 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:23 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:23 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:23 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:25 [6] DHCPD: Recv INFORM from 38:C9:86:XX:XX:XX
2016-01-01 00:01:25 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:25 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:26 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:28 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:28 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:29 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:31 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:31 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:31 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:32 [5] System: DSL Link Down
2016-01-01 00:01:35 [5] System: DSL Training
2016-01-01 00:01:37 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:37 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:38 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:40 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:40 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:40 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:43 [5] System: DSL Link Down
2016-01-01 00:01:44 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:44 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:44 [5] System: DSL Training
2016-01-01 00:01:45 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:47 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:47 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:48 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:48 [5] System: DSL Link Down
2016-01-01 00:01:49 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 00:01:52 [5] System: DSL Training
2016-01-01 00:01:54 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:54 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:54 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:56 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:56 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:57 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:02 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:02 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:03 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:05 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:05 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:06 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:08 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:08 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:08 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:10 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:10 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:11 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:13 [5] System: DSL Link Up us/ds 0/79999 kbps Type 64/65B PTM Annex B
2016-01-01 00:02:17 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:17 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:18 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:18 [6] PPP: sent [PADT session is 2896]
2016-01-01 00:02:18 [6] PPP: sent [PADI Host-Uniq(0x00000694)]
2016-01-01 00:02:19 [3] PPP: Unable to complete PPPoE Discovery
2016-01-01 00:02:19 [4] PPP: Connect script failed
2016-01-01 00:02:20 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:20 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:21 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:24 [6] PPP: sent [PADT session is 2896]
2016-01-01 00:02:24 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:26 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:26 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:27 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:29 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:29 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:29 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:30 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:32 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:32 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:33 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:35 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:35 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:36 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:39 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:39 [6] PPP: rcvd [PADO PeerMac(a4-7b-2c-XX-XX-XX)]
2016-01-01 00:02:39 [6] PPP: sent [PADR Host-Uniq(0x0000076f)]
2016-01-01 00:02:39 [6] PPP: rcvd [PADS SessionID(0x0c1c)]
2016-01-01 00:02:39 [5] PPP: Connected to a4:7b:2c:XX:XX:XX via interface nas8.101
2016-01-01 00:02:39 [6] PPP: Using interface ppp1
2016-01-01 00:02:39 [5] PPP: Connect: ppp1 <--> nas8.101
2016-01-01 00:02:39 [6] PPP: CHAP authentication succeeded: CHAP authentication success
2016-01-01 00:02:39 [5] PPP: CHAP authentication succeeded
2016-01-01 00:02:39 [5] PPP: peer from calling number A4:7B:2C:CD:F4:E2 authorized
2016-01-01 00:02:39 [5] PPP: local IP address 81.157.X.X
2016-01-01 00:02:39 [5] PPP: remote IP address 172.16.X.X
2016-01-01 00:02:39 [5] PPP: primary DNS address 81.139.X.X
2016-01-01 00:02:39 [5] PPP: secondary DNS address 81.139.X.X
2020-06-28 19:39:10 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2020-06-28 19:39:10 [5] DHCPD: Send OFFER with ip 192.168.0.107
2020-06-28 19:39:11 [5] DHCPD: Send ACK to 192.168.0.107
2020-06-28 19:44:36 [6] Httpd: DNS 81.139.X.X resolve succeed for dns.msftncsi.com
2020-06-28 19:44:36 [6] Httpd: DNS 81.139.X.X resolve succeed for www.msftncsi.com
2020-06-28 19:44:36 [6] Httpd: NCSI response check succeed.
2020-06-28 19:47:49 [6] Httpd: DNS 81.139.56.100 resolve succeed for dns.msftncsi.com
2020-06-28 19:47:49 [6] Httpd: DNS 81.139.56.100 resolve succeed for www.msftncsi.com
2020-06-28 19:47:49 [6] Httpd: NCSI response check succeed.
Any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I tried both the older FW on the site, and some new beta firmware tech support sent me - neither worked, as the issue persisted.
- Copy Link
- Report Inappropriate Content
Thats not good. I've tried setting mine to automatically reboot overnight at 3am in the hope that a forced restart might keep it running when I need it to be.
- Copy Link
- Report Inappropriate Content
I think my SNR might be too low, which, from what I've read, can cause disconnections and the modem to re-train if the SNR gets too low.
I'm on NBN / IINET.
Also seeing error packets in the downstream. Have changed phone cable, no change in behaviour.
For me it's now more like once or twice a day that it disconnects/re-trains
What SNR are you getting? Cany you share the beta firmware?
I should also add that:
- I mentioned this to my ISP (IINET) and they said they did some 'reset' at their end yesterday to try to fix it
- I reverted back to the original firmware which shipped with the unit.
I'm now almost 19 hrs without a disconnection, I'll keep you posted.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello, thanks for bringing this up, we will follow up your case in another post, please check and confirm.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@naz_eg Only solution for me was send it back and buy something else, sadly.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Just want to get back and update this.
It turned out that I had poor quality (old) telephone cabling in the house.
My ISP offered to send a technician out to have a look and made a few changes. (rewired 2 phone sockets / disabled 2 unused phone sockets)
Once this was complete, the line tested much better and I have not had any disconnections since.
So the modem is just particularly sensitive to poor quality lines.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6462
Replies: 36
Voters 0
No one has voted for it yet.