• How can I prevent problems when using eMule P2P software?
• Why is my actual throughput speed slower than 54/108 Mbps?
• Why is wireless LAN throughput very low or erratic?
• How to increase TCP window size (RWIN) on DGL-4100/4300
• Why are my pings the same or higher with my Gaming Router?

There are several issues that might occur when using eMule P2P software and some routers (including some D-Link routers). Although we have seen several firmware releases that attempt to address eMule problems, they seem to persist and become frequent issues in the forum.

The most frequent behaviors related to overloading are spontaneous reboots, gradually reduced performance, or a non-responsive router:

•When KAD is used, the NAT table overflows and the router reboots. While some users have reported various improvements using various firmware versions, there is no certain cure except for not using KAD.

•Under normal use, the router slows, locks, or reboots. You may turn off the router's DNS Relay feature, which on later firmware versions is located on the "Home / LAN" configuration page.

•When there are hundreds of connections, the router slows or reboots. You may configure eMule to maintain fewer simultaneous connections.

Other frequent issues:

•The file sharing network reports "Low ID," indicating a firewall problem, even after you properly configured a Virtual Server entry. After setting a firewall rule, shutdown the eMule software completely until the TCP connection is closed. Then, restart eMule.

•The router log indicates an incoming "Ping of Death attack" on my eMule port. This is usually not an attack, but is believed to be a misconfigured or improperly compiled eMule client. It may be ignored or you may turn off Attack Logging in Log Settings.

got feedback? got feedback?

Any feedback you provide is sent to the owner of this FAQ for possible incorporation and shown publically as well.

by funchords
last modified: 2005-08-14 04:20:32

This is best answered here:

»Wireless Networking Forum FAQ »How fast can I actually download over a wireless network?

got feedback? got feedback?

Any feedback you provide is sent to the owner of this FAQ for possible incorporation and shown publically as well.

by funchords

Very low or erratic throughput between LAN clients is not normal.

For the purposes of this FAQ entry:

•Very low is 2% or less of the expected 802.11 data rate (e.g. 11 or 54 Mbps).
•Erratic is a sudden drop to zero or nearly zero percent of the expected 802.11 data rate for several seconds. Or, a communication that simply stops and does not resume.

There are two factors to consider in troubleshooting this problem:

•is this problem limited to wireless communication? or,
•does this problem occur between the LAN members if they are wired?

To determine whether the wireless connection is involved, eliminate wireless from the equation and attempt the traffic again.

•Repeat the problem, writing down the exact steps necessary to do so
•Disable the wireless network device in your computer(s)
•Connect your computer(s) using an Ethernet cable. If you are using a wireless router with LAN ports, connect to the LAN ports. If you are using an Wireless Access Point, connect the computers directly using a cross-over cable.
•Create the traffic again.
•If the problem still exists between wired LAN clients, the resolution should start with considerations other than wireless -- such as your router, your network stack, or the network software or hardware on the other LAN client involved. This FAQ entry will not be of any further help.
•If the problem no longer exists between wired LAN clients, the solution will involve adjusting the wireless portion of your network and may be covered by the remainder of this entry. To continue, first return your network back to its wireless topography.

The most frequent problems and resolutions are:

•An enhanced mode is involved in the issue. As a work-around resolution, reduce or eliminate the enhanced modes such as 4x, Super-G, faster connections than the normal 54 Mbps 802.11g or 11 Mbps 802.11b, and etcetera. Reconfigure this on the AP or wireless router.
•The client drivers or AP firmware have a problem. Ensure they are updated to the latest versions. Reboot the AP. Check the support databases and forums for the brands involved.
•The wireless connection is poor, and the AP or wireless card is stepping down the data rate to reduce errors. Experiment with adjusting the location of the AP and/or client(s) involved. Even if the signal is strong, a poor signal pathway can cause the digital signal to have an imprecise (or "fuzzy") quality. Even an adjustment of a few feet can change this condition for better or for worse. When a large amount of data is traversing, the number of data errors climb and the AP/Clients react to that by lowering the data rate.
•The client hardware is misconfigured. In the Network Connections folder, open the Properties page for your wireless connection. Click on Configure toward the top of the dialog, then click on Advanced. Return any parameters you previously changed here to factory defaults. If you have made previous changes, but do not remember what the defaults were, you can uninstall and reinstall your hardware to return to the defaults.

got feedback? got feedback?

Any feedback you provide is sent to the owner of this FAQ for possible incorporation and shown publically as well.

by funchords
last modified: 2005-08-14 04:24:20

Users have noticed that the SPI setting seems to affect the maximum TCP window size. Follow these suggestions provided by joe_dude . Note: Always consider performaing a backup or creating a Restore Point before editing the Registry.

1) On the router, disable SPI under Advanced -> Firewall.

2) In Windows 2000/XP/2003, add/change the value DefaultReceiveWindow in HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Afd -> Parameters to greater than 65535. You may also want to increase DefaultSendWindow as well.

I recommend matching DefaultReceiveWindow to GlobalMaxTcpWindowSize in HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> Tcpip -> Parameters.

got feedback? got feedback?

Any feedback you provide is sent to the owner of this FAQ for possible incorporation and shown publically as well.

by joe_dude edited by funchords
last modified: 2005-09-23 13:18:34

The ping tool's protocol (ICMP) is not given high priority by the GameFuel* technology.

The best way to tell that it is helping is to turn on GameFuel and play the game. Your game performance should no longer suffer due to outgoing lag.

Where your game performance used to suffer due to your household's other internet use (such as transferring files), responses to your keyboard or joystick should seem much more responsive than it did before.

During light networking periods, where no lag was being created by other network activity, game play should be unchanged.

How GameFuel technology (prioritization) works:

When you use your mouse, joystick, or keyboard in an online game, data is sent to the game's server.

Without prioritization, each new piece of data is placed at the end of the outgoing queue; the last data to enter the queue is the last to go out. Your "fire" button data must wait for the data that are already ahead of it in the queue. By the time your command to fire clears your router, your character may already be dead.

With prioritization, the data is prioritized (either by your rules or by automatic classification). Any new outgoing data is inserted into the queue based on this priority. New, higher priority traffic (such as an interactive game) is placed near the front of the outgoing queue, ahead of other data. New, lower priority traffic (such as a long, steady file transfer) is placed near the end. Your "fire" button data jumps ahead of the data that are already in the queue. Your command reaches the game's server faster, and so your character reacts faster to your commands.

Notes:

The author claims no particular inside knowledge of GameFuel prioritization specifically, but he understands how prioritization works.

GameFuel can help your own congested network work better, but it cannot do anything about internet congestion that exists outside of your network.

*The GameFuel trademark is the property of its owners, and is used here to describe features of the D-Link products that use it.

got feedback? got feedback?

Any feedback you provide is sent to the owner of this FAQ for possible incorporation and shown publically as well.

by funchords
last modified: 2006-08-11 12:12:51