RT-N66 378.56_2 Merlin: WAN link seem to fail

[kiccolsd]

Newly I noticed that my RT-N66 has troubles with WAN link.
My config is VDSL Technicolor FTTC Modem\Router acting as pure modem --> RT-N66 for routing and WAN connection. If I don't look at the log everything seem to work well.

This is the Log

Nov 26 01:04:20 pppd[377]: No response to 10 echo-requests
Nov 26 01:04:20 pppd[377]: Serial link appears to be disconnected.
Nov 26 01:04:20 pppd[377]: Connect time 15033.2 minutes.
Nov 26 01:04:20 pppd[377]: Sent 3565120230 bytes, received 3248891084 bytes.
Nov 26 01:04:20 miniupnpd[2293]: Failed to get IP for interface ppp0
Nov 26 01:04:20 miniupnpd[2293]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 26 01:04:20 dnsmasq[260]: read /etc/hosts - 5 addresses
Nov 26 01:04:20 dnsmasq[260]: read /etc/hosts.dnsmasq - 5 addresses
Nov 26 01:04:20 dnsmasq-dhcp[260]: read /etc/ethers - 5 addresses
Nov 26 01:04:20 dnsmasq[260]: using nameserver 8.8.8.8#53
Nov 26 01:04:20 dnsmasq[260]: using nameserver 8.8.4.4#53
Nov 26 01:04:20 WAN Connection: Fail to connect with some issues.
Nov 26 01:04:20 stop_nat_rules: apply the redirect_rules!
Nov 26 01:04:26 pppd[377]: Connection terminated.
Nov 26 01:04:26 pppd[377]: Sent PADT
Nov 26 01:04:26 kernel: Interface ppp0 doesn't exist
Nov 26 01:04:26 pppd[377]: Modem hangup
Nov 26 01:05:11 pppd[377]: Timeout waiting for PADO packets
Nov 26 01:06:08 miniupnpd[2293]: Failed to get ip address for interface ppp0
Nov 26 01:06:26 pppd[377]: Timeout waiting for PADO packets
Nov 26 01:07:41 pppd[377]: Timeout waiting for PADO packets
Nov 26 01:08:57 pppd[377]: Timeout waiting for PADO packets
Nov 26 01:08:58 pppd[377]: PPP session is 3 (0x3)
Nov 26 01:08:58 pppd[377]: Connected to XX:XX:XX:XX:XX:XX via interface eth0
Nov 26 01:08:58 pppd[377]: Using interface ppp0
Nov 26 01:08:58 pppd[377]: Connect: ppp0 <--> eth0
Nov 26 01:08:59 pppd[377]: PAP authentication succeeded
Nov 26 01:08:59 pppd[377]: peer from calling number 30:91:8F:34:D5:72 authorized
Nov 26 01:08:59 miniupnpd[2293]: Failed to get IP for interface ppp0
Nov 26 01:08:59 miniupnpd[2293]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 26 01:08:59 miniupnpd[2293]: Failed to get IP for interface ppp0
Nov 26 01:08:59 miniupnpd[2293]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 26 01:08:59 miniupnpd[2293]: Failed to get IP for interface ppp0
Nov 26 01:08:59 miniupnpd[2293]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 26 01:08:59 pppd[377]: local  IP address XX.XXX.XXX.XXX
Nov 26 01:08:59 pppd[377]: remote IP address 192.168.100.1
Nov 26 01:08:59 rc_service: ip-up 5231:notify_rc start_firewall
Nov 26 01:08:59 dnsmasq[260]: read /etc/hosts - 5 addresses
Nov 26 01:08:59 dnsmasq[260]: read /etc/hosts.dnsmasq - 5 addresses
Nov 26 01:08:59 dnsmasq-dhcp[260]: read /etc/ethers - 5 addresses
Nov 26 01:08:59 dnsmasq[260]: using nameserver 8.8.8.8#53
Nov 26 01:08:59 dnsmasq[260]: using nameserver 8.8.4.4#53
Nov 26 01:08:59 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Nov 26 01:08:59 wan: finish adding multi routes
Nov 26 01:09:00 WAN Connection: WAN was restored.

Can anyone help me understand what's wrong with my config?

Ps. Before 378.56 I didn't notice this kind of message but I'm not sure that there was.

 

[kiccolsd]

No one can help me? Any idea? Nothing??

 

[john9527]

PADO timeouts are usually caused by something upstream of the router....

- try replacing the ethernet cable between the router and modem
- if you can get to the modem logs, check those for a problem reported there

 

[joegreat]

- try replacing the ethernet cable between the router and modem

A good CAT5e or CAT6 cable needed - the N66U is very sensitive about cables...

 

[kiccolsd]

Thanks to both of you. First of all I'm going to buy a brand new Cat6 Ethernet Cable. Then I logged in the modem GUI searching for something like a LOG but without luck, btw i noticed that due to remote handling of my ISP over his modem some setting was restored to default and one is the AutoConnection that must be setted off in order to bridge the modem. I'll keep an eye to check if this is the solution and report back to you.

Thx!

 

[cowst]

Hey,
Stable (all): 378.56_2
Date: 3-Nov-2015
Is it really for all?
Because 378.56 was not suitable for N66U.

 

[kiccolsd]

Hey,
Stable (all): 378.56_2
Date: 3-Nov-2015
Is it really for all?
Because 378.56 was not suitable for N66U.

Why?? In the changelog N66U was present. Maybe you are talking about 378.56_0

 

[bbunge]

I have a month of uptime on my N66R with zero issues on this firmware.


Sent from my iPod touch using Tapatalk

 

[cowst]

yes, I meant 56_0.
thanks guys, going to upgrade