Below is the content of the windows help file packaged with the software, so that you can read it before you download the software. Not sure if you want to, but you can. Once the application is installed, this information can be accessed via built-in help function.
PumpKIN is a program designed to send and receive files over the net while having T42 or Wintalk session running using TFTP (RFC1350) protocol. It includes full-functional TFTP server/client so it may be useful for maintaining CISCO routers and other network equipment.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
2.7.3 - Apr 27th, 2011
- Added configuration option to bind to specific ip address
- Fixed a minor bug that lead to misdiagnosis of the packet from unexpected source
2.7.2 - October 18th, 2006
- Added rejecting of too large file requests with explicit error message about the block size
- A bit more elaborate logging
- Not closing receive socket until the last ACK receved now
2.7.1 - March 13th, 2006
- Bugfix release
2.7 - February 28th, 2006
- Access lists based on request IP address and TFTP opcode for automating access policy
- Possibility to start/stop TFTP server, while keeping client functionality intact
- Logging to file
- Resizable main window
2.6 - August 6th, 2005
- more robust solution to the backslash/slash dilemma
- A bit more elaborate error reporting
- Fixed uninstall procedure so that it works on XP
2.5 - July 11th, 2004
- Change of license and opening the source.
- Minor cosmetic changes
2.0 - June 13th, 1998
- Sounds customization. Now you can customize PumpKIN bells and whistles or turn them off completely.
- Previous version of PumpKIN had a bug causing it to misbehave when you're requesting file from remote tftp server using IP Address (as opposed to hostname).
- Typo causing PumpKIN to log outgoing request in reverse (i.e. Requesting 'hostname' from 'filename') fixed.
- Something else that you may not notice and I can not remember.
1.5 - February 12th, 1998
- Transfer resumes. No checking on file contents is done, so it's up to you to decide whether you want to start transmission from the beginning or resume unfinished transfer.
- Support for block size, trasnfer size and transfer timeout options as described in RFC1782, RFC1783 and RFC1784. I'm not sure if there are any other TFTP implementations supporting this, but at least it makes sense if you use PumpKIN on both ends.
- New Install program
This is a simple program for file exchange between two parties. It allows you to send files over the network to your party while having a T42 or Wintalk conversation. It uses open sessions to determine IP address of your party. Also you may use it as a TFTP client/server by itself. To get/put files from/to TFTP server you need to enter host name/IP address manually in the Request Dialog.
To Abort transfer(s) currently in progress - select transfer(s) you want to terminate in the list and click Abort xfer button.
You may want to hide PumpKIN window and leave it as a tray icon only. Just click the icon in the tray or simply close the window.
Use Options button to set PumpKIN options.
You can start and stop PumpKIN's TFTP server by checking and unchecking the Server is running checkbox in the lower right corner of main PumpKIN window.
Confirm Read Request Dialog
When the file is requested from your TFTP server you may choose to Grant Access to this file or to Deny Access. If you hesitate to answer for Confirmation timeout (default - 30 seconds) PumpKIN defaults to denial of all requests.
Confirm Write Request Dialog
Whenever your party sends you a file you have always a choice to accept it or not. You can also save the file under a different name by choosing the Rename option. If you already have file with such name you may chose to resume transfer. No checking on file contents is done. This option may or may not work depending on remote implementation of protocol. It does work if you use PumpKIN on both ends. If you are still unsure for Confirmation timeout (default - 30 seconds) PumpKIN will make safe decision for you (deny).
Request dialog is aimed to let you form read or write request. You may set the following options:
- Local File - You can change the name of the file you're sending (or destination in case you're receiving) right here. You may also use Browse button to select the file.
- Remote File Specifies the name of file on the remote host you're requesting (in case of read request) or the name of file you want your file to appear as (in case of write request).
- Remote Host is your party's host or TFTP server you're requesting file from/sending file to. To refresh the list of your talk windows use REFRESH button.
- Type is the type of transfer as defined in RFC1350. Doesn't mean much, really. Defined types are 'octet' or 'netascii'. Default is 'octet'.
- Block Size - Use this block size if remote is RFC1783-compliant. If remote doesn't support this option PumpKIN will fallback to 512 bytes per block.
- UDP Ports
- Listen for incoming connections on port - specifies the port we're listening to. The default as defined in RFC1350 is 69.
- ip address - ip address to listen to.
- Send outgoing requests to port - specifies the port we're going to send all requests to.
- Default Connection timeout - if there's no activity for specified time, transfer is considered to be dead and terminated. PumpKIN tries to propagate this value to remote as described in RFC1782 and RFC1784 if possible.
- Default Block Size - PumpKIN tries to negotiate block size with remote using this value unless specified explicitly in request. If remote doesn't support RFC1782 and RFC1783 PumpKIN falls back to 512 bytes per block.
- TFTP Filesystem root - Specifies the location of files you're transmitting or where to start looking for them from. Defaults to the directory you start PumpKIN for the first time from.
- Allow access to subdirectories - specifies whether you want allow access to the whole subtree of TFTP Root or only to the directory itself.
- Read Request Behavior - You may choose to automatically agree to give all files requested, to be prompted to confirm these operations, or to deny all requests as if you're not even here.
- Write Request Behavior - You may chose to take all files (not recommended), to prompt only if file exists already, Always prompt or Deny all requests.
- Confirmation timeout - this is the time PumpKIN will wait for you to accept or deny request before it will give up and take default action which is always deny.
- Log file - If you want to enable logging to file, set the destination file here.
You can customize PumpKIN sounds notifications here. There are three customizable sounds defined - Incoming request, which notifies you about incoming request prompt if you're set to be prompted whenever incoming request occurs. xfer Aborted - which happens to sound every time transfer is interrupted for whatever reason - time out, explicit kill, denied access, etc. xfer Finished means that your file was successfully transmitted.
You can select any .wav file or one of the predefined sounds from the dropdown list.
You can slightly automate your access policies by setting up read/write request behavior for different incoming requests.
The rule consists of request type, source network (ip and netmask) and action to take (see also Server Options).
When PumpKIN receives request it goes through the list of rules and bases its decision on the first matching rule. To rearrange order of rules, select the rule you wish to move and use up and down arrows buttons on the right. To remove rule, use the cross button.
To add a new rule fill in the information about request type, source address and netmask and desired action. Then click on the 'Add new rule' button.
If you wish to amend the rule, select it in the rules list, change parameters below and click the 'Replace rule' button.
- Our free softwareKIN
- tinimalistic template preprocessorcliche
- Eye-Fi card manageriii
- Sleeptracker® PRO softwarenapkin
- flickr manager firefox extensionfireflix
- midi manipulation c++ library and toolsmidillo
- c++ OpenID support librarylibopkele
- convenience librarykonforka
- process monitoring daemondudki
- c++ web development enginesitecing
- c++ CGI support librarykingate
- ntalk client and daemonT42
- syslog serverklog
- console mode telnet clientkinsole
- TFTP server and clientpumpkin
- simple network monitoring toolbigbrother
- download mirrors evaluatordipstick