| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Trivia |
ml> ping sucks for diagnostics... use traceroute but understand that, ml> like ping, not all systems will respond... traceroute will get you ml> responses from systems in the path whereas ping doesn't and so ml> doesn't give any idea where the breakage may be... RW> Tracert sucks as well. It hanged somewhere in Tennesee when I was RW> trying to figure out why I couldn't connect with 1:19/0. He lives RW> in Mississippi or western Alabama. (1:18/x territory) like i said, we can only use the data that is passed back from the requests... i, too, did the traceroute game with roger a while back and then things started working but only some systems give responses... then you get some with circular loops going on which get reported to have their routing fixed... then there's the ones with a lot of traffic which drop some packets on life time expiry... )\/(ark* Origin: (1:3634/12) SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 953 @PATH: 3634/12 123/500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.