Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2884 comp.os.linux.misc:20502 Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!agate!howland.reston.ans.net!EU.net!sun4nl!cs.vu.nl!philip From: philip@cs.vu.nl (Philip Homburg) Subject: Re: nonsense about broadcast address (was I hope this wont ignite ...) Message-ID: <CtpD2x.DEq@cs.vu.nl> Sender: news@cs.vu.nl Organization: Fac. Wiskunde & Informatica, VU, Amsterdam References: <CtMnq1.C8@rex.uokhsc.edu> <CtnLDs.6zG@cs.vu.nl> <Cto4HC.BoH@calcite.rhyolite.com> Date: Fri, 29 Jul 1994 12:52:08 GMT Lines: 22 In article <Cto4HC.BoH@calcite.rhyolite.com> vjs@calcite.rhyolite.com (Vernon Schryver) writes: %In article <CtnLDs.6zG@cs.vu.nl> philip@cs.vu.nl (Philip Homburg) writes: %> ... %>A well known property of BSD code is of course the use of x.x.x.0 as %>a broadcast address. % %Well known, perhaps, but only to people who think "BSD" is spelled "SunOS". % %It's getting close to 10 years since 4.3BSD has used x.x.x.255 as the %broadcast address. Yes, I know, I should have written "a well known property of at least one wide-spread BSD (derived) TCP/IP implementation is..." The point is that any decent TCP/IP implementation has to deal with this behaviour. Does this also mean that the TCP/IP implementation in SunOS 4.x is not based on BSD in the sense used in this thread? That would be funny. Philip Homburg