Udpsever exits when the tcp connection dead on the server side

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. start the sever on remotehost "./udptunnel -s 5050 -vv
2. start squid sever on the remote-host which would list on localhost:3128
3. start the client ./udptunnel -c 4455 remote-host 5050 localhost 3128
4. Now setup a http proxy on the browser as localhost:4455
5. Try to browse. It should fetch the webpage.
6. Stop squid server
7. Try to browse.

Now the sever sends the following output few lines and exits.
       recv: Transport endpoint is not connected

What is the expected output? What do you see instead?
      There server not should NOT exit when the tcp endpoint is closed.

What version of the product are you using? On what operating system?
        udptunnel-r13 on Linux - 2.6.33.3-85.fc13.i686.PAE

Please provide any additional information below.

Original issue reported on code.google.com by logsna...@gmail.com on 28 Sep 2010 at 10:31

GoogleCodeExporter commented 8 years ago

Thanks for finding this bug. It is fixed in Revision #14.

Original comment by dmeek...@gmail.com on 7 Nov 2010 at 12:08

GoogleCodeExporter commented 8 years ago

Closing issue (didn't know how to change the 'status' before).

Original comment by dmeek...@gmail.com on 12 Mar 2011 at 6:30

Changed state: Fixed

hellvesper / udptunnel

Udpsever exits when the tcp connection dead on the server side #5