Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gumb]

Hi

I have an ubuntu linux operating system (dapper). I installed amule for the first time recently and, at the first sight, everything was going fine. but after a while, I noticed what I now see happens every time: my Internet connection seems to be blocked and everything ends in time out. I find this might be a problem with the network send buffer because when I run tcpdump and open the browser, I get no dumped packages while it is trying to resolve the ip of the homepage. the only solution I figured out until now was to kill amule and deactivate and activate the network interface. it happens about 20min after I connect to an e2dk server and being uploading. I have 100 Kb/s and 20 Kb/s of download and upload limits, respectively and my network connection would easily support more. Also, I'm forwarding all the necessary ports in my router, as far as I know. Does anyone know how to solve this problem? 'cause I'm somewhat new to linux and can't go any further in solving this.

Many thanks in advance
gumb

[Kry]

Search forum. countless posts about this, router to blame.

[gumb]

I searched the forum and could'n find any solution. The problem cannot be from the router as it remains when I connect directly to the modem! I tried do reduce upload and download rates, the number of maximum connections, the number of connections per second and disable kad. Nothing had any impact, except maybe reducing the time it would take for the connection to become obstructed.
If any other post explains how to get rid of this problem please tell me which because I couldn't find it.

thank you again
gumb

[gumb]

please could anyone help me. i'm really lost with this

[vdb]

It seems that your problem is stuck a bit, let's see if we can do something about this. Of course some information is required:
- What speed is your internet connection, down/up in kilobits per second, is it DSL, (euro)DOCSIS or fiber?
- What type of router do you have, or is your pc connected directly to the internet modem? Do you have a manual of the router at hand in case it requires changing of settings?
- Do you run a firewall application on your Linux machine? If so, have you tried turning it off and what happens then?
- What versions of wxWidgets are you using? Did you compile aMule yourself or did you use a pre-compiled binary? Did you try upgrading to 2.1.3 yet?

Let's start from here and see where it takes us.

[gumb]

Thank you for your help vdb. The answers to your questions are:

-I have a cable connection with 8192 Kbps downstream and 384 Kbps upstream;
-As I said, I have a router but I tried connecting directly to the modem and the problem is there either way. Besides, I belive my router settings are correct and I always get High ID while I'm connected;
-I haven't got any firewall on my system, as far as I know, unless my ubuntu dapper distribution comes with one set by default, but I don't think so;
-Sorry I don't even know what wxWidgets are :S I installed amule through apt-get. I didn't upgrade to 2.1.3 because it's not on the stable repositories but I will try to do so and see if the problem continues, then I will post what happened.

Thank you again
gumb

[gumb]

ok I just installed the 2.1.3 version of amule, removed all the old settings and started all over. I could easily connect with HighID to e2dk and kad but after about 20min, the same thing happened.
I'm clueless...

gumb

[vdb]

About the wxWidgets, if you type "amule -v" it will show you what version is installed.

But apart from that it is odd that it happens after 20 minutes. This could indicate that perhaps not your system is at fault, but that your ISP uses some form of traffic screening and after seeing p2p traffic for 20 minutes decides to drop your connection.

What happens if you set your upload limit to 11 kB per second, does it take twice as long before the internet connection drops? And if you set it to 3 kBps, does it take 6 times as long? And perhaps also you can experiment with a lower amount of client connections. This is 4000 as a default, try setting it to 1000 or lower in the preference menus. Also you might want to try to set the value for connections per second to 1, and go up from there.

In the past there were posts about DLink routers having troubles with p2p traffic, this is what Kry was referring to.

[gumb]

well, the output of amule -v is the following:

"aMule 2.1.3 using wxGTK2 v2.6.1 (Unicoded) (OS: Linux)"

About the 20 minutes, it is not really a pattern. Usually it takes around that but sometimes it takes less time and sometimes it takes longer (as long as 1h30 or more). I tried it now with the upload at 6kb and download at 24kb and it took 3min to "constipate" the connection.

I also don't think it's because of my ISP blocking p2p trafic because, as I told you, I had emule working fine on windows and I never experienced anything like this.

About the number of connections and all those values, I already have them really low...

[gumb]

Another thing I noticed is that it takes less time if I'm downloading something else or using the internet in some other way (I thing even browsing has some efect). With amule closed, however, I had no such problem until now, even downloading at 600kb/s sometimes...

[pepe0008]

Hello.

I'm having the same problem. I have a linux server with Linux 2.4.26 running Debian 3.1 (stable) without X-Windows, and it's job is mainly to run aMuled. I was previously running a backported version of amuled 2.0.3, and I was having the same problem described above by gumb, which I thought was caused by the somewhat older version of aMuled that I was using. I have now upgraded to a backported version of amule 2.1.3, and I have the very same problem in the same terms.

The upgrade process went like this:

   - apt-get install amule-daemon
      Inst amule-common (2.1.3-1 amule-debian.dyndns.org)
      Inst libwxbase2.6 (2.6.3-2 amule-debian.dyndns.org)
      Inst amule-daemon (2.1.3-1 amule-debian.dyndns.org)
   - apt-get install amule-console-utils
      Inst libfreetype6 (2.1.7-2.5 Debian-Security:3.1/stable)
      Inst libgd2-noxpm (2.0.33-1.1sarge1 Debian-Security:3.1/stable)
      Inst amule-console-utils (2.1.3-1 amule-debian.dyndns.org)

Also, I changed my ports to see if it made a difference, but the problem remains the same.

- old ports: TCP/4665, UDP/4675, UDP(tcp+3)/4668
- new ports: TCP/64665, UDP/64675, UDP(tcp+3)/64668

I always get HighID and the router has these ports properly NATed to my Linux server. My connection is ADSL 4Mb down, 512 Kb up, and I have a router 3COM OfficeConnect Remote 812 (with firmware V2.1.5).

I would like to note that I also have a linux desktop with Linux 2.6.8 and Debian 3.1, running 24/7 the monolithic full-blown aMule 2.1.3, and it has never had this problem. Also, my brother runs eMule 0.47a in his WinXP laptop, and he has never experienced any blocking whatsoever. (The upload and download bandwidth limits in eMule/aMule are carefully set in the three computers to about 80% of nominal capacity of the line, in aggregation.)

These are the settings on these aMule/eMule versions:

-linux server, amuled 2.1.3 (the one with problem): Speed limits, up 20 Kb, down 90 Kb; Max. sources per file: 300; Max. connections: 400; Max. new connections / 5secs: 20. [aMuled 2.1.3 using wxGTK2 v2.6.3 (Unicoded) (OS: Linux)]

-linux desktop, amule 2.1.3 (works fine): Speed limits, up 10 Kb, down 50 Kb; Max. sources per file: 500; Max. connections: 500; Max. new connections / 5secs: 100. [aMule 2.1.3 using wxGTK2 v2.6.3 (Unicoded) (OS: Linux)]

-WinXP laptop, eMule 0.47a: my brother is away on holidays, it is powered off.

I mainly use the aMuled in the linux server to powershare some releases of mine, whereas I use the aMule in my linux desktop to do regular P2P grabbing.

The network connection blocking only happens for amuled in the Linux server, the Linux desktop running monolithic amule is not affected at all. Also, the network connection block happens about every 10 minutes, and lasts from only one or two minutes, to sometimes up to six or seven minutes. In any case, it certainly is something cyclical.


Screenshot of amuled upload network block in linux server:


- - -


Screenshot of upload network traffic drop of amuled in the ADSL router:


- - -


Screenshot of amule working fine at the same time on the linux desktop:




My guesses are two possible causes: my ISP doing some network throttling, or my ADSL router being somehow overwhelmed.

However, I don't think I am overrunning my router's memory: This is a screenshot of the NAT mappings and open connections in the router at the time the amuled network block happens (I don't think I am overrunning the router's memory or CPU):



- - -

So I have been with this problem at least for three of four months now, and I cannot find how to solve it.

Does anyone have any ideas?

Thanks a lot. :-D

[vdb]

Hmm, didn't see any mentioning of emule in your posts, so I didn't know that.

If it takes less time when you are downloading, it indicates that it is a problem on your machine or router: More open connections, faster saturation of buffers. And since you have tried a bridged connection to the internet, I would certainly look at your Linux. Unfortunately I know nothing about Ubuntu. I don't suppose it's an option to re-install using a different distribution? (Mandriva works great for me, except that KDE 3.4 is crap...)

Maybe Ubuntu sets the default settings for TCP fragmentation buffers really low? If you check the values of /proc/net/sys/ipv4/ipfrag_low_thresh  or /proc/net/core/rmem_max? (use the command "cat /proc/net/sys/ipv4/ipfrag_high_thresh" etc.). Search the internet a bit on nice values for this, it might help to up them a bit, start by doubling them.

Anyway, there might be a bottom line to all: If emule works well, you might have to consider just go with Windoze.......

[vdb]

Hmm, this 10 minutes = 600 seconds, just so happens to be the default value for /proc/sys/net/ipv4/ipfrag_secret_interval, the interval in which the ip stack recalculates all fragmented packets.

What if you set this value to a different one? Use echo 300 > /proc/sys/net/ipv4/ipfrag_secret_interval and see if it now takes 5 minutes for the connection to drop? If this is the case, you might want to consider changing the values for ipfrag_low_thresh to double the current value, same as ipfrag_high_thresh.

For reference, the values for the buffers on my Mandriva with kernel 2.6.12 are:
/proc/sys/net/core/rmem_default         110592
/proc/sys/net/core/rmem_max              110592
/proc/sys/net/ipv4/ipfrag_low_thresh   524288
/proc/sys/net/ipv4/ipfrag_high_thresh  1048576

[pepe0008]

Hello.

I'm the guy above with the long post and the screenshots. Well, I have solved my problem, which finally I could trace to a borked network card in the linux server. What a shame!, I am sorry for all that noise here from me.

So my suggestion to gumb would be to try to replace the hardware, especially the network card(s) involved...

Regards.

[gumb]

At this point I'm pretty sure the problem is about the way my linux is configured because I' have excluded the problems with the router as with any other hardware or network connection because everything worked fine in windows. So I would now change the values of ipfrag* to the ones suggested by vdb, but I don't now how to do this because they don't look like regular files: when I do cat I am able to see the value inside but when I open it to edit, the file seems empty... I also tried $sudo echo 524288 > ipfrag... but it still tells me I don't have permissions, even with sudo. Can you tell me how to change it?
Do I have to do anything to the kernel after I changed those values (like recompiling it or something like that)?

Once again, thanx a lot for the help
gumb