WRT54g + emule over wireless

Discussion in 'Cisco/Linksys Wireless Routers' started by informaniako, Dec 8, 2005.

  1. informaniako

    informaniako Network Guru Member

    Well i want to know from all of wrt54g owners if this router can manage a wireless connection running eMule and/or torrents over it. I'm thinking in buying an wireless pci adapter for my pc but my question is: Will i get the same connection over wireless? Will wireless manage to keep all the connections eMule and torrents make?

    I need some advice about this. I still need some advice for a wireless pci adapter but i've asked that in another thread :)

    So, wrt54g owners, how this router acts with a emule over wireless? :D
  2. drdivago

    drdivago Network Guru Member

    No problem with a WMP54G v2 using latest Broadcom drivers

  3. simax

    simax Network Guru Member

    Works fine. But remember that the default concurrent connections limit on DD-WRT firmware is 512 (IIRC). The default for eMule is 300 or so.

    You do the math.

    Increasing WRT54G's limit to 1024 is a commonly accepted option. And running >1 emule per WAN connection, not wise.

    Let us know.
  4. informaniako

    informaniako Network Guru Member

    thanks for the replies :D

    simax, i use hyperwrt 2.1b1 tofu10 and i suppose that the limit is the same as the DD-WRT.

    now, about increasing that limit to 1024, won't that change mess with the router performance? how do i change that limit? that might help me with a problem i have. I'm always disconnecting from servers but that only started happening almost a month ago. before that i've never had such problems.

    looks like i'll add this code
    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
    to the startup script to see if it solves the problem like tofu says in the readme file.
  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