从技术向生活转型，敬请各位期待。

cFosSpeed - problems with pings

Once activated, cFosSpeed will be sending ping packets to the Internet to measure how "congested" the connection is. Without these packets, cFosSpeed Traffic Shaping won't work.

cFosSpeed will only send pings if you are up or downloading at a certain minimum rate. Therefore, the easiest way to confirm that pings are actually getting through is to start an upload that will take at least 30 seconds (e.g., by sending yourself a large e-mail message). Then, check and see if the message balloon appears (see below).

Should there be no response to these pings for an extended period of time, cFosSpeed will indicate this by displaying a balloon. You should then proceed as follows:

1. Do you have a firewall?

Hint:
If the ping problems remain while
the firewall is deactivated,
please uninstall your firewall and try again.

Check if you have a firewall running on your system. If so, make sure the SPD.EXE program (cFosSpeed service) is allowed to send and receive ICMP data. Also note that CFOSSPEED.EXE does not access the Internet.

Important!
When the configuration of your firewall for ICMP data avoids that answers to the cFosSpeed measure pings are allowed, cFos Traffic Shaping will not work. You can check this with a simple tracert command.

2. Enter tracert command

Click Start -> Programs -> cFosSpeed -> Open console, and type in "tracert www.cfos.de". If everything checks out, it should return something like this:

Tracing route to www.cfos.de [194.95.249.23] over a maximum of 30 hops:
	
1    56 ms    56 ms    55 ms  217.0.116.148
2    55 ms    54 ms    54 ms  217.0.74.50
3    54 ms    53 ms    55 ms  k-ea1.K.DE.net.DTAG.DE [62.154.55.154]
4    61 ms    62 ms    61 ms  h-eb1.H.DE.net.DTAG.DE [62.154.49.166]
etc.

What is absolutely crucial here is that there are time values (and not asterisks) displayed in columns 2 through 4..

If that's the case, skip to step 4 below.

However, pings are being blocked if the output reads as follows:

Tracing route to www.cfos.de [194.95.249.23] over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  
etc.

In this case, continue on with step 3 .

3. Tracert does not work

Tracert does not seem to be working on your system. If you do not use a firewall or you use one that does let pings of SPD.EXE through, pings and incoming replies are likely being blocked by another component.

If you are using a router, it must also be set to allow pings to pass through. Configure your router so that cFosSpeed can send outgoing pings (ICMP echo requests - type 8) and receive ping replies (ICMP echo reply - type 0) in addition to time-outs (or ICMP TTL/time exceeded - type 11). You may have to restart your router for these changes to take effect.

Now repeat step 2 above, using the "tracert www.cfos.de" command. Should there still be no pings coming through, chances are your Internet provider may be filtering such data out. In this case, you should contact your provider..

Last possibilty: Disable your firewall and try again. If this still doesn't help, deinstall your firewall and try again.

4. Tracert is working

Tracert is working, but the message balloon still appears: Please check again if your firewall software isn't blocking the pings from SPD.EXE after all.

If, during an upload running at maximum speed (or close to it), cFosSpeed is at any time displaying ping times on the status window, pings are not being filtered by your system but are lost somewhere in the Internet instead. The reliability of ping data can vary widely among different Internet providers. It may also be affected by other factors such as network load, over which cFosSpeed has naturally no control.

If Tracert is working but ping time values never appear on the status window, please send us an e-mail and attach copies of TRACE.TXT and TRACE_OLD.TXT from your cFosSpeed directory. Please make sure to send us these files shortly after the problem has occurred so that they contain all data necessary for closer analysis.

Notes on some specific firewalls or routers

Sygate Personal Firewall:

Under "options," go to the "security" tab and deactivate "DoS detection." This is necessary because otherwise the firewall will wrongly classify the cFosSpeed calibration process as a DoS attack.

Users have also reported that the "Anti-IP Manipulation" must be turned off for cFosSpeed to run without problems.

Agnitum Outpost Firewall:

Here, users have reported that in the ICMP settings you have to check the "Echo reply - outgoing" box, so the firewall doesn't block outgoing replies.

Orange Livebox:

Settings for the Orange livebox with built in Inventel router to allow cFosSpeed pings.

Kaspersky Anti-Hacker:

You can set special rules for each aplication. In this case for SPD.EXE (cFosSpeed service). This allows the cFos communication. Further you can disable that Anti Hacker detects "DoS" attacks, to avoid false Anti-Hacker actions.

You should also activate the option "Allow outgoing ICMP pakets with ICMP-Code: Echo Reply".

The ICMP Settings should be:

ICMP Type 0 (Echo Reply) incoming : allow
ICMP Type 8 (Echo) outgoing : allow
ICMP Type 11 (Time Exceeded) incoming : allow
Other ICMP Types incoming and outgoing : allow

Draytek Router:

Some users have reported that the option "Ip Filter/Firewall Setup - DoS defense" has to be switched off cause otherwise the router filters cFosSpeed PING Pakets.

Linksys wag54g router:

Some users have reported that the option ""Block Anonymous Internet Requests" has to be switched off cause otherwise the router blocks ICMP answers.

Retrieving and interpreting cFosSpeed's ping stats

Open the cFosSpeed console and type in "spd pingstat".

This should yield an output similar to the one below:

Ping statistics:

Total ping requests      107,686        
  done                   107,686     (1)
  ...and only            107,686        
                                        
Total pings sent         106,949        
  strong                 106,778        
  ...and new             106,778     (2)
                                        
Total pongs              106,804        
  found                  106,566        
  ...and strong          106,519        
  ...and strong reply    106,519     (3)
  ...and used            106,519     (4)

Ping outage statistics:
  1 ping in a row 33 times
  5 pings in a row 1 time

Ping src/dst: 192.168.0.100 to 194.95.249.23, ttl 3
Ethernet src/dst: 00:0e:a6:57:9b:0b to 00:11:95:78:27:a4

The three values given for "total ping requests" should be identical. In case there is any great deviation among these, please report it to us.

The value marked (1) should be approximately the same as the one next to (2) . If that is not the case, it is typically strong evidence for a firewall blocking data transmission. As above, a small deviation of several percent isn't dramatic, though.

Values for (3) and (4) should likewise be about the same. If not, do send us a mail.

By the same token, values (2) and (3) should be roughly identical. If this is not so, this usually indicates pings and their replies get lost somewhere "in the Net" (which happens quite a lot). Unfortunately, there is nothing we can do about that.

When writing us an e-mail, please refer to step 4 above regarding what files to attach to your message.

public static void drawSubImg(Graphics g,Image img,int x,int y,int sx,int sy,int swidth,int sheight)
{
  g.setClip(x,y,swidth,sheight);
  g.drawImage(img,x-sx,y-sy,GLT) ;
  g.setClip(0,0,width,height) ;
}