search

juanfranblanco / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Getting WAN IP kills router #178

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem? (after a sudden crash)

1. disconnect all wires, USB stuff, wait 5 minutes to semi-cool down
2. plug in AC
3. wait a few seconds to boot-up
4. plug in LAN cable (DHCP enabled)
5. wait a few seconds to get an IP address
6. start pinging the router, it works properly
7. plug in WAN cable (Automatic IP, cable TV modem)
8. watch the router dying

What is the expected output? What do you see instead?

Get a WAN IP, and route properly, don't crash.

What version of the product are you using? On what operating system?

Asus RT-N56U, RT-N56U_1.0.1.8d-p3

Please provide any additional information below.

The router works properly. Sometimes it suddenly crashes, no webUI, no ping 
response, nothing. Leds are lit. See the pic attached, it's funny...

Original issue reported on code.google.com by cono...@gmail.com on 19 Mar 2012 at 8:33

Attachments:

GoogleCodeExporter commented 9 years ago 
And now, it's okay... Might be my HW's issue?

Original comment by cono...@gmail.com on 19 Mar 2012 at 8:37

Attachments:

GoogleCodeExporter commented 9 years ago 
Does it get very warm? Because normally it shouldn't. I bought my device about 
a year ago. So, every time I touched it with my hand, it was a little bit 
higher than body temperature.
Does it stands on platform?..
Please, try to get log when it will die again.

Original comment by d...@soulblader.com on 19 Mar 2012 at 11:57

GoogleCodeExporter commented 9 years ago 
Something like that happened to me. And it seems to be caused by having 
firewall logging enabled. I think in my WAN there are some computers infected 
with viruses which constantly scan for open ports this in turn will cause the 
router to log them as intrusion attempts at a very high rate.

During this I had huge latency while trying to ping my router from LAN.

One quick fix would be to turn off the logging here:
1) http://192.168.1.1/Advanced_BasicFirewall_Content.asp
2) general-> Logged packets type: -> none

In my opinion the logging iptables rules are wrong since they don't have a 
maximum rate of logging like the one bellow:

limit

This module matches at a limited rate using a token bucket filter. A rule using 
this extension will match until this limit is reached (unless the '!' flag is 
used). It can be used in combination with the LOG target to give limited 
logging, for example.
--limit rate[/second|/minute|/hour|/day]
Maximum average matching rate: specified as a number, with an optional 
'/second', '/minute', '/hour', or '/day' suffix; the default is 3/hour.
--limit-burst number
Maximum initial number of packets to match: this number gets recharged by one 
every time the limit specified above is not reached, up to this number; the 
default is 5.

See:
http://linux.die.net/man/8/iptables

Original comment by constant...@gmail.com on 22 Mar 2012 at 8:06

GoogleCodeExporter commented 9 years ago 
Dear d...@soulblader.com,

Yes, it gets pretty warm :/ approximately 50°C. Should I return it to the 
seller? (with the original fw of course :P) I bought it 2 months ago...

I had issues when the orig fw was installed, too.

Dear constant...@gmail.com,

Yes. The error instantly occurs when I enable my firewall, and its logging 
mechanism. I'll check the things you mentioned above. I'll share my experiences 
afterwards.

I'll enable a syslog server to preserve the logs on my computer. Thanks for you 
replies. :)

Original comment by cono...@gmail.com on 22 Mar 2012 at 8:35

GoogleCodeExporter commented 9 years ago 
I don't know if that logging is turned on by default but if it is any bad 
person can bring down most of ASUS RT-N56U routers by simply flooding the 
router with TCP requests on port 80 for example. 
This seems quite serious to me.

Original comment by constant...@gmail.com on 23 Mar 2012 at 4:07

GoogleCodeExporter commented 9 years ago 
Disabling the logging solves the problem. Thanks for your help!

Original comment by cono...@gmail.com on 8 Jun 2012 at 10:49

GoogleCodeExporter commented 9 years ago

Original comment by d...@soulblader.com on 30 Jul 2014 at 12:49