TftpServer is a utility which helps you to utilize and configure the TFTP server shipped with the standard Mac OSX distribution.
Using this application you can start/stop the TFTP service on your Mac and change its working path, that's where the files are sent to and received from by any TFTP client (e.g. a Cisco router or switch). In addition, other features are available to help you to seamlessy send and receive files from any TFTP enabled device to a Macintosh acting as TFTP server.
This is useful if you have a lot of network devices and want to store in a safe
What's New
Version 3.4:
Now compatible with Mac OS X 10.6 Snow Leopard.
The TFTP service is now started is secure mode, to chroot to the tftp working folder on startup.
If you have Tiger or Leopard, which started tftpd in insecure mode by default, TftpServer will fix the tftp configuration to start in secure mode.
The TFTP service status reported by TftpServer now effectively checks if the service is running instead of just checking if it was set to start on boot.
Removed the Console Log because it was no longer useful since Mac OS X 10.3 Panther.
There is now a popup menu list all IP addresses configured on your Mac; the IP address is copied on the clipboard when you select it.
Great utility to configure the TFTd server on a Mac. I have been using it for a long time to load/save configuration files for routers, switches, etc...
Highly recommended tool! Without any knowledge about TFTP was the setup of TFTP server a question of 2 minutes!
With this tool I could load firmware image to FortiGate 60 and save my firewall, which was not working (unfinished firmware upgrade through web interface).
Thank you to the developer for this usefull tool!
WARNING! TftpServer 3.2.1 has a serious flaw. If you are trying to use it to upload a Cisco IOS to a Cisco router or switch then DO NOT use this software... it will appear to work and then at the very end of the transfer the Cisco device will report "Timeout. Transfer Cancelled" , then you'll be stuck with no IOS in your device. Although I have not tested the theory I believe this may be caused by the software having a size limit on the file size it will transfer? For reference I have been moving IOS files of about 30MB and 50MB. Both transfers failed.
Otherwise this software seemed to work flawlessly with moving small size files up/down. I moved Cisco config files up and back with no issues.
That's not a TftpServer flaw, neither a flaw of the tftp server shipping with Mac OS X.
As also explained in the TftpServer online help and web site, Cisco devices are not able to use tftp extended mode and this is why they are able to upload/download files larger than 32 Mb only with Cisco TFTP Server for Windows.
- The failure to transfer large files is not a flaw of TftpServer 3.2.1 since that product is merely a GUI shell interface for the unix tftpd utility is is nonetheless an important and limiting issue. So the limitation is with that tftpd utility in Mac OS. I am running OSX 10.5 (have not gotten 10.6 yet so unsure if it may work there). The issue is with any large tftp transfer over 32MB. I have tested this from my Mac to my PC.. so it is not related to Cisco IOS problems.
Cisco IOS did a long time ago suffer from a 16MB maximum tftp transfer limitation. But any IOS equal to or newer then the following has this issue resolved now:
The Cisco IOS Software, or boot mode version, must be a minimum of 12.0(14)S, 12.1(6), 12.0(14)ST, 12.0(14)SC, 12.1(6)E, 12.1(5)DB, 12.1(5)DC, 12.1(5)T4, 12.1(6)EC, 12.1(6)E01, later versions of these trains, or any 12.2 or 12.3 version.
The following article/blog [link below] seems to confirm what I am saying:
On the page you linked you may also a link to this:
[quote]
This is from the tftp man page:
blksize blk-size
Set the tftp blksize option to blk-size octets (8-bit bytes).
Since the number of blocks in a tftp get or put is 65535, the
default block size of 512 bytes only allows a maximum of just
under 32 megabytes to be transferred. The value given for
blk-size must be between 8 and 65464, inclusive. Note that many
servers will not respect this option.
I would assume that most routers, etc. would likely use the default block size. If this is configurable on your router, you might try increasing the size to accommodate.
[/quote]
I have investigated and I can assure you that Cisco devices keep their blocksize fixed to 512 bytes, so the reason why other tftp servers running under Windows or Linux are instead able to transfer files larger than 32 Mb is that they are not RFC-compliant (and this is not necessarily a bad thing, at least in this case) so I guess they reset their block counter when its limit of 65536 is reached.
Thank you for the info FABRO. I have now confirmed that this is NOT a problem with TftpServer 3.2.1 or the Mac implementation of tftpd. Here is what I did.
1. Start up TftpServer 3.2.1 and make sure there is both a small file and a large (over 32MB) file in the path directory.
2. Now, from the command line type: tftp localhost
This is the built in Mac tftp client. The prompt should change to tftp>
3. Type get filename.txt [use whatever filename and extension is applicable to the small file you placed in the TftpServer 3.2.1 directory.
This file should transfer no problem. Success.
4. Now repeat step 3 above, but instead use the large file filename and extension.. after some time this transfer should time-out.
This verifies that a large file will not tyransfer.
5. Now at the command line press the CONTROL key and the Z key simultaneously to exit the built-in tftp client.
6. Type tftp -e localhost
This will open the built-in tftp client on the Mac again. But this time will enable binary mode (the default is ASCII, and also enable support for large files).
7. Repeat step 4 above. This time the large file transfer will succeed.
CONCLUSIONS: To me this verified that any problems with large file transfer are a tftp client software issue/limitation and NOT in any way related to TFTPServer 3.2.1 or the Mac OSX implementation of tftp.
So, I wholeheartedly apologize for my rush to judgement. Many thanks to FABRO for keeping on me and spurring me to do some further testing.
Of course in the final analysis the fact is still that TFTPServer 3.2.1 will not work with Cisco IOS files. This is a Cisco IOS tftp client limitation.
I wish we could find a way around it? Clearly other tftp server implementations have implemented 'tricks' to accommodate the CiscoIOS.
This is a great little utility. Anyone who uses their Mac for Cisco configuration knows how nice this utility made your life with panther. Now It's tiger compatible.
A classic example of making the tools already available in Mac OS X more accessible for users.
Good work.
[Version 3.0.1]
Anonymousreviewed on 10 Dec 2003
Excellent application -- solved all of my issues!
[Version 2.4]
Anonymousreviewed on 07 Nov 2003
Great application. Super simple yet very functional. Just one thing, is there a way that the TFTP server can create a file if it doesn't exists?
[Version 2.2.1]
1 Reply
Anonymouscommented on 18 Jan 2005
No. This is not possible with the tftp protocol.
Anonymousreviewed on 08 Aug 2003
Useful contribution to Macintosh GUI and takes the rocket science out of running a tftp server. IT Director.
[Version 1.6]
There are currently no troubleshooting comments. If you are experiencing a problem with this app, please post a comment.
Please login or create a new MacUpdate Member account to use this feature
Watch Lists are available to MacUpdate Desktop Members Upgrade Now
Download and auto-install
using MacUpdate Desktop. Save
time moving folders and cleaning-up.
TftpServer is a utility which helps you to utilize and configure the TFTP server shipped with the standard Mac OSX distribution.
Using this application you can start/stop the TFTP service on your Mac and change its working path, that's where the files are sent to and received from by any TFTP client (e.g. a Cisco router or switch). In addition, other features are available to help you to seamlessy send and receive files from any TFTP enabled device to a Macintosh acting as TFTP server.
This is useful if you have a lot of network devices and want to store in a safe place all their configuration files and operating system binary images. These files can be reused later (or modified using a text editor on your Mac) to easily configure from scratch other similar devices or update their system image files.
mississippislim reviewed on 11 Nov 2011
Working path permissions:
Fix Needed
I am unsure what to do
If the "fix" button does not work, use "chmod -R 777 /private/tftpboot" as root user in a terminal window
The GUI should now confirm that Attributes are OK
+3
Bottacco reviewed on 15 Aug 2011
-8
Ikir reviewed on 22 Mar 2011
+1
+6
Jr reviewed on 24 Sep 2010
With this tool I could load firmware image to FortiGate 60 and save my firewall, which was not working (unfinished firmware upgrade through web interface).
Thank you to the developer for this usefull tool!
-2
-2
Dwight Hughes reviewed on 03 Sep 2009
Otherwise this software seemed to work flawlessly with moving small size files up/down. I moved Cisco config files up and back with no issues.
+1
As also explained in the TftpServer online help and web site, Cisco devices are not able to use tftp extended mode and this is why they are able to upload/download files larger than 32 Mb only with Cisco TFTP Server for Windows.
-2
Cisco IOS did a long time ago suffer from a 16MB maximum tftp transfer limitation. But any IOS equal to or newer then the following has this issue resolved now:
The Cisco IOS Software, or boot mode version, must be a minimum of 12.0(14)S, 12.1(6), 12.0(14)ST, 12.0(14)SC, 12.1(6)E, 12.1(5)DB, 12.1(5)DC, 12.1(5)T4, 12.1(6)EC, 12.1(6)E01, later versions of these trains, or any 12.2 or 12.3 version.
The following article/blog [link below] seems to confirm what I am saying:
http://www.macosxhints.com/article.php?story=20070218233806794
[quote]
This is from the tftp man page:
blksize blk-size
Set the tftp blksize option to blk-size octets (8-bit bytes).
Since the number of blocks in a tftp get or put is 65535, the
default block size of 512 bytes only allows a maximum of just
under 32 megabytes to be transferred. The value given for
blk-size must be between 8 and 65464, inclusive. Note that many
servers will not respect this option.
I would assume that most routers, etc. would likely use the default block size. If this is configurable on your router, you might try increasing the size to accommodate.
[/quote]
I have investigated and I can assure you that Cisco devices keep their blocksize fixed to 512 bytes, so the reason why other tftp servers running under Windows or Linux are instead able to transfer files larger than 32 Mb is that they are not RFC-compliant (and this is not necessarily a bad thing, at least in this case) so I guess they reset their block counter when its limit of 65536 is reached.
-2
1. Start up TftpServer 3.2.1 and make sure there is both a small file and a large (over 32MB) file in the path directory.
2. Now, from the command line type: tftp localhost
This is the built in Mac tftp client. The prompt should change to tftp>
3. Type get filename.txt [use whatever filename and extension is applicable to the small file you placed in the TftpServer 3.2.1 directory.
This file should transfer no problem. Success.
4. Now repeat step 3 above, but instead use the large file filename and extension.. after some time this transfer should time-out.
This verifies that a large file will not tyransfer.
5. Now at the command line press the CONTROL key and the Z key simultaneously to exit the built-in tftp client.
6. Type tftp -e localhost
This will open the built-in tftp client on the Mac again. But this time will enable binary mode (the default is ASCII, and also enable support for large files).
7. Repeat step 4 above. This time the large file transfer will succeed.
CONCLUSIONS: To me this verified that any problems with large file transfer are a tftp client software issue/limitation and NOT in any way related to TFTPServer 3.2.1 or the Mac OSX implementation of tftp.
So, I wholeheartedly apologize for my rush to judgement. Many thanks to FABRO for keeping on me and spurring me to do some further testing.
Of course in the final analysis the fact is still that TFTPServer 3.2.1 will not work with Cisco IOS files. This is a Cisco IOS tftp client limitation.
I wish we could find a way around it? Clearly other tftp server implementations have implemented 'tricks' to accommodate the CiscoIOS.
Thanks.
+4
lucid reviewed on 19 Mar 2007
Anonymous reviewed on 06 Sep 2005
A classic example of making the tools already available in Mac OS X more accessible for users.
Good work.
Anonymous reviewed on 10 Dec 2003
Anonymous reviewed on 07 Nov 2003
Anonymous reviewed on 08 Aug 2003
+3
Widber rated on 03 Apr 2012
+3
Bottacco rated on 17 Jan 2012
+3
Widber rated on 12 Oct 2011
+3
Widber rated on 07 Aug 2011
Hellsnake rated on 26 Feb 2011