22 Mar 12 13:27, mark lewis wrote to Roy Witt:


 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.

 ml> yes, we do see that data is missing and from what IP... "should" is
 ml> subjective, though, because it is not required to reply to those
 ml> protocol requests ;)

True, but having an alternative path to follow, it can be routed around.

 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...

 ml> this cannot be done on the internet by the common folk... only the
 ml> service providers can adjust their routers to feed around
 ml> blockages...

This is where tracert and ftn work hand in hand. Roger told me that he had
no problem with an internet connection with the RC...I routed what I
needed to through Roger and it got to it's destination, in spite of the
internet dead spot in Tennesee...


                R\%/itt


  ... Only those who will risk going too far can possibly
  ... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10