Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!mips!wyse!vsi1!ames!dftsrv!chris From: chris@asylum.gsfc.nasa.gov (Chris Shenton) Newsgroups: comp.sys.apollo Subject: Re: TCP routing from ring through node to ether on SR10.2? Message-ID: Date: 4 Sep 90 15:47:58 GMT References: Sender: news@dftsrv.gsfc.nasa.gov Organization: NASA Goddard Space Flight Center; Greenbelt, MD Lines: 20 In-reply-to: chris@asylum.gsfc.nasa.gov's message of 30 Aug 90 21:06:05 GMT Thanks to all who answered my questions about TCP routing from ring to ether. The solution appears to be to set the net mask the same (255.255.255.0) on all ring and ether interfaces, on all nodes. Here's the kick in the groin, though: GSFC has a boatload of nodes, and the overlords have decided (for backward compatibility reasons, I suppose) that everyone on the ether must use 255.255.0.0 netmask, which basically says ``No netmasks''. Can anyone think of a workaround? Is there any good reason why I can't use that 2-byte mask on all my hardware? or will the gate get confused thinking that my gate addresses (128.183.10.155 and 128.183.30.1) are on the *same* network? Thanks in advance, again :-) -- ____________________________________________________________________________ INET: chris@asylum.gsfc.nasa.gov (128.183.10.155) NASA/GSFC: Code 735 UUCP: ...!uunet!asylum.gsfc.nasa.gov!chris Greenbelt, MD 20771 SPAN: PITCH::CHRIS Fax: 301-286-9214 Phone: 301-286-6093