Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!mcsun!inria!ircam!mf
From: mf@ircam.ircam.fr (Michel Fingerhut)
Newsgroups: comp.protocols.tcp-ip
Subject: Hosts whose IP numbers end in 0........
Message-ID: <1990Aug25.220042.29632@ircam.ircam.fr>
Date: 25 Aug 90 22:00:42 GMT
Sender: mf@ircam.ircam.fr (Michel Fingerhut)
Organization: IRCAM, Paris (France)
Lines: 15

Our LAN is a class B network, 129.102.0.0, and I had the unfortunate idea to
choose *legal* IP numbers for some of our main hosts of the form 129.102.nn.0,
(nn != 0).  It's legal for a machine, since the HOST part, nn.0, is definitely
NOT zero.

Turns out some major gateways (sorry, no names) filter out such numbers,
thinking these are broadcasts or some such.  Well, they are not.

I can see 3 solutions:

1.  Changing the numbering scheme of our (several dozen) machines.
2.  Changing the RFC describing the internet addressing scheme
3.  Fixing those gateways.

So, what about (3), guys 'n gals, before I suggest (2) is done?