P2P resulting in a slow connection problem (I know...again)

Discussion in 'Cisco/Linksys Wireless Routers' started by Prodoc, Mar 20, 2006.

  1. Prodoc

    Prodoc Network Guru Member


    Like a lot of other people I'm stuck with the problem that using eMule is resulting in a _very slow_ connection. Downloading is going fine but I can't browse a single website anymore.

    I've been going through this forum and I've been trying every trick in the book without results. I used the latest default firmware, tofu for a while and now Thibor14, with no obvious difference.

    OS: Windows XP sp1

    I limited the connections in eMule to almost it's minimum:
    Queue Size: 1000
    Max. Connections: 50
    In 5 sec: 10
    Max Sources Per File: 150

    Router: WRT54G v2.2

    Methods tried:
    - Port Range Forward
    - Port Triggering
    - DMZ
    - QoS
    - P2P QoS

    Sometimes it works fine for a day or two but this doesn't happen a lot. Sometimes my system keeps running fine but other in the network (not using P2P software) will have problems.

    What should I do? What am I doing wrong? Is it the router version?

    Can you give me a list of the exact features I should configure in the router (Port Range Forward vs Port Triggering, etc.)?

    Is it worth trying other firmware releases (Tarifa, MustDie, etc)?
  2. dvaskelis

    dvaskelis Network Guru Member

    How did you configure QoS? That plus the Conntrack settings seemed to make all the difference for me.
  3. vincentfox

    vincentfox Network Guru Member

    Here's an idea, uninstall eMule and replace your P2P software, instead of fiddling with the router.
  4. Prodoc

    Prodoc Network Guru Member

    I set the eMule ports in the 'Application Priority' section with the 'Priority' set to 'low'. I also tries the 'P2P QoS' with 'All Supported Types' set to 'low'.

    Where can I find this 'Conntrack' setting?

    What alternative do you suggest? I'm using eMule Plus at the moment. Won't other eDonkey network supported programs cause the same problems because of to the required amount of connections?

    Can this be considered a bug in the P2P software? What is the exact problem? I read that P2P programs tend to not close the connection but instead rely on the router to time-out. This makes me wonder, can't this behaviour be changed? The open connection is required when actually sending or receiving data from a different user but not when you're in the queue. It might as well open a connection, determine its position, close it when it's not its turn yet and try again later.
  5. dvaskelis

    dvaskelis Network Guru Member

    For just a server role? Or client too?

    You may also want to set DNS to Highest, HTTP/HTTPS to High and Prioritize ACK. If you somehow missed some P2P traffic, at least web browsing will still have priority.

    Also, if you're missing some P2P traffic somehow, you can also set High Ports to Low and that will likely catch it. This may also de-prioritize some other traffic too, but it sounds like you're stuck for an answer.

    How did you set your upstream bandwidth? This is pretty important in making QoS work effectively. With QoS off, the Speakeast Speed Test works well for me.

    In Administration, Management tab under Conntrack settings:

    Established State Timeout: 600 seconds
    Max Connections: 4096

    The following startup script from Avenger 2.0, the original author of HyperWRT, also sets these values and a few others:

    echo 4096 > /proc/sys/net/ipv4/ip_conntrack_max
    echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
    echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
    echo 512 > /proc/sys/net/ipv4/neigh/default/gc_thresh1
    echo 2048 > /proc/sys/net/ipv4/neigh/default/gc_thresh2
    echo 4096 > /proc/sys/net/ipv4/neigh/default/gc_thresh3
    echo "600 1800 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts
    That last 'echo "600...' line and the following '>/proc...' are all on one line.

    Some people have suggested that these settings are too aggressive, and that the defaults in HyperWRT Thibor are more appropriate in most situations. But, if you're having P2P trouble I'd give them a try.
  6. vincentfox

    vincentfox Network Guru Member

    I've long ago switched to Torrent-based programs.

    uTorrent and Azureus work very well. And they are not potentially sypware and adware-ridden like the old FasTrack/Kazaa-based programs.
  7. jchuit

    jchuit Network Guru Member

    Having slow internet.

    To Prodoc

    If the internet speed is low I allways do the following:

    Install all the latest service packs from Microsoft.
    Install a good virus protection, like the norton AV 2005 or 2006.

    You can also try to disable the UPNP setting.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice