Connect() problem-broadcast socket -w- tcludp,tcl 8.3, FreeBSD 4.9

From: haunted (macdaddep_at_gmail.com)
Date: 01/23/05 

Date: 22 Jan 2005 20:56:09 -0800

Hi All.

Have an issue with connect() not doing the right thing
in the subject'd env.
In short have a script that daemonizes, opens tcp and udp server
sockets, does some initialization and reacts via fileevent readable.

The fconfigured udp socket is set for broadcast and does receive
udp bcast packets. However sending bcast pkts fails in
connect()(probably)
with variations on: Original error: sock5: socket is not connected.
It would seem to me that the broadcast flag should call code smart
enough to save the original setting, recall connect() for the new
connection, handle business, and then reset.

Is this a known issue or is there a workaround? The client is already
coded in C but since the server interaction involves either heavy pty
work in C :/, or expect :), I chose tcl....
Ideas or pointers are appreciated.

Relevant Pages

  • Re: Internet connection through PC
    ... You can craft your code to force your UDP traffic through a connection other ... You need to bind your socket to the IP of your GPRS adapter. ... > while keeping the eVC4 debug capability alive. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: How to uniquely identify a UDP session at Winsock layer?
    ... For UDP, once a send is done, the socket will be auto-bound if it has not ... > Theoretically, I guess, a connection or session in uniquely identified ... > by "Source IP, Source port, Destination IP, Destination port". ...
    (microsoft.public.pocketpc.developer.networking)
  • Re: checking connection to server:port [socket]
    ... I need to check connection to server ... i think you just want to check a udp connection to a udp server. ... not a UDP socket connect. ...
    (comp.lang.ruby)
  • Socket error 10052 on UDP socket
    ... We have a .NET 2.0 desktop application which sends and receives network packets over UDP. ... Several users have reported an occasional socket error 10052 which happens when the code calls socket.BeginReceiveFrom on a the UDP socket. ... The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. ...
    (microsoft.public.dotnet.general)
  • Re: SetSockOpt with SO_REUSEADDR parameter
    ... So I create multiple UDP sockets with the same port to send data. ... happening is that you are throwing away the old socket and replacing it with the new ... When the second client is connecting to server, I still get the error code ...
    (microsoft.public.vc.mfc)