200 Part II . Running the Show The
200 Part II . Running the Show The r flag denotes that the server machine will be the receiver. The s flag, in conjunction with the r flag, tells ttcp to ignore any received data. Have someone outside your data link, with a network link close to the same speed as yours, set up a ttcp sending process: # ttcp -ts server.example.com ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp -> server.example.com ttcp-t: socket ttcp-t: connect Let the process run for a few minutes and then press Ctrl+C on the transmitting side to stop the testing. The receiving side will then take a moment to calculate and present the results: # ttcp -rs ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ttcp-r: socket ttcp-r: accept from 64.223.17.21 ttcp-r: 2102496 bytes in 70.02 real seconds = 29.32 KB/sec +++ ttcp-r: 1226 I/O calls, msec/call = 58.49, calls/sec = 17.51 ttcp-r: 0.0user 0.0sys 1:10real 0% 0i+0d 0maxrss 0+2pf 0+0csw In this example, the average bandwidth between the two hosts was 29.32 kilobytes per second. On a link suffering from a DDoS, this number would be a fraction of the actual bandwidth for which the data link is rated. If the data link is indeed saturated, the next step is to determine where the connections are coming from. A very effective way of doing this is with the netstat command. Type the following to see connection information: # netstat tupn Table 6-1 describes each of the netstat parameters used here. Table 6-1 netstat Parameters Parameter Description -t, –tcp Shows TCP socket connections. -u, –udp Shows UDP socket connections. -p, –program Shows the PID and name of the program to which each socket belongs. -n, –numeric Shows numerical address instead of trying to determine symbolic host, port, or usernames.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.