Subj : ERRORS in Route List!
To   : Ross Cassell
From : Carl Austin Bennett
Date : Mon May 07 2001 12:52 pm

 RC> Now tell me what a echo hijacker like yourself has to do with a route 
 RC> list, you a big time router or have you lost confidence that your 
 RC> uplink wont be able to find you?

As a moderator, wouldn't Bobby require access to reliable routed netmail to all 
of the millions of sysops and echo participants who carry his many echos?

No point in his telling people to "take it to netmail" if netmail isn't there.

His point of view (as moderator) will differ from mine (as a *c) but he does 
need the netmail routing to work in order to fulfill his task in this network.

 RC> Do you have a clue on how routing works Bobby, I dont think you do, you 
 RC> want folk to route down to the node level, route files are monstrous 
 RC> enough as it is, you want to make them even more complicated?

In some cases, the independent feed is the only one still up. 

NC's have been known to disappear without warning; that at least two NC's in 
Region 14 alone answer voice as wrong numbers, two more are numbers that are 
out of service and a few others just don't answer at all isn't news to anyone.

I've seen a couple disappear and re-appear in-region, for that matter.

A large part of the reason for using RVIA to flag independent feeds is as an 
informational tool for use in finding links to bypass any *C's who go AWOL.

Would be great if they weren't necessary, but if that one independent link is 
overlooked, it is possible to conclude (incorrectly) that the whole net's gone

 RC> Why in the hell are you using echomail conference tag names as source 
 RC> data? Thats a mighty big assumption there fella

Why do the other lists use data as old as 1999, much of it routing through 
nodes that don't exist any more? An echo path might be the only valid data.

It would be preferable that NC's and NEC's tag their routes so that current, 
reliable data would always be available without any reverse engineering.

It would also be nice to have peace on earth and an end to all world hunger.

Given the amount of baloney being distributed as routing data, likely the end 
to world hunger will be found first.

 RC> What you gonna do Bobby, if ERN routing info is inaccurate, blame it 
 RC> on HOLYSMOKE or FN_SYSOP???????

I'd put more faith in HOLYSMOKE than in the most recent ROUTELST.R14 (1999) and 
there are other regions that are lagging close to half a year behind too.

 RC> I dont even need to go into the NET section, what I showed you above 
 RC> is a comedy of errors, but I do note that NET 105's source data is 
 RC> EVOLUTION.

If you have creationist leanings, you could always rely on HOLYSMOKE instead.

 RC>  N  18 1:365/ALL  1:365/1                    1:18/500   2001O502 FLAME 
 RC> While the above info is correct, he was pulling a few echoes from me 
 RC> and most of his echo in addition to his ERN from 18/500, the above 
 RC> info is pretty recent, I dont see how FLAME could have given you 
 RC> substantial and reliable info.

It's correct and pretty recent? 

Nah, can't have that now. There are traditions to uphold here.

Let recent and correct info sneak in to the routing and those nodes might 
actually be able to get netmail from Bobby the moderator Queen. Oh no!

 RC> Before you go parading around to Foxy to show her what you found, 
 RC> look what I found. I bet a dollar to a doughnut that even Dale Ross 
 RC> finds this monstrosity filled with bloat and unreliable as well as 
 RC> inaccurate source data. He should have proofread it before he hatched 
 RC> it for you.

 RC> Tell me Bobby, do you route down to the node level, I bet you route 
 RC> something like this:

 RC> The world --> 379/1 excepting direct linkages you might have

That passes the buck to Dale; it doesn't provide a solution to the whole "no 
route found" mess. 

Mail could be being defaulted to RC's for nodes which don't even exist.

How bad have things become? If you want to send a message to 1:293/643, and he 
is in the nodelist, don't even bother using a computer. Just dial voice. John 
will answer and explain that he hasn't run a BBS in several years now.

If the nodelist and routelist are in this bad shape, the reverse-engineered 
path info could well be a last resort in trying to determine who's connected.

I don't like it, but it's time to stop pretending that replacing "no route 
found" with the default route is going to get the mail to its destination.

--- Msged/LNX TE 06
 * Origin: Pause-Caf‚ Kingston 613-549-5599 telnet:cafe.dyndns.org (1:249/116)

.