Router loses connection to LAN and WAN

[kktk]

Here's my setup:

I'm using a DSL modem.
Connected my N66U to it.
2 desktops hard-wired to the N66U.
2 laptops on wifi.

Randomly--I will lose complete connectivity.
No access to LAN. WAN--wifi or wired.

I've restored to factory settings.
Restarted machines, routers, cable modems etc.
I've even purchased another router and set that up...same thing happened there too. 2-3 days things work..then randomly I lose all connectivity.

I have setup my network as 192.168.1.1 with 255.255.255 as the subnet and 192.168.1.1 as the gateway. All this works when things are going smoothly.

I've searched but havent found anything that would explain this.
Nothing seems to help.

If I direct connect any of the PC's to the DSL modem and dial out...that works...but networking seems to be an issue.

So is the problem with something in the DSL modem that is throwing things off? I've changed 2 routers---both cant have the same issue?

K

 

[joegreat]

Router loses connection to LAN and WAN

Hi K,

The N66U is very sensitive on the cabling: You have to use CAT5e or CAT6 cables to the internet (WAN, modem) and to you cable connected devices.

On the other hand I had some issues in the past with my provider where he disconneced the WAN port regulary - not sure why but is was really dropping the exernal connection.
Only after a resest of my configuration on the provider side (including getting a new external IP address) the thing works rock solid.

Maybe this two directions (where the cableing the simpler) can help you...

With kind regards
Joe

 

[PrivateJoker]

@kktk what brings connectivity back once it drops? Rebooting the router (whether it's the N66 or the alternate router you bought) is what reconnects things?

Perhaps try peeking on the router log page and copy and paste the few lines before & after connectivity dropped out to the forum.

 

[kktk]

I'm using CAT5e...and mostly CAT6 cabling already.

My ISP does regularly change IP's on me. I'm suspecting that is causing some issues. Usually whenever that happens, the router handles this just fine(like it should).

Also, most of the times when this happens, restarting the DSL modem and the router does get me connected back again. But a lot of times even that doesn't help.

What I find strange is that I have connected my older Medialink Router...and the same thing happens there too.

Could other downstream devices cause a complete connection failure like mine? Problems on the PC side? OR sometimes I connect another AP to extend the wifi range(although this doesnt seem to have any connection to the drop out).

Thanks!
K

 

[kktk]

On more searching(and disconnecting all devices)...I found this in the router log:

Oct 5 01:57:55 pppd[342]: LCP terminated by peer
Oct 5 01:57:55 pppd[342]: Connect time 1382.5 minutes.
Oct 5 01:57:55 pppd[342]: Sent 167178151 bytes, received 1990503502 bytes.
Oct 5 01:57:55 dnsmasq[304]: read /etc/hosts - 5 addresses
Oct 5 01:57:55 dnsmasq[304]: using nameserver 195.229.241.222#53
Oct 5 01:57:55 dnsmasq[304]: using nameserver 213.42.20.20#53
Oct 5 01:57:58 WAN Connection: Fail to connect with some issues.
Oct 5 01:57:58 stop_nat_rules: apply the redirect_rules!
Oct 5 01:57:58 pppd[342]: Connection terminated.
Oct 5 01:57:58 pppd[342]: Sent PADT
Oct 5 01:57:58 pppd[342]: Modem hangup
Oct 5 01:58:16 miniupnpd[421]: ioctl(s, SIOCGIFADDR, ...): No such device
Oct 5 01:58:16 miniupnpd[421]: Failed to get ip address for interface ppp0
Oct 5 01:58:16 pppd[342]: PPP session is 501 (0x1f5)
Oct 5 01:58:16 pppd[342]: Connected to 00:00:5e:00:01:01 via interface eth0
Oct 5 01:58:16 pppd[342]: Using interface ppp0
Oct 5 01:58:16 pppd[342]: Connect: ppp0 <--> eth0
Oct 5 01:58:17 miniupnpd[421]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 5 01:58:17 miniupnpd[421]: Failed to get ip address for interface ppp0
Oct 5 01:58:17 miniupnpd[421]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 5 01:58:17 miniupnpd[421]: Failed to get ip address for interface ppp0

Any ideas?

 

[wouterv]

What is the firmware version?

 

[RMerlin]

1382 minutes is nearly 23 hours. Does the disconnect always happen every 1380-ish minutes? If so, then it might be your ISP disconnecting you periodically - I have seen some ISPs do that.

 

[kktk]

3.0.0.4.374_720 is the firmware I'm running.

I'll try and monitor the disconnect...but I dont think its every so often.
Sometimes I'm up for days without an issue...other times I go down 2-3 times a day.

Even if I lose internet connectivity--why would my lan access get hosed up at the same time as well? Wired or wireless--its happening to the complete LAN And WAN. Cant access the LAN or the router admin access page.

Also, the gateway gets blanked out and I land up getting thrown on the 169.243 ip address scheme with a 255.255.0.0 subnet.

K

 

[jlake]

3.0.0.4.374_720 is the firmware I'm running.

I'll try and monitor the disconnect...but I dont think its every so often.
Sometimes I'm up for days without an issue...other times I go down 2-3 times a day.

Even if I lose internet connectivity--why would my lan access get hosed up at the same time as well? Wired or wireless--its happening to the complete LAN And WAN. Cant access the LAN or the router admin access page.

Also, the gateway gets blanked out and I land up getting thrown on the 169.243 ip address scheme with a 255.255.0.0 subnet.

K

Hmmm.... Are you aware that 169.243.x.x and subnet mask 255.255.0.0 is the address that windows assigns itself if it can't find a DHCP server?

You might have better luck if you put your DSL modem in full bridged mode and configure your Asus router with a PPPoE internet connection type (assuming your ISP is PPPoE)....so you only have 1 router (and 1 NAT) on your network.

Possibly I misread you original post but you have your DSL modem with an IP address of 192.168.1.1 and the Asus at 192.168.1.1? That's not good. I'm not a subnetting expert and I really don't know if the Asus supports only class C subnetting, but many people change the IP address of the Asus to 192.168.2.1 and use DMZ on their dsl modem/router.

Personally, I put my dsl modem/router in to full bridge mode to eliminate that NAT.

http://www.ipprimer.com/addressing.cfm

 

[kktk]

Thanks for your help.
I did realize on searching that windows is assigning itself that IP.
So that's why the LAN is getting thrown off probably.

What I'm trying to narrow down is that the issue is happening due to either:
1. The providers' box.
2. My router.
3. Something downstream.

Also, let me clarify the setup a bit more.

I do have a PPPoE connection. The provider(Etisalat) gives us a optical network terminal since they give us a Fiber line. The product is listed here:
http://www.huawei.com/en/products/fixed-access/fttx/ont/hg8240/index.htm

We then configure our router at 192.168.1.1 to dial out(just like in a DSL line) using PPPoE to the ONT device.

On the downstream side, I assign IP addresses starting from 192.168.1.50 onwards. I static assign 192.168.1.2 to another Access point I use for extending my WiFi range.

Hope this helps.
K

 

[wouterv]

I suggest in your case (with 192.168.1.1 at the PPPoE side), to configure the "downstream side" in the 192.168.2.xx range.