Why another TFTP Server? Doesn't 3Com already supply one?

In the beginning, there was 3CTftpd, which was a small TFTP Server program I wrote so that 3Com customers could upgrade their 3Com equipment.

3CTftpd begat 3CServer, which was a more full-featured TFTP and FTP server I wrote. This eventually became part of 3Com's Transcend Network Management product.

However, it soon became apparent that our customers were using 3CServer for a lot of other things, in addition to upgrading their 3Com boxes. I was getting a number of enhancement requests. In order to accommodate these requests, I took another look at the code, and tried to implement as many as I could.

There was a problem, though. 3CServer was now part of a different product. I spoke with our Network Management folks, and we agreed that we didn't want the two programs getting in each other's way. Therefore, I decided to rename my newest incarnation to 3CDaemon.

I'm confused! Which one should I use?

It's really a matter of personal choice. If 3CServer fulfills your needs, then by all means, continue using it. If you want or need some of the extra functionality provided by 3CDaemon, then use it instead. Either one will work for upgrading 3Com products, since they are adapted from the same code base. Since both are freeware, I don't make a penny off of them either way :)

So, what's new in this 3CDaemon thing?

• New interface. Lot more extensible, so that I can add sub-programs more easily.

• TFTP Server:
• Support for RFC 1782, 1783 and 1784. Block size, timeout and transfer-size negotiation.
• Faster. See speed comparison chart below.
• Prints IP address(es) on which it is listening.

• FTP Server:
• Supports PASSIVE transfer.
• Supports Netscape/IE4 browsing
• Supports 32 char passwords.
• Passwords are MD5 hashed. This should provide adequate password security, yet at the same time still be exportable.
• Prints IP address(es) on which it is listening.

• Syslog Server:
• Added Syslog functionality.
• Logs all syslog messages received.
• Allows filtering/restriction of syslog messages by IP Address.
• Allows logging into via message priority, message facility or IP address.
• Allows viewing of the log files while active, plus copy to clipboard or print
• Produces standard ASCII text files, suitable for including in emails or faxing.
• Prints IP address(es) on which it is listening.

• TFTP Client:
• Support for RFC 1782, 1783 and 1784. Block size, timeout and transfer-size negotiation.
• Stores addresses of frequently accessed hosts
• Supports multiple file transfer, or directory transfer

• Lots and lots of other little fixes and enhancements. Play with it. I'll be adding more as time goes by.

Totally Unscientific Speed comparison:

(i.e. These are numbers I got transferring the same file between two PCs on the same hub. Your mileage will vary...)