JDBP> RB>      /* Bind the UDP socket to the server address. */
JDBP> RB>      client.sin_family      = AF_INET;    /* Server is
JDBP> RB> in Internet Domain */
JDBP> RB>      client.sin_port        = 0;          /* Any port in a storm */
JDBP> RB>      client.sin_addr.s_addr = INADDR_ANY; /* Server's
JDBP> RB> Internet Address    */
JDBP> RB>      if (bind(s, (struct sockaddr *)&client, sizeof(client)) < 0) {
JDBP> RB>          return(-1);
JDBP> RB>      }

JDBP>What that is actually doing is binding an address to the *local* end of
th
JDBP>socket, not the remote end.  Your comments are wrong.

You're right, the comments were lifted verbatim from one of the toolkit
example files.

JDBP>Given the address that you are binding to the client end, I
JDBP>have to ask:  Is it the *server* end that is receiving the
JDBP>"no route to host" errors ?

I'm sending out a broadcast and then waiting for a response on the same
socket.  It is the broadcast call that is failing with the No route to
host error.  If I specify an address for the call to the server rather
than using a broadcast, it works as expected.

I find it most odd that it works in Warp 4 but not in WSeB.  You'd think
that they would have tested broadcast calls in the 4.1 TCP/IP stack.

Rob.
___
 X SLMR 2.1a X This tagline is umop apisdn

--- Maximus/2 3.01