Xref: utzoo comp.mail.uucp:5045 comp.mail.misc:3882 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!usc!snorkelwacker!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.mail.uucp,comp.mail.misc Subject: Re: Pathalias data for a private _UUCP_ network. Message-ID: Date: 20 Aug 90 19:38:18 GMT References: <1990Aug18.005655.5102@fts1.uucp> Organization: University of Karlsruhe, FRG Lines: 61 In comp.mail.misc, article <1990Aug18.005655.5102@fts1.uucp>, michael@fts1.uucp (Michael Richardson) writes: < < A number of Unix people in the Ottawa area, members of a local < user's group are going to be registering a domain: ocug.on.ca < (Ottawa Carleton Unix Group) under which we will be a number < of our sites: mostly single user sites which would otherwise wind < up in .UUCP. < < ocug-net = { amiga.ocug.on.ca, < alzabo.ocug.on.ca } < < julie .ocug.on.ca(LOCAL) < fts1 ocug-net < alzabo ocug-net < [ various problems deleted ] Our solution is to have entries like host1 .some.domain host1 = one.some.domain # host2 .some.domain(DAILY/3) host2 = two.some.domain # host3 .some.domain(DAILY*2) host3 = three.some.domain for all hosts with external connections and which want to carry traffic into the domain. The cost on these entries approximates general connectivity of that host into the domain. Since Pathalias won't generate routes with names in them which start with a dot, this works nicely. If you want to allow paths through your domain (somewhere!host1!host3!xyzzy! !user), you'll still have to include links from host1 to host3. It isn't a problem if the internal version of these connections isn't direct, as long as the link cost advertised to the outside world is greater than the internal cost of that link. If not, you may run into problems with rerouters. < Has anyone else come across such a problem before? Yes. After playing around with Pathalias network notation and stuff, I decided to drop it. All it says is "All the hosts in there can be reached via this host", while requiring you to explicitly mention the machines which are reachable through these secondary links. Domains are supposed not to require outside knowledge of the hosts in the domain, so... Your internal map will probably not have to be changed except for equipping every entry with its domain alias: host99 = someone.some.domain < Are there any good solutions? Bad solutions? NB: Requiring that everyone with more than one link use a smart mailer, has proven either to be a good solution in itself, or to prevent some problems from happening which are discussed here every two months anyway. ;-) -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)