scope_creep
New Around Here
setup is asus rt-n66u with vigor 120 adsl modem.
Behaviour seems to be that connection is dropping every day at around 4pm.
I've attached the syslog. I've also put a shielded, I think S/FTP cable between the modem and router, which was one solution on the web.
Taking yesterday as an example, the log reports
Mar 7 14:16:27 WAN Connection: Fail to connect with some issues.
Mar 7 14:16:27 stop_nat_rules: apply the redirect_rules!
Mar 7 14:16:28 pppd[342]: Connection terminated.
Mar 7 14:16:28 pppd[342]: Modem hangup
Mar 7 14:16:39 pppd[342]: Connected to 00:50:7f:f3:69:96 via interface eth0
Mar 7 14:16:39 pppd[342]: Connect: ppp0 <--> eth0
Mar 7 14:16:40 pppd[342]: CHAP authentication succeeded
Mar 7 14:16:40 pppd[342]: peer from calling number 00:50:7F:F3:69:96 authorized
Mar 7 14:16:40 pppd[342]: local IP address 81.130.130.150
Mar 7 14:16:40 pppd[342]: remote IP address 81.130.224.1
Mar 7 14:16:40 pppd[342]: primary DNS address 194.72.9.38
Mar 7 14:16:40 pppd[342]: secondary DNS address 62.6.40.162
Mar 7 14:16:40 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Mar 7 14:16:40 rc_service: ip-up 17186:notify_rc stop_upnp
Mar 7 14:16:40 miniupnpd[11347]: received signal 15, good-bye
Mar 7 14:16:40 rc_service: ip-up 17186:notify_rc start_upnp
Mar 7 14:16:40 miniupnpd[17215]: HTTP listening on port 46407
Mar 7 14:16:40 miniupnpd[17215]: Listening for NAT-PMP traffic on port 5351
Mar 7 14:16:43 WAN Connection: WAN was restored.
At Mar 7 14:16:28 the modem drop the wan connection. Is that normal behaviour? It was working fine for a 1.5 years, until that big BT outage last week, then regular drop outs every afternoon. It is providing connectivity in a restaurant, so I set the DHCP lease down to 10800, so as to get back the lease IP address for customers who only stay on average 2 hours. I don't think it has a bearing on it. I've had one draytek vigor modem failing on me before, but not for 4 years. The router has a static IP, obviously setup on the modem.
3 years ago, we had a similar problem seemingly caused by a WAN dhcp problem. We put in a static IP and changed the dns to point to opendns and google. And it seemed to work fine.
Bob.
Behaviour seems to be that connection is dropping every day at around 4pm.
I've attached the syslog. I've also put a shielded, I think S/FTP cable between the modem and router, which was one solution on the web.
Taking yesterday as an example, the log reports
Mar 7 14:16:27 WAN Connection: Fail to connect with some issues.
Mar 7 14:16:27 stop_nat_rules: apply the redirect_rules!
Mar 7 14:16:28 pppd[342]: Connection terminated.
Mar 7 14:16:28 pppd[342]: Modem hangup
Mar 7 14:16:39 pppd[342]: Connected to 00:50:7f:f3:69:96 via interface eth0
Mar 7 14:16:39 pppd[342]: Connect: ppp0 <--> eth0
Mar 7 14:16:40 pppd[342]: CHAP authentication succeeded
Mar 7 14:16:40 pppd[342]: peer from calling number 00:50:7F:F3:69:96 authorized
Mar 7 14:16:40 pppd[342]: local IP address 81.130.130.150
Mar 7 14:16:40 pppd[342]: remote IP address 81.130.224.1
Mar 7 14:16:40 pppd[342]: primary DNS address 194.72.9.38
Mar 7 14:16:40 pppd[342]: secondary DNS address 62.6.40.162
Mar 7 14:16:40 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Mar 7 14:16:40 rc_service: ip-up 17186:notify_rc stop_upnp
Mar 7 14:16:40 miniupnpd[11347]: received signal 15, good-bye
Mar 7 14:16:40 rc_service: ip-up 17186:notify_rc start_upnp
Mar 7 14:16:40 miniupnpd[17215]: HTTP listening on port 46407
Mar 7 14:16:40 miniupnpd[17215]: Listening for NAT-PMP traffic on port 5351
Mar 7 14:16:43 WAN Connection: WAN was restored.
At Mar 7 14:16:28 the modem drop the wan connection. Is that normal behaviour? It was working fine for a 1.5 years, until that big BT outage last week, then regular drop outs every afternoon. It is providing connectivity in a restaurant, so I set the DHCP lease down to 10800, so as to get back the lease IP address for customers who only stay on average 2 hours. I don't think it has a bearing on it. I've had one draytek vigor modem failing on me before, but not for 4 years. The router has a static IP, obviously setup on the modem.
3 years ago, we had a similar problem seemingly caused by a WAN dhcp problem. We put in a static IP and changed the dns to point to opendns and google. And it seemed to work fine.
Bob.
Last edited:
