Bad routers

From VuzeWiki
Jump to: navigation, search

List of routers that have problems with Vuze and how to solve them when it's possible

Typical reasons[edit]

Typical reasons, why a router fails with Vuze traffic, are related to the fact that bittorrent traffic (and other P2P solutions) burden your network infrastructure quite much. There are both lots of connections to other users and high amounts of transferred data. DI-524 is an example of a bad router.

That may lead to router crashing due to e.g.

  • too many connections : some home routers have buggy firmware and crash when there are lots of connections at the same time
  • UPnP problems : some home routers do not handle UPnP very well and may crash or act weirdly
  • overheating : some home routers do not have appropriate cooling, and may be subject to crashes due to heat, if you have constant data transfer

Due to (too) many connections[edit]

The following routers have known problems with too many simultaneous connections. Limiting "Max connections globally" in Vuze's Transfer options to 200 or fewer should fix the problems:

  • Belkin 54G F (really bad router for any P2P)
  • D-Link DI-524 (really bad router, slow down dramatically larger than 120 connections)
  • D-Link DI-624
  • D-Link DI-624
  • D-Link DIR-615 D2 (Anything over 800 connections crashes but OpenWRT Barrier Breaker 14.07-rc2 okay!)
  • D-Link DSL-3780 (TalkTalk UK ISPs Fibre router combo) - Anything over 110 crashes, WiFi is worser by 65, Really bad router from the ISP company!)
  • D-Link DSL-G664T
  • Linksys BEFSR41V4/BESR41
  • Linksys WRT54G (upgrading firmware dramatically helps)
  • Linksys WRT54GS v4 (upgrading firmware to DD-WRT v24-SP2 helps HOWEVER anything over 400 crashes.)
  • Linksys Wireless-b
  • Netgear DG632
  • Netgear DG834G
  • Netgear MR814
  • Netgear Rangemax 802.11n WPN824
  • Netgear WGT524
  • Netgear WGR614
  • Netgear Virgin Media SuperHub v1 - R34 (now has been updated to R39 by Virgin Media so okay.)
  • Anything made by Nettopia
  • SpeedStream 5660 in Router/NAPT configuration. Latest firmware is 2.(3).7. Alternate workarounds:
    • Switch to bridged mode. (For security, firewall your network.)
    • When it dies, just power-cycle the router and continue on.
  • W-Linx MB401-S (and SMC Barricade 7004 BR, which is identical in construction)
  • WRT54G/GL/GS
  • TPLink TL-1043ND flashed with OpenWRT (Feb 10 2014 snapshot)
    • My attempts over the last 2-3 weeks have failed to resolved this.
    • Periodic CRON daily restarts and DHT Disabling helps
    • There is also a packet loss issue that gets worse with Vuze and DHT Enabled running.

Due to UPnP[edit]

  • D-Link DI-524 (cause by buggy firmware)
  • Zyxel Prestige 660hw
  • D-Link DI-604 (Updating the firmware helps somewhat, but still buggy)

Due to Port Forwarding[edit]

  • D-Link DI-524 (not port forwarding UDP protocol consistently, extremely unstable)

Due to overheating[edit]

Most home routers do not have proper cooling. Usually no fan and not even heatsinks for CPU. If your router fails/locks after longer use, consider heat issues as a possible reason.

  • Note: overheating issues may also apply to ADSL/cable modems and/or WLAN base stations

The following routers have known problems:

  • D-Link DIR-524 (become very hot after using for 3 hours)
  • D-Link DIR-624
  • D-Link DIR-615
  • Trendnet TEW-652BRP

Installing a small memory-chip heatsink to the router's processor may help to keep temperatures down. Example: RTENOTITLE

Due to modem/router intrusion detection functionality[edit]

  • Speedtouch 780 WL (KPN in Netherlands has enabled "fragment_out-of-order" firewall/intrusion detection function in modem. It is recommended to use a safe password on your router to keep the risk of being hacked as low as possible.

Reason not yet verified[edit]

  • Apple airport extreme (802.11g wireless with wep 128bit)
    Setting the router IPv6 support (under advanced) from local to tunnel may help in addition to the solutions listed below.
  • Cisco 1841 Modular Router
    Starting Vuze and starting a torrent causes external internet access to fail. The following solution will only re-enable external network access until Vuze is started again.
  1. Telnet into the Router
  2. Issue the following command: Clear IP Nat Trans *
  3. Upgrading memory >128MB and installing c1841-advipservicesk9-mz.150-1.M.bin (release 15 IOS) seems to have magically cured this router
  • Motorola 2210-02-1ATT (for AT&T U-verse ADSL2+ HSI)
    Apparently it has some problem handling a large number of different nodes communicating with each other in DHT. Disabling DHT in your BitTorrent client is a work-around, or restart the modem when you have connectivity problems (time-outs reaching new web sites). You might also need to limit the total number of connections in your BitTorrent client to 100 or so.

Usual solutions[edit]

  • Updating the router firmware
    Note: If you consider yourself as an experienced user you can also try to install a 3rd party firmware if there is one for your specific model. Often those 3rd party firmwares are tuned for higher loads. But be warned: A failed firmware installation can render your router useless or require a complicated reset/manual firmware repair procedure.
  • Restricting the number of connections globally in Vuze's Transfer options to something like 100 (or even below)
  • Turning off the UPnP plugin and doing manual Port forwarding
  • Check that your router/modem has no firewall/intrusion detection functionality active, which might prevent connections
  • Binding outgoing connections to a single port (see Advanced network settings)
  • Restricting the number of max simultaneous outbound connection attempts in the advanced network settings.
  • Disabling the DDB plugin
  • Connect to the internet without the router/only the modem (for testing purposes)
  • Getting a new router if all else fails
  • Disabling DHT (which seems to communicate with a large number of peers over UDP, quickly filling the NAT state tables which causes new connections to fail)

See Bad ISPs for troublesome [[1]].