Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!blake!Tomobiki-Cho!mrc
From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin)
Newsgroups: comp.sys.next
Subject: Re: Aaaaarrrrgggghhhhh!!!!!?
Message-ID: <2171@blake.acs.washington.edu>
Date: 25 May 89 22:00:38 GMT
References: <10806@orstcs.CS.ORST.EDU> <1115@garcon.cso.uiuc.edu> <2455@mace.cc.purdue.edu>
Sender: news@blake.acs.washington.edu
Organization: Mendou Zaibatsu, Tomobiki-Cho, Butsumetsu-Shi
Lines: 19

In article <2455@mace.cc.purdue.edu> dls@mace.cc.purdue.edu (David L Stevens) writes:
>	The netmask comes from an ICMP NETMASK broadcast request. It's
>documented in detail in RFCs 950 and 792, available via anonymous FTP from
>sri-nic.arpa, for those interested in details.
>	Any unmodified Berkeley host should answer netmask requests, though
>this is contrary to the RFC; only *gateways* are supposed to. If your NeXT is
>on a network with some such beast, as mine is, the netmask will appear as if
>by magic, and is reported in the boot output.

The problem is that on our 128.208 network, the magic sets the netmask
to 0xffff (not the correct 0xffff0000) and the NeXT subsequently hangs
on booting.

Mark Crispin / 6158 Lariat Loop NE / Bainbridge Island, WA 98110-2020
mrc@CAC.Washington.EDU / MRC@WSMR-SIMTEL20.Army.Mil / (206) 842-2385
Atheist & Proud / 450cc Rebel pilot -- a step up from 250cc's!!!
tabesaserarenakerebanaranakattarashii...kisha no kisha ga kisha de kisha-shita
sumomo mo momo, momo mo momo, momo ni mo iroiro aru
uraniwa ni wa niwa, niwa ni wa niwa niwatori ga iru