I enabled test 1009 and made the --local-port use a wide range to reduce the
risk of failures.
This commit is contained in:
parent
67d94514b0
commit
6dd6b4d1fa
3
CHANGES
3
CHANGES
@ -7,6 +7,9 @@
|
||||
Changelog
|
||||
|
||||
Daniel S (4 October 2007)
|
||||
- I enabled test 1009 and made the --local-port use a wide range to reduce the
|
||||
risk of failures.
|
||||
|
||||
- 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
|
||||
|
@ -3,4 +3,4 @@
|
||||
# test cases are run by runtests.pl. Just add the plain test case numbers, one
|
||||
# per line.
|
||||
# Lines starting with '#' letters are treated as comments.
|
||||
1009
|
||||
#1009
|
||||
|
@ -3,6 +3,7 @@
|
||||
<keywords>
|
||||
TFTP
|
||||
TFTP RRQ
|
||||
--local-port
|
||||
</keywords>
|
||||
</info>
|
||||
|
||||
@ -24,10 +25,10 @@ returned
|
||||
tftp
|
||||
</server>
|
||||
<name>
|
||||
TFTP retrieve
|
||||
TFTP retrieve with --local-port
|
||||
</name>
|
||||
<command>
|
||||
tftp://%HOSTIP:%TFTPPORT//1009 --local-port 44444
|
||||
tftp://%HOSTIP:%TFTPPORT//1009 --local-port 44444-45444
|
||||
</command>
|
||||
</client>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user