The TclUDP package provides Tcl with UDP sockets on Windows and un*x.
The created sockets support the fileevent command and also support multicasting and binary data. The package has recently been restructured as a TEA3 compliant package with build testing done for Linux, Windows, Solaris and OpenBSD.
TclUDP is now a project at sourceforge [L1 ] ("owned" by Xiataow, but maintained by PT) and the latest releases will be available at [L2 ].
With TclUPD, you first create a socket on the local system:
set sock [udp_open]
You can also specify a port number if that is required. You could set the characteristics of the socket with
fconfigure $sock -buffering none -translation binary
You specify the other end-point for the UDP datagram with 'udp_conf':
udp_conf $sock somserv.example.com $watchPort
You can send datagrams (of up to 4096 bytes) with 'puts' and read incoming datagrams with 'gets'.
puts $sock "Pack my box with four dozen liquor jugs."
You can also use 'fileevent' to specify a callback that should be invoked when a UDP datagram arrives:
fileevent $srvsock readable [list ::udpCallback $srvsock]
The following does only indirectly pertain to TclUDP. These are some speculations on what a UDP package for tcl could look like.
ECS on 20041122 - The multicast packets are sent with a TTL of 1, so they don't cross routers. Maybe we should add an option to define the TTL?
PT 22-Nov-2004: Which version are you using and on what operating system? It would be useful to me if you provide a small sample that uses multicast. I don't have something that I know works for testing this. However, what I can do is add a fconfigure option that can call get/setsockopt(s, SOL_IP, IP_TTL, &ttl);
If you raise a bug at [L3 ] you can get notified when it's dealt with.
In fact - I'm just checking this in:
% load libudp1.0.6.so
% set u [udp_open]
sock3
% fconfigure $u -buffering none -blocking 0 -broadcast 1 -remote {172.16.255.255 9876}
% puts -nonewline $u test
% fconfigure $u -ttl 10
% puts -nonewline $u testThe above gives me the following packets using tcpdump:
09:31:39.665765 IP (tos 0x0, ttl 64, id 0, len 32) host.example.com.1140 > 172.16.255.255.9876: [udp sum ok] udp 4 (DF) 09:31:39.665765 IP (tos 0x0, ttl 10, id 0, len 32) host.example.com.1140 > 172.16.255.255.9876: [udp sum ok] udp 4 (DF)
ECS 20041122 - Well, I am using tcl 8.4.7, TclUDP (1.0.5) available on sourceforge, and running on linux (2.4.27-ow1). The problem seems to be related with multicast. Look the code below: [snip] Maybe I just misunderstood the documentation. BTW
PT - No - you haven't misread the docs. I'm working on this NOW so what I'm showing above the the current CVS head version. I've implemented a -ttl. This affects normal UDP. For multicast UDP, it seems we have to use IP_MULTICAST_TTL. So I'm arranging this such that if the socket has multicast groups added, then I'll also set the multicast ttl. You will need to checkout the CVS source to try this -
cvs -d:pserver:[email protected]:/cvsroot/tcludp co tcludp (changed from udp UK)
However, the anonymous access may lag behind ssh access by some time - usually only a few hours I understand.
ECS - Thanks, I will check in a few hours. I did changed udp_tcl.c to set TTL just after join the multicast group. I used 31 (site multicast) but I think it will be better to have the value as an option in udp_conf or fconfigure, as you wish. This way we can limit packet propagation.
PT - It is in now - the revision version for the new version of udp_tcl.c is 1.17. I intend to depreciate [udp_conf] in favour of [fconfigure] but both commands are supported. To set the multicast ttl you should have first set a multicast group.
fconfigure $udpsock -mcastadd 224.5.1.21 -ttl 31
will work. I have also made the channel remember the mcast groups added and it now calls the mcastdrop code for each one still in the list when the channel is closed. This seems like a good idea - but do you agree?
DAS: note that TclUDP is part of my Mac OS X TclTkAquaBI distro already, a small patch [L4 ] is required to build properly on Mac OS X.
Future direction
PT There is some work on a version 2 udp package which will drop the udp_open and udp_conf commands in favour of a single [udp] command for creating the channel instance and then use the [fconfigure] command for everything else. As of udp 1.0.6 the fconfigure functionality is already in place.
The [udp] command will permit specification of the local interface with a -myaddr option and also supports a -reuseaddr flag to set the SO_REUSEADDR socket option so that multiple sockets can bind an address.
I also want to sort out the IPv6 side of things so that the same library can handle both ipv4 and ipv6 connections.
[PT] writes on 11Mar03: The current interface to this package isn't quite what we'd like to see for Tcl. I'm currently implementing the bits required to support the stock fconfigure command. For the future I think that I'd like to see a udp command very much like socket. This could then be used as
set u [udp $remote $port] ; # create a udp socket and set the target set u [udp] ; # create a udp client socket that requires configuring later set u [udp -server handler $port] ; # create a udp server socket listening on $port
UDP sockets are not normally connected to anyone. So fconfigure can be used to redirect outbound traffic. The server handler can use fconfigure $u -peer to obtain information about who sent the current packet. So the same socket could be used to fire off packets to a list of hosts.
proc handler {sock} { do stuff }
set u [udp]
fconfigure $u -buffering none -translation binary
fileevent $u readable [list ::handler $u]
foreach {host port} $targetlist {
fconfigure $u -remote [list $host $port]
puts -nonewline $u $data
}Note that to read data from a udp socket, you will always have to set up a fileevent handler.
Seems reasonable - until aku invents his Tcl Event System :)
[Jacob Levy] writes on March 11, 2003: This all seems very reasonable. Then a small step forward would be to convert it to using the socket command like this:
set u [socket -udp $remote $port] ; # create a udp socket and set the target set u [socket -udp] ; # this one needs to be fconfigured later set u [socket -udp -server handler $port] ; # create a udp server listening on $port
Note that this is backwards compatible with the regular socket command.
Question: in the readable handler, is there any way to find out the name/IP address of who made it readable? Is the read blocking, i.e. will it block if you try to read more than what's there?
[PT] answers: As for the socket command, fconfigure -peername will return the senders details for the current packet. As for blocking - the udp socket cannot be blocking. What happens is that read reads data from a single packet until it's complete. If you try to read too much, an end of data gets returned once the packet is exhausted. So you can safely use set d [read $sock] and be sure to only get the data from one packet. With udp it usually makes sense to have buffering off - so this generally means you read the entire packet.
Pat has written, "Multicast is a little different to standard unicast or broadcast UDP. Your operating system ignores multicast packets unless an application has explicitly joined a multicast group. In the case of TclUDP we do this by using
fconfigure $socket -mcastadd $mcastaddress
This actually results in a system call that causes the system to start listening to packets addresses to this group. In C this would be:
setsockopt(socket, IPPROTO_IP, IP_ADD_MEMBERSHIP, ....);
Once the system is no longer ignoring such packets, normal UDP addressing takes effect. This means that you need to send to this multicast address and in order to receive packets you need to have a listening socket open and bound to the correct address and port.
It is not necessary to join the multicast group to send but it is necessary if you want to receive.
There is a minimal demo called multicast.tcl in the tcludp demos/ folder (as distributed in the source package). If you run that as
tclsh multicast.tcl
it listens to group 224.5.1.21 port 7771. You can send to it using netcat (or the chat.tcl demo) eg:
echo "testing " | nc -u 224.5.1.21 7771
or
wish demos/chat.tcl "
[ Category Package | Category Internet | Category Networking ]