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!BRILLIG.UMD.EDU!chris
From: chris@BRILLIG.UMD.EDU (Chris Torek)
Newsgroups: mod.protocols.tcp-ip
Subject: 4.3(beta) subnets & routed
Message-ID: <8605220813.AA13263@brillig.umd.edu>
Date: Thu, 22-May-86 04:13:43 EDT
Article-I.D.: brillig.8605220813.AA13263
Posted: Thu May 22 04:13:43 1986
Date-Received: Fri, 23-May-86 02:45:17 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa

This is perhaps obvious in retrospect, but it is a bad idea to run
routed between two machines with different subnet masks.  Boy do
they get confused.  Sorry about all those UMDNET packets that sprayed
out into the MILNET (though that may have been due to an unrelated
mistake).  (We just turned on subnets, and I did it in phases.  That
was a mistake.  Do it all at once!)

Other than that, hey!, it works very well indeed.  You will need
to use `route -n add <subnet> <gateway> <metric>' (note the `-n')
if your subnet gateways do not run routed.  I am not sure what
happens if they do:  ours are not under my control (for which many
are no doubt grateful :-) ).

Chris