Hello,

I'm using FreeWRT 1.0 on a Asus WL-500g Premium and have a strange
problem which seems to be related to the bittorrent protocol (or maybe
the way how Azureus implements it). I'm not ABSOLUTELY sure about this
but I could reproduce it several times.

After I had installed FreeWRT I did not experience any problems in the
first 2 days. Even downloading multiple Gigs of data via SCP worked
flawlessly. Then I started the bittorrent client Azureus. After some
hours of work (Down and upstream around 10KB/s) I lost the Internet
connection and I could no longer access the router via LAN or WLAN.
After resetting it everything was working again. Azureus continued with
it's work. Some hours later the router was again no longer available. A
reset fixed it again.

The next day I did not use Azureus and the Internet connection was
stable, the router was accessible all the time. The next day I used
Azureus again and the router died again. The next day it worked
flawlessly because I did not use Azureus. I begin to see a pattern here.

Yesterday I noticed another strange thing. Azureus was running again and
 I was online in Second Life. Then I noticed that I could no longer
access websites, Azureus stopped working and I could again no longer
access the router. But Second Life was still working for some minutes.
Normally I can no longer move in there when the Internet connection is
lost but I could even teleport to other regions, so Second Life
definitely had an Internet connection. But after some minutes this one
died, too. So maybe for some time existing connections are still working
while new connections are blocked.

Any idea what can cause this? Because the router always dies only when
Azureus is running I'm pretty sure its related to the bittorrent
protocol. Maybe bittorrent opens lots of connections during the time the
client is running and the router keeps track of all these connections
(to masquerade them) and then some internal table is full and netfilter
stops working? Are there tools to prove this? Can I display the current
NAT translation table?

Or does FreeWRT use a special NAT module for the bittorrent protocol
which can cause such problems? Unfortunately I don't have a serial
console yet so I can't see any console messages after the router dies.

-- 
Bye, K <http://www.ailis.de/~k/>
[A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391]
(Finger [EMAIL PROTECTED] to get public key)
_______________________________________________
freewrt-users mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-users

Reply via email to