RT-AC66U keeps losing internet where do i start

[rusty]

hi folks, got a RT-AC66U with an Vigor 120 modem, had them for around 15 months, and every 6 months or so they start dropping off for some reason, normally I put on my old HH5 for a few months then put the RT-AC66u & vigor back on
anyway it started playing up again lasr night
I've got the logs from the AC66u, but can't see where the logs are stored for the vigor
can anyone see what's going wrong

Nov 27 14:30:13 WAN_Connection: Ethernet link down.
Nov 27 14:30:13 DualWAN: skip single wan wan_led_control - WANRED off
Nov 27 14:30:13 stop_nat_rules: apply the redirect_rules!
Nov 27 14:30:20 WAN_Connection: WAN was restored.
Nov 27 14:30:20 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Nov 27 14:39:37 miniupnpd[16629]: Failed to get IP for interface ppp0
Nov 27 14:39:37 miniupnpd[16629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 27 14:39:38 WAN_Connection: Fail to connect with some issues.
Nov 27 14:39:38 DualWAN: skip single wan wan_led_control - WANRED off
Nov 27 14:39:38 stop_nat_rules: apply the redirect_rules!
Nov 27 14:39:40 pppd[552]: Connection terminated.
Nov 27 14:39:40 pppd[552]: Modem hangup
Nov 27 14:40:05 pppd[552]: Connected to 00:************ via interface eth0
Nov 27 14:40:05 pppd[552]: Connect: ppp0 <--> eth0
Nov 27 14:40:05 pppd[552]: CHAP authentication succeeded
Nov 27 14:40:05 pppd[552]: peer from calling number 00:5********* authorized
Nov 27 14:40:08 miniupnpd[16629]: Failed to get IP for interface ppp0
Nov 27 14:40:08 miniupnpd[16629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 27 14:40:08 miniupnpd[16629]: Failed to get IP for interface ppp0
Nov 27 14:40:08 miniupnpd[16629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 27 14:40:08 miniupnpd[16629]: Failed to get IP for interface ppp0
Nov 27 14:40:08 miniupnpd[16629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 27 14:40:08 pppd[552]: local IP address ***********
Nov 27 14:40:08 pppd[552]: remote IP address ********
Nov 27 14:40:08 miniupnpd[16629]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 27 14:40:08 miniupnpd[16629]: Failed to get IP for interface ppp0
Nov 27 14:40:08 miniupnpd[16629]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 27 14:40:08 rc_service: ip-up 17453:notify_rc start_firewall
Nov 27 14:40:09 miniupnpd[16629]: shutting down MiniUPnPd
Nov 27 14:40:09 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Nov 27 14:40:10 rc_service: ip-up 17453:notify_rc stop_upnp
Nov 27 14:40:10 rc_service: waitting "start_firewall" via ip-up ...
Nov 27 14:40:10 miniupnpd[17489]: HTTP listening on port 49508
Nov 27 14:40:10 miniupnpd[17489]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 27 14:40:11 rc_service: ip-up 17453:notify_rc start_upnp
Nov 27 14:40:11 rc_service: waitting "stop_upnp" via ip-up ...
Nov 27 14:40:11 miniupnpd[17489]: shutting down MiniUPnPd
Nov 27 14:40:13 miniupnpd[17496]: HTTP listening on port 49994
Nov 27 14:40:13 miniupnpd[17496]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 27 14:40:15 stop_nat_rules: apply the redirect_rules!
Nov 27 14:40:20 pppd[552]: Connection terminated.
Nov 27 14:40:20 pppd[552]: Modem hangup
Nov 27 14:41:05 pppd[552]: Timeout waiting for PADO packets

 

[ColinTaylor]

Nov 27 14:30:13 WAN_Connection: Ethernet link down.
Nov 27 14:30:20 WAN_Connection: WAN was restored.

Looks like your modem rebooted itself.

Then when it came back up it lost connection to the internet.

Nov 27 14:39:40 pppd[552]: Connection terminated.
Nov 27 14:39:40 pppd[552]: Modem hangup
Nov 27 14:40:05 pppd[552]: Connected to 00:************ via interface eth0
Nov 27 14:40:05 pppd[552]: Connect: ppp0 <--> eth0
Nov 27 14:40:05 pppd[552]: CHAP authentication succeeded
Nov 27 14:40:05 pppd[552]: peer from calling number 00:5********* authorized
Nov 27 14:40:08 pppd[552]: local IP address ***********
Nov 27 14:40:08 pppd[552]: remote IP address ********
Nov 27 14:40:20 pppd[552]: Connection terminated.
Nov 27 14:40:20 pppd[552]: Modem hangup
Nov 27 14:41:05 pppd[552]: Timeout waiting for PADO packets

So it doesn't look like a problem with the router. I suspect there's a problem with your line, contact your ISP and ask them to investigate.

 

[rusty]

do you think it could be the modem ?
its 2nd hand, got it from fleabay when I got the AC66u router
I've put my old Netgear router/modem on to see if that has any probelms

 

[ColinTaylor]

I'm guessing your internet connection is an old-style ADSL/ADSL2+ over a telephone line? I'm sure you already know that that technology is very unreliable. Certain devices work better (are more reliable) than others depending on line quality and what hardware is installed in the local exchange. In my own case a particularly old Netgear model was the go-to item because its Broadcom chipset worked best with my ISP's equipment.

ADSL line quality is very susceptible to external factors such as weather, interference from electrical equipment and even the time of day or year. If your modem has any logs that would be the place to start. You should also do a "quiet line test" to see if there's any detectable hiss (you'll need an analog phone for this, not digital). Good luck.

 

[rusty]

thanks,
the Asus router & Vigor modem work ok for a few weeks or months then suddenly start giving problems, where as the Netgear router/modem or the old BT HH4, work ok all the time, I only got the Asus as I wanted to put VPN on various kit
I can't find any where that the vigor 120 stores logs, so i'm in the dark with that
yes I'm on ADSL/ADSL2 line, Live in the sticks so won't get fibre to house, its in the exchange but can't see them putting down the farm track I live on
may just get a new vigor 130 modem to work with the AC66U, unless you can suggest something better

 

[ColinTaylor]

Sorry don't have any recommendations, I haven't had an ADSL line for about 10 years. I'd have a look at your ISP's own forums to see if other users have a preferred device.

 

[PowerChaos]

You can solve iT differend
You say the netgear works good
Then why not use the netgear as main hub ? And put asus behind it and dmz to the asus ?

So asus is still your main but does not need to dial in
If that works stable then the dial function gives the trouble ( see post above. Providers hardware... )



Greets from PowerChaos
Verzonden vanaf mijn iPhone met Tapatalk

 

[john9527]

Also try the easy change first....replace the modem-router ethernet cable with a good quality cat5e or cat6 cable. Inspect the modem/router ethernet ports for any bent pins or dirt.

 

[rusty]

thanks for replies, the ethernet cable between the 2 was new when I got the asus last year, and it runs ok for some time (weeks/months) then it starts playing up, so think its more a component fault ( ?)
when I was in bed I thought about using the netgear as the modem, not sure how to do it and if it will affect the VPN on the asus

 

[PowerChaos]

thanks for replies, the ethernet cable between the 2 was new when I got the asus last year, and it runs ok for some time (weeks/months) then it starts playing up, so think its more a component fault ( ?)
when I was in bed I thought about using the netgear as the modem, not sure how to do it and if it will affect the VPN on the asus

Well
You can easy set it up

First you got your carrier modem ( I do not work with dsl but I guess it is the same)
On that carrier modem you plugin the wan port of the netgear
So now you have netgear->modem->internet
Where netgear get a ip from the modem ( if router ) or so netgear can dial in ( modem only )

Now the asus router. Put the Wan to the netgear. And let it get a ip a dress
Change the asus lan ip to other range and plug everything in there

So the setup is now the following
Asus->netgear->modem
10.10.10.10 <-> 192.168.1.50 -> 192.168.1.1 <-> 192.168.0.50 -> 192.168.0.1 -> internet

Then open all ports ( called dmz) to the netgear and from netgear to asus

Then the vpn works like normal as the netgear only get used as a hub (kinda )

Greets from PowerChaos


Greets from PowerChaos
Verzonden vanaf mijn iPhone met Tapatalk

 

[rusty]

thanks
not sure I understand it ( i'm an oldie so brain not working well now), but will it a go

 

[rusty]

just dug out my older netgear DGN2000 hopefully I can use that as the modem, (want to keep the newer netgear router/modem as my trusty backup, using it now)

 

[PowerChaos]

Ok it stays the same
Just make sure you use a differend subnet.
And assign a static ip
So you know where to forward all the incoming traffic to

I know it is easy to explain on paper. But if you know a little then I am sure you can get it working

This is the setup in short
You connect the netgear to the internet and the asus to your netgear
You set the netgear just as gateway and use the asus as main router
So you disable everything on the netgear except dhcp ( or manual assign ip ). This also include firewall
Then you dmz ( open all ports and bypass firewall to single ip ) to the asus router
And then you setup the asus as your main ( WiFi firewall dhcp .. vpn )

In that case your netgear will act as your modem and pass everything to the asus

Ofcourse you need to see for the ip that it does not come in conflict with the other ip that is assigned
Best is to change the ip to a other range ( 10.x or 192.168.x )



Greets from PowerChaos
Verzonden vanaf mijn iPhone met Tapatalk

 

[rusty]

thanks, I think the ips are different, netgear is 192.168.0.1 and asus is 192.168.1.1

 

[PowerChaos]

Ok that is perfect
Now asus got also a 192.168.0.x ip. That’s the ip you need to forward everything to from the netgear.
You can see that ip in the client list on the netgear

Then everything is fine and the asus can be setup like you want


Greets from PowerChaos
Verzonden vanaf mijn iPhone met Tapatalk

 

[rusty]

thanks again

I'll have a play tomorrow (Thursday) in case I muck it up, as I need internet access tonight to watch the match

 

[rusty]

managed to find a netgear AC 1200 (d6100) router modem, so going to try to use that
in the netgear AC 1200
I turned off the wireless,
then turned it to Modem only

connected the Asus RT-AC66U router to netgear, connected all my LAN cables (4 ethernet cables) to the Asus router
my laptop connected right away, think it was on LAN 1 slot,
when I tested a IPTV box last night that connects on another LAN slot it didn't connect to internet

so it looks like only LAN slot 1 on Asus router is connecting to the Netgear AC1200 (in modem mode)
not sure what setting are still on the Netgear when you put it into modem mode

 

[rusty]

had a google yesterday, it appears that netgears Modem only mode has problems, quite a few folks have said there ones would not let iptv, iplayer etc