[Q]: Howto setup WRT54GS 1.1 to use donkey/mule etc.

Discussion in 'Cisco/Linksys Wireless Routers' started by kpg, Feb 18, 2005.

  1. kpg

    kpg Network Guru Member

    maybe this is the wrong forum or a _bad_ question. if so, please direct me to a more appropriate place.

    i would like to set up my linksys wrt54gs running dd-wrt firmware to use donkey/mule "filesharing". torrent runs fine out of the box..
    but how do i get the donkey/mule running?
    the settings are:

    Firewall Protection: Enable
    Additional Filters: Filter ActiveX
    Block WAN Requests: Filter IDENT(Port 113)

    Applications and Gaming:
    Port Range forward.

    App start end proto address enable
    emule 4662 4662 tcp mystaticaddress enabled
    emule 4672 4672 tcp mystaticaddress enabled
    overnet 9217 9217 tcp mystaticaddress enabled
    overnet 5468 5468 tcp mystaticaddress enabled

    i do not use any port triggering options (should i)

    with the above setup i get very poor download speeds if any at all.

    Question: is the setup ok? which addtional filters should i apply?
    which ports should i open?

  2. linksysonline

    linksysonline Network Guru Member

    You could always try to set your PC in the DMZ and see if things increase. If it does then we know there are other settings that need to be done.
  3. Praktiker

    Praktiker Guest

    WRT54GS and emule

    Hi, I just did what I found on the net. Forwarding of 4662 TCP, activated it and put my PC in the DMZ. Still low ID!
    What else can be done?
    I need help...
    regards Praktiker.
  4. silviemeis

    silviemeis Network Guru Member

    Maybe a problem with your pc? Do you have a firewall running there? Do you use windows xp windows 2003 windows 3.11? Norton firewall? windows xp sp2 firewall?
  5. Demon

    Demon Network Guru Member

    4672 should be UDP

    4672 should be UDP for emule
    Not sure about overnet

    Also - where is your internet connection coming from? Is it another router? If so, port forwarding must be set up on this too!
  6. jepe

    jepe Network Guru Member

    Had the same problem.
    You should do "Port Triggering" when you run the DHCP-Server.
    And do not just trigger one port (e.g. 4662) but at least 4 ports in series (e.g. 4660-4664)

    With stativ IP "Port forwarding" is OK.
    But you have to foward at least 10 ports in series (e.g. 4660-4669) and you have to write the last 3 digits of your internal IP in the right box (e.g.

    And 4672 (= 4670-4679) is UDP !

    At least it worked for me.

    good luck

  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