From 67d94514b0d1501832a52fd42db8f5a41151d7f5 Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <daniel@haxx.se>
Date: Thu, 4 Oct 2007 10:01:41 +0000
Subject: Kim Rinnewitz reported that --local-port didn't work with TFTP
 transfers. This happened because the tftp code always uncondionally did a
 bind() without caring if one already had been done and then it failed. I
 wrote a test case (1009) to verify this, but it is a bit error-prone since it
 will have to pick a fixed local port number and since the tests are run on so
 many different hosts in different situations I add it in disabled state.

---
 tests/data/test1009 | 43 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 tests/data/test1009

(limited to 'tests/data/test1009')

diff --git a/tests/data/test1009 b/tests/data/test1009
new file mode 100644
index 000000000..86470ff74
--- /dev/null
+++ b/tests/data/test1009
@@ -0,0 +1,43 @@
+<testcase>
+<info>
+<keywords>
+TFTP
+TFTP RRQ
+</keywords>
+</info>
+
+#
+# Server-side
+<reply>
+<data>
+a chunk of
+data
+returned
+ to client
+</data>
+</reply>
+
+#
+# Client-side
+<client>
+<server>
+tftp
+</server>
+ <name>
+TFTP retrieve
+ </name>
+ <command>
+tftp://%HOSTIP:%TFTPPORT//1009 --local-port 44444
+</command>
+</client>
+
+#
+# Verify pseudo protocol after the test has been "shot"
+<verify>
+<protocol>
+opcode: 1
+filename: /1009
+mode: octet
+</protocol>
+</verify>
+</testcase>
-- 
cgit v1.2.3