Yes, we are talking about different things. I was **not** referring to your post about adding actual path data to the ping/tracert. As for stupid. Its not stupid to want to make the system more efficient, it ***is*** stupid how they, all too often, set up the systems that do that such that no alternate route is allowed, unless some massive delay happens, and *other* systems inform their routers that they can get there some other way. That is the key problem with the system as it stands. I have had 1-2 times where the direct path via Nevada failed, due to flooding, and I couldn't get to some place in California, *but* I could connect via the Pheonix network path to some place that was physically less than 50 miles away from the first one, also in California. That *is* stupid. And, to make it even dumber, nothing in that chain was smart enough to find an alternate path for anything at all that went via Nevada. I find this quite ridiculous. Its like if your own phone stopped being able to call your neighbors phone, due to someone a block away hitting a phone pole, yet, somehow, you could both call in to complain to the phone company about the problem. If you can both hit a central location, from both paths, not being able to get to anything on the other path is... incomprehensible, unless the reason is because someone has been busy hardwiring the pathing information into the system, in such a fashion that no alternates *can* be found. What term would you prefer I use to describe this overzealous optimizing? lol
EDIT- Normal problems resolve, even in bad cases, within minutes, or maybe hours. The case I ran into here lasted for two days. Literally half the country was cut off from me, despite the fact that half the places I *could* get to where in the same states, or even sometimes the same cities, as the ones I *couldn't*. Oh, and in one case, Northern California was lost to me, due to work being done in LA, for 3-4 months. One could get to Oregon, Washington, etc. from both me, and from there, or from those states to N. California, but not from me to there. I.e., a route "existed" which still linked the places I could get to, to the ones I couldn't, but the system was "optimized" in that collection of routers on both paths to *ignore* the solution, since key locations had, "If you are trying to get to IPs X through Y, always take path Q, never Z." |