Subj : Old Versus New - Ways To : Richard Webb From : Janis Kracht Date : Mon Jul 14 2008 05:20 pm Hi Richard, >> BS> Every node should be prepared, and able to connect with their >> BS> NC regularly, just as every NC should be able to do the same with >> BS> their RC, that way routing can always default to host-routed. I >> BS> believe this is stated so in pee4. >> WOuld be nice, but in my case, my nc is ion, I'm pots only. >> Then you need to find an intermediary who can handle both, and >> is agreeable to route traffic between you both. OR one of you add a >> second format to allow communication with the other. > Internet isn't practical here at the moment, hence I"m plain ol' modem on a > phone line only. My nc is internet only, no pots, but we've arranged Danny Walters is your NC, correct? He needs to update his nodelist entry if he doesn't have POTS going over there. Maybe Ross has an email address for him and can contact him about that. > intermediaries that work most of the time . We've worked rather well >together on this in fact, so there's no problem there, but as Ross notes, make > it a problem for routing tables. That's good - and you have a connection here as well which is good - my system can do any type of connection necessary. From here, mail is going to flow right to the main Star systems and RCs, most of whom have agreed to take any netmail I get in for their regions. > Still wonder if nodes such as myself and others who are not internet capable > should endeavor to fly the ping flag to help those building routing tables. That's so software specific though. For instance, I don't have a ping feature in any of the software I run. Take care, Janis --- BBBS/LiI v4.01 Flag * Origin: Prism bbs (1:261/38) .