| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Trivia |
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) ml> like i said, we can only use the data that is passed back from the ml> requests... RW> And some that isn't passed back. The stuff that should be there, RW> but is missing. yes, we do see that data is missing and from what IP... "should" is subjective, though, because it is not required to reply to those protocol requests ;) ml> i, too, did the traceroute game with roger a while back and then ml> things started working but only some systems give responses... then ml> you get some with circular loops going on which get reported to have ml> their routing fixed... then there's the ones with a lot of traffic ml> which drop some packets on life time expiry... RW> This is when you stop doing what you're doing and route around the RW> bastards... this cannot be done on the internet by the common folk... only the service providers can adjust their routers to feed around blockages... )\/(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™.