Several of you asked me about EARNET routing problems and the strange node INTNET. What happened is that node EARNET is being moved to another computing centre in Pisa, that is, the "old" EARNET computer remains active but will be renamed to IEARN while the "new" computer in Pisa will be called EARNET (or maybe it's the opposite, I'm not too sure). Anyway there are at present TWO nodes named EARNET on the network: the old one and the new one. Since a node cannot talk to itself, the EARNET people had to define a dummy node called INTNET (using a virtual CTCA connection), which is itself connected to another node named IEARN (another CTCA connection), which eventually connects to the other EARNET. This is a mess but it works. Important note: when you have received the new nodes table for this month, please do NOT run NODESGEN without first receiving the updated LINKSWT FILE I will send you as soon as I get the new nodes tables myself. Since the setup will have been drastically altered, with IEARN no longer being a synonym for EARNET, the nodes table generation program would give a (nonfatal) error and would most probably result in unweighted nodes table in LISTSERV. This would not cause it to crash but subscriptions would not be routed where they ought to, etc... :-( Eric