Hi guys,
First time reader, first time poster! I've read through as many related posts as I can, though have not been able to as yet confidently ascertain where the blame definitively lies. I have my suspicions based upon other threads, but my system log message appears to be slightly different, at least to my untrained eyes.
Set-up: RT-N66U connected directly to what I believe is an ONT box, part of a new build See The Light system if anyone is familiar with them. Cable goes directly from the wall into the box, which then feeds into my router. The router goes into a Netgear powerline adapter, with another adapter by my computer. PPPoE connection to the best of my understanding. Login details would appear to be correct, because it does work for some time.
Problem: I started getting these brief WAN drops two days ago. Three or four days ago is when I put in the powerline adapters (replacing a set of TP-Links with a fault of their own), and two days ago is when See The Light had some work done about 2 miles from me. Yesterday wasn't so bad but, as of last night, it's happened at least a dozen or so times now in as many hours (which I know because I've been up all night reading threads and trying things out!).
What I've done: I've changed the cable between the ONT and the router, gone through a few different firmwares (no update had been done directly prior to the WAN issues though, so it was more a desperate hope than expectation), left both powered down for 30 minutes, and factory restores on the router. I haven't done anything with the ONT box because I know nothing about them, and don't want to make it worse by fiddling and getting it completely wrong.
I've set up static IPs for all connecting devices, after reading a thread about someone's computer trying to connect directly to the box and bypassing the router. Amusingly, after doing that and the replacement cable, I got a whole hour of connection (which was a record at that point), then it happened again, and now I've had two hours before it occurred again. Whether this means I've just been lucky, those steps helped, or it's time centric from my ISP, I don't know!
TLDR: Anyway, the messages have been consistent throughout the whole process, small variances depending upon which firmware I'm using at the time. I'm feeling fairly confident at this point that it's the modem or the ISP, especially with the timing of their local works (and the fact we've not had this issue before to my knowledge over the last 18 months), but my experiences with trying to get companies like these to take responsibility for problems tells me that I'm better off getting a third party opinion so that I can be confident in my approach.
If anyone can offer some knowledgeable insight and assurance on my placement of blame, and has got through this lengthier than intended post, I would be eternally grateful!
First time reader, first time poster! I've read through as many related posts as I can, though have not been able to as yet confidently ascertain where the blame definitively lies. I have my suspicions based upon other threads, but my system log message appears to be slightly different, at least to my untrained eyes.
Set-up: RT-N66U connected directly to what I believe is an ONT box, part of a new build See The Light system if anyone is familiar with them. Cable goes directly from the wall into the box, which then feeds into my router. The router goes into a Netgear powerline adapter, with another adapter by my computer. PPPoE connection to the best of my understanding. Login details would appear to be correct, because it does work for some time.
Problem: I started getting these brief WAN drops two days ago. Three or four days ago is when I put in the powerline adapters (replacing a set of TP-Links with a fault of their own), and two days ago is when See The Light had some work done about 2 miles from me. Yesterday wasn't so bad but, as of last night, it's happened at least a dozen or so times now in as many hours (which I know because I've been up all night reading threads and trying things out!).
What I've done: I've changed the cable between the ONT and the router, gone through a few different firmwares (no update had been done directly prior to the WAN issues though, so it was more a desperate hope than expectation), left both powered down for 30 minutes, and factory restores on the router. I haven't done anything with the ONT box because I know nothing about them, and don't want to make it worse by fiddling and getting it completely wrong.
I've set up static IPs for all connecting devices, after reading a thread about someone's computer trying to connect directly to the box and bypassing the router. Amusingly, after doing that and the replacement cable, I got a whole hour of connection (which was a record at that point), then it happened again, and now I've had two hours before it occurred again. Whether this means I've just been lucky, those steps helped, or it's time centric from my ISP, I don't know!
TLDR: Anyway, the messages have been consistent throughout the whole process, small variances depending upon which firmware I'm using at the time. I'm feeling fairly confident at this point that it's the modem or the ISP, especially with the timing of their local works (and the fact we've not had this issue before to my knowledge over the last 18 months), but my experiences with trying to get companies like these to take responsibility for problems tells me that I'm better off getting a third party opinion so that I can be confident in my approach.
If anyone can offer some knowledgeable insight and assurance on my placement of blame, and has got through this lengthier than intended post, I would be eternally grateful!
Code:
Jan 27 09:57:04 WAN Connection: Fail to connect with some issues.
Jan 27 09:57:04 stop_nat_rules: apply the redirect_rules!
Jan 27 09:57:31 pppd[1823]: LCP: timeout sending Config-Requests
Jan 27 09:57:31 pppd[1823]: Connection terminated.
Jan 27 09:57:31 pppd[1823]: Modem hangup
Jan 27 09:57:41 pppd[1823]: Connected to **:**:**:**:**:** via interface eth0
Jan 27 09:57:41 pppd[1823]: Connect: ppp0 <--> eth0
Jan 27 09:57:44 pppd[1823]: peer from calling number **:**:**:**:**:** authorized
Jan 27 09:57:44 pppd[1823]: local IP address ***.**.***.***
Jan 27 09:57:44 pppd[1823]: remote IP address ***.**.***.*
Jan 27 09:57:44 pppd[1823]: primary DNS address ***.**.*.*
Jan 27 09:57:44 pppd[1823]: secondary DNS address **.**.*.**
Jan 27 09:57:44 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Jan 27 09:57:44 wan: finish adding multi routes
Jan 27 09:57:44 rc_service: ip-up 1976:notify_rc stop_upnp
Jan 27 09:57:44 miniupnpd[1909]: shutting down MiniUPnPd
Jan 27 09:57:44 rc_service: ip-up 1976:notify_rc start_upnp
Jan 27 09:57:44 miniupnpd[2007]: version 1.9 started
Jan 27 09:57:44 miniupnpd[2007]: HTTP listening on port 35394
Jan 27 09:57:44 miniupnpd[2007]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 27 09:57:49 WAN Connection: WAN was restored.
