gparmer/Composite — pull request #30 by rezie2 (2012-09-27 19:28:31+00:00)
Title: Changes as per comments; tunrecv having issues

Currently, both the udp receiver and the tun receiver have their thread priority settings commented out so that your system does not freeze up as a result of the tun receiver's inability to read messages from the client. The udp receiver _should_ be fine, but I've commented it out there as a precaution.

To run this you'll need two terminals, one for the sender, one for the receiver.

For the sender, do:

./udp_client

Do not provide the receiving port paramter

For the receiver, do:

./udp_server1w
or
./tunrecv

If you were to re-enable the thread priority settings, you'll need to start the sender first, otherwise the receivers are going to freeze up the system (assuming you're running both off the same system).

The tun receiver has a pre-defined IP address that I've been using for tests - 196.0.0.15 but feel free to change that. Just make sure that you issue the same IP for the sender as well.

For the udp receiver, make sure the ports are the same. For tests, I've been sending to the loopback address from the sender which the udp receiver can pick up.

To compile either receivers, make sure you include -lpthread and -lm.

That's all I can think of for now, let me know if anything comes up.