legacycentral bbs

I tried this from two independant connections with similar results

Reply from 63.230.12.202: bytes=32 time=58ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=55ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=61ms TTL=50
Reply from 63.230.12.202: bytes=32 time=62ms TTL=50
Reply from 63.230.12.202: bytes=32 time=74ms TTL=50
Reply from 63.230.12.202: bytes=32 time=58ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=56ms TTL=50
Reply from 63.230.12.202: bytes=32 time=72ms TTL=50
Reply from 63.230.12.202: bytes=32 time=85ms TTL=50
Reply from 63.230.12.202: bytes=32 time=88ms TTL=50
Reply from 63.230.12.202: bytes=32 time=64ms TTL=50
Reply from 63.230.12.202: bytes=32 time=78ms TTL=50
Reply from 63.230.12.202: bytes=32 time=55ms TTL=50
Reply from 63.230.12.202: bytes=32 time=97ms TTL=50
Reply from 63.230.12.202: bytes=32 time=66ms TTL=50
Reply from 63.230.12.202: bytes=32 time=56ms TTL=50
Reply from 63.230.12.202: bytes=32 time=66ms TTL=50
Reply from 63.230.12.202: bytes=32 time=58ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=63ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=67ms TTL=50
Reply from 63.230.12.202: bytes=32 time=59ms TTL=50
Reply from 63.230.12.202: bytes=32 time=57ms TTL=50
Request timed out.
Reply from 63.230.12.202: bytes=32 time=55ms TTL=50
Reply from 63.230.12.202: bytes=32 time=61ms TTL=50
Reply from 63.230.12.202: bytes=32 time=58ms TTL=50

When this happens Im unable to fully load a page.

Yeah, that happened to me about half an hour ago too.

Last time I left an xterm open pinging the server, I got an email from the guy who runs the box saying to stop it. :)

Please, PLEASE do NOT ping the box.

We're aware of the issues, this box is hosted at a poorly run ISP, and we're in the process of getting a box together for a "real" colocation.

Just bear with us ang go with the flow for a bit longer...

Dave

im curious what pinging means. i heard somethings but i would like to know the scoop.
thanks,

Pinging is one of the first signs of detonation, sounds like a marble is rattling around in your engine... Best to go up one grade of gas...



I have no idea what pinging is in computer terms, but I do think this board is growing too big for its britches...

ping is the amount of time it takes to send a packet from your terminal to another and back again.

Well, that's what a ping time represents. The action of pinging a network host is to send a special type of packet (ICMP ECHO_REQUEST) requesting an immediate response (ICMP ECHO_RESPONSE) from the host. By measuring the time between when you sent the request and received the response, you can infer some measure the quality of your connection to the host.

DLC, you ask us not to ping it because you dont want people to know of the bad response time and lost packets?

Dont assume anything about my connection, I tried on both a team of 3 load balanced t1 (packet based) and a single t3 that currently only has 4 hosts connected. On both of these networks I was connected to a switch directly connected to the outside router so no other device is adding latency.

You shouldnt worry, I was sending pings at a very low rate. I dont plan to smurf you or anything!

For the non techie peeps......the DDOS attacks you may have heard of a while ago, essentually used pinging to cause them. Granted it's a little different, but same principle......which is probably why dave doesn't want people pinging the server.

I have a smurf utility that lets you run multiple instances. Now imagine 10 large offices worldwide (more than 1000 hosts) and 10 instances of the utility hitting the broadcast address of those networks with the source being the site.

Thing is, I would never do it. If anything Id figure out a way to speed the site up!