Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Michael Khaw)
Newsgroups: comp.unix.wizards,comp.bugs.4bsd
Subject: Re: Serious problem in SunOS 3.3 subnetting w/r/t booting Sun-2 clients
Message-ID: <10950@teknowledge-vaxc.ARPA>
Date: Thu, 19-Mar-87 13:52:53 EST
Article-I.D.: teknowle.10950
Posted: Thu Mar 19 13:52:53 1987
Date-Received: Sat, 21-Mar-87 04:54:56 EST
References: <975@smeagol.JPL.NASA.GOV>
Reply-To: mkhaw@teknowledge-vaxc.UUCP (Michael Khaw)
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 25
Keywords: ip_icmp.o	subnet mask
Xref: mnetor comp.unix.wizards:1532 comp.bugs.4bsd:237

In article <975@smeagol.JPL.NASA.GOV> earle@smeagol.JPL.NASA.GOV (Greg Earle) writes:
>I have just installed SunOS 3.3 (with subnetting support) on a net of
>Sun-2's and Sun-3's; some diskless, most diskful.  I have encountered
>a serious problem ...
>
>I am on a Class B network, 128.149.0.0, on subnet 10, with host numbers 1-XX.
>My main gateway, smeagol, is at 128.149.10.1.  Because of this setup, I
[ continues with describing problems booting diskless sun-2's from a sun-3
server ]

Since I've been unable to reach smeagol.jpl.nasa.gov via internet
mail, I'm posting my request here:

My site has a similar setup:  mostly sun-3s, plus one diskless sun-2/50.
We are currently at OS 3.2 but will upgrade to 3.4 when it comes out (RSN).
Since we also have a class B internet, I suspect we will face the same
problem and are interested in solutions.

Thanks,
Mike Khaw
-- 
internet:	mkhaw@teknowledge-vaxc.arpa
usenet:		{hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
voice:		415/424-0500
USnail:		Teknowledge, Inc., 1850 Embarcadero Rd., POB 10119, Palo Alto, CA 94303