No replies to this topic
#1
Posted 29 July 2012 - 03:42 AM
I am writing a TFTP Client using C++. I was able to send a read request using "octet" mode to a default TFTP Client (tftpd32). The problem is that I am unable to send the ACK back at the regular TFTP respond. I am getting the following error:
Connection received from 127.0.0.1 on port 51401 [27/07 23:03:15.612]
Read request for file <test.txt>. Mode octet [27/07 23:03:15.612]
Using local port 51402 [27/07 23:03:15.612]
Connection received from 127.0.0.1 on port 51401 [27/07 23:03:18.624]
Unexpected request 4 from peer [27/07 23:03:18.624]
Returning EBADOP to Peer [27/07 23:03:18.624]
Why I am able to send the RRQ but not the ACK using the same method?
Also tagged with one or more of these keywords: c++, udp, client
project
Groups →
Project forge →
Cish - A Unix shell and C++ interpreter based on ClingStarted by tinybit , 03 Apr 2018 project, cish, unix, shell, c++ and 5 more... |
|
|
||
Boot methods & tools →
Boot from LAN →
Tftpd32 →
TFTP client : Blocksize no taken in account ?Started by aurelienr , 29 Jun 2017 client, blocksize |
|
|
||
Groups →
Windows Extreme →
Windows PE →
Painting Issue when CFileDialog run WinPEStarted by Arunkumar Uthandan , 27 Oct 2016 mfc, vc++, win32, c++, winpe |
|
|
||
Answered
Groups →
Project forge →
ImDisk →
Unable to create device from C++Started by jazzycamel , 17 Feb 2015 c++ |
|
|
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users