Xref: utzoo comp.unix.wizards:11147 comp.unix.questions:9221 comp.protocols.tcp-ip:4624
Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!tut.cis.ohio-state.edu!cwjcc!cwsys3.cwru.Edu!ferencz
From: ferencz@cwsys3.cwru.Edu (Don Ferencz)
Newsgroups: comp.unix.wizards,comp.unix.questions,comp.protocols.tcp-ip
Subject: TCP/IP Broadcast Address & Wollongong WIN3B
Message-ID: <54@cwjcc.CWRU.Edu>
Date: 15 Sep 88 18:39:09 GMT
Sender: news@cwjcc.CWRU.Edu
Reply-To: ferencz@cwsys3.cwru.Edu (Don Ferencz)
Organization: CWRU Dept of Systems Engineering
Lines: 21


Hello again.

A short while back I posted a question pertaining to the "broadcast
address" of my particular TCP/IP version - Wollongong's Enhanced
WIN3B running on three AT&T 3B2/310's.  I asked if anyone knew why all of
my attempts to change the broadcast address from a sockets application
(with the SIOCIFGBRDADDR ioctl) were failing with EINVAL.  Well, many
people pointed out what should have been painfully obvious: that
version of TCP/IP is based on BSD4.2 Sockets, which does not support
a change of broadcast address!  However, the #define for
SIOCIFGBRDADDR appears in the header file <ioctl.h>!!!  My thanks
to all who responded, and my condolances to those who had wished to
do the same thing I did.

===========================================================================
| Don Ferencz                       |  "All the world's indeed a stage\   |
| ferencz@cwsys3.cwru.EDU           |   And we are merely players\        |
| Dept of Systems Engineering       |   Performers and portrayers"        |
| Case Wetsren Reserve University   |     -- Rush                         |
===========================================================================