Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!decvax!bellcore!ulysses!ucbvax!info-vax From: AWalker@RED.RUTGERS.EDU (*Hobbit*) Newsgroups: mod.computers.vax Subject: Another interesting one Message-ID: <12178807774.2.AWALKER@RED.RUTGERS.EDU> Date: Tue, 28-Jan-86 06:09:11 EST Article-I.D.: RED.12178807774.2.AWALKER Posted: Tue Jan 28 06:09:11 1986 Date-Received: Sat, 1-Feb-86 18:18:04 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 14 Approved: info-vax@sri-kl.arpa I have a vax on an ethernet cable with a few other DECNET vaxen on it also. In particular, I'm host 13, the others are 2 [NB] and 10 [CHEMA]. NB routes to a bunch of other hosts via a DMC or something. In farting around with tasks and things, I've run across entries in netserver.log of the type '' connect request received from 1026::"0=USER" which turns out to be host 2. I.e. if I do SET HOST 1026 from my host, I get to host 2. My host is nonrouting, has no knowledge of host 2, 1026, or anything like that in its own tables, so it doesn't know what to call the incoming host. Do host numbers wrap around at 1024, is 2 translating to 1026, and why would my host be adding extra bits to the incoming host number? In other words, what's going on? _H* -------