[SOLVED] WR842ND rebooting on its own

If your problem doesn't fall into one of the other categories, report it here.

Moderator: Moderators

Post Reply
web_knows
Posts: 9
Joined: Tue Oct 22, 2013 9:37 pm

[SOLVED] WR842ND rebooting on its own

Post by web_knows »

The Setup:
Gargoyle Version:1.5.11
Model:TP-Link TL-WR842N/ND v1
Number of clients: 8, not concurrent and only 1 of these is heavy in bandwidth usage (torrents)

The Problem:
The router is rebooting (aka crashing) on its own with an increased frequency (since I first installed Gargoyle about 1 week ago).

The Scenario:
Nothing have changed drastically since I installed Gargoyle. The major changes I can think of is that I installed the Tor plugin (not being used right now) and 2 themes.

Other than that I have even reduced the number of connections allowed by my torrent client (general max # of connections reduced to 90 and max # of connections for new transfers reduced to 20).

The Analysis:
Since the router was rebooting several times in a row, at a very short interval, I ssh'ed in and left 'top' running to see if I could catch the culprit, but no luck there (see below the latest snapshot from 'top' before the router rebooted, I don't see anything using up much of the router's resources).

Btw, 'logread' didn't give any clue of the problem either, for obvious reasons.

The Question:
Do you guys have any advices to try to fix this problem? Should I try to uninstall some stuff I'm not using?

Thanks in advance.

Code: Select all

Mem: 27988K used, 1272K free, 0K shrd, 2192K buff, 5284K cached
CPU:   0% usr   1% sys   0% nic  86% idle   0% io   0% irq  10% sirq
Load average: 0.05 0.29 0.28 1/65 4359
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1265     1 root     R     2148   7%   2% hostapd -P /var/run/wifi-phy0.pid -B
    3     2 root     SW       0   0%   1% [ksoftirqd/0]
 3653  3648 root     R     1728   6%   0% top
 3647  1518 root     S     1448   5%   0% /usr/sbin/dropbear -P /var/run/dropbe
 4339  1994 root     S     3940  13%   0% /usr/sbin/smbd -D
 1996     1 root     S     3424  12%   0% /usr/sbin/nmbd -D
 1994     1 root     S     3336  11%   0% /usr/sbin/smbd -D
  708     1 root     S     1732   6%   0% /sbin/syslogd -C16
  959   895 root     S     1732   6%   0% udhcpc -p /var/run/udhcpc-eth1.pid -s
 3515     1 root     S     1732   6%   0% /usr/sbin/crond -c /etc/crontabs -l 9
    1     0 root     S     1728   6%   0% init
 2730  2310 root     S     1728   6%   0% -ash
 2823     1 root     S     1728   6%   0% /usr/sbin/ntpd -n -l -p 0.pool.ntp.or
 3648  3647 root     S     1728   6%   0% -ash
  481     1 root     S     1728   6%   0% init
 2323     1 root     S     1724   6%   0% /sbin/watchdog -t 5 /dev/watchdog
  710     1 root     S     1716   6%   0% /sbin/klogd
  895     1 root     S     1700   6%   0% /sbin/netifd
 1943     1 root     S     1620   6%   0% /usr/sbin/rpc.mountd -p 32780 -F
 2111     1 root     S     1604   5%   0% /usr/bin/ddns_gargoyle -P /etc/ddns_p
Last edited by web_knows on Tue Nov 12, 2013 11:11 am, edited 1 time in total.

web_knows
Posts: 9
Joined: Tue Oct 22, 2013 9:37 pm

Re: WR842ND rebooting on its own

Post by web_knows »

I know for a fact that what is causing the router to reboot is my torrent client.

What I've noticed doing further investigation is that the TCP TIME_WAIT connections are being counted as "live" connections by Gargoyle, it seems, according to its Status page.

What does it mean? Even though the ESTABLISHED connections are not beyond the TCP limit (4096), the count is still increasing and I start seeing packets being dropped, as shown in nf_conntrack, because of those TIME_WAIT connections.

This makes no sense, why would the router reboot if it still has lots of memory available and CPU?

Anyone has any ideas, please? I'm really digging Gargoyle, but just this one thing is making me a bit anxious.

Just making sure, this is the version this router is running on (and yes, I know this version is experimental):

Code: Select all

|----------------------------------------------------------------|
| Gargoyle version 1.5.11   | OpenWrt Attitude Adjustment branch |
| Gargoyle revision e3cc435 | OpenWrt revision r38347            |
| Built October 16, 2013    | Target  ar71xx/usb                 |
------------------------------------------------------------------
root@Scorpius:~# uname -a
Linux Scorpius 3.3.8 #3 Wed Oct 16 22:55:53 EDT 2013 mips GNU/Linux
[/size]

web_knows
Posts: 9
Joined: Tue Oct 22, 2013 9:37 pm

Re: WR842ND rebooting on its own

Post by web_knows »

By the way I have reduced even more the torrent client number of concurrent connections (both globally and for each torrent). Also have reduced the download and upload speed limits. Still the router is crashing.

tapper
Moderator
Posts: 1076
Joined: Sun Oct 13, 2013 5:49 pm
Location: Stoke-on-trent UK

Re: WR842ND rebooting on its own

Post by tapper »

hi have you had a look at this
http://www.dd-wrt.com/wiki/index.php/Router_Slowdown
I set my tcp time out to 400 and UDP time out to 130 and have no probs. If that don't help try resetting your router and configure from scratch again and see if it still happens. strange things like this can happen wen you have dun a upgrade and tict the chek box to try and save settings.
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260

web_knows
Posts: 9
Joined: Tue Oct 22, 2013 9:37 pm

Re: WR842ND rebooting on its own

Post by web_knows »

[For some reason I wasn't notified about the above reply]

Anyways, I have changed 2 settings on my torrent client that seem to have helped: 1) turned off DHT and 2) checked an option to only connect to encrypted peers.

I haven't had the chance to test it through yet, hopefully tomorrow. I'll report back here once I do.

Thanks!

web_knows
Posts: 9
Joined: Tue Oct 22, 2013 9:37 pm

Re: WR842ND rebooting on its own

Post by web_knows »

Alright, so it's been a couple of hours and ... so far, so good!

The router hasn't crashed since I restarted downloading torrents after using the options from my previous post, I'm able to download torrents while placing VoIP calls and all.

So clearly the current version of Gargoyle and Transmission's DHT + "poisoned peers" aren't good friends.

Issue resolved, customer happy. Have a good day!

Post Reply