curl/tests/data/test1009

<testcase>
<info>
<keywords>
TFTP
TFTP RRQ
--local-port
</keywords>
</info>

#
# Server-side
<reply>
<data>
a chunk of
data
returned
 to client
</data>
</reply>

#
# Client-side
<client>
<server>
tftp
</server>
 <name>
TFTP retrieve with --local-port
 </name>
 <command>
tftp://%HOSTIP:%TFTPPORT//1009 --local-port 44444-45444
</command>
</client>

#
# Verify pseudo protocol after the test has been "shot"
<verify>
<protocol>
opcode: 1
filename: /1009
mode: octet
</protocol>
</verify>
</testcase>
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. 2007-10-04 06:01:41 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`TFTP`
			`TFTP RRQ`
I enabled test 1009 and made the --local-port use a wide range to reduce the risk of failures. 2007-10-04 17:26:26 -04:00			`--local-port`
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. 2007-10-04 06:01:41 -04:00			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`a chunk of`
			`data`
			`returned`
			`to client`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`tftp`
			`</server>`
			`<name>`
I enabled test 1009 and made the --local-port use a wide range to reduce the risk of failures. 2007-10-04 17:26:26 -04:00			`TFTP retrieve with --local-port`
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. 2007-10-04 06:01:41 -04:00			`</name>`
			`<command>`
I enabled test 1009 and made the --local-port use a wide range to reduce the risk of failures. 2007-10-04 17:26:26 -04:00			`tftp://%HOSTIP:%TFTPPORT//1009 --local-port 44444-45444`
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. 2007-10-04 06:01:41 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify pseudo protocol after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`opcode: 1`
			`filename: /1009`
			`mode: octet`
			`</protocol>`
			`</verify>`
			`</testcase>`