Example TFTP server file configuration
This article is specific to the 32-bit TFTP server provided with Entuity when installed to Windows environments. In Solaris and Linux environments, please consult with your system adminstrator.
Entuity includes the following to entuity_home\integ\TFTPServer:
- license file.
- tftpserver.ini - this is an example initialization file.
- TFTPServerMTInstallerv1.61.exe - this is the TFTP server installer executable.
When you run the installer, you can configure to where the TFTP server is installed, but the default location is: c:\Program Files (x86) \TFTPServer. The following files are installed by the installer:
- ReadMeMT.txt
- RunStandAloneMT.bat
- TFTPServerMT.exe
- TFTPServerMT.ini
- TFTPServerMT.log
- TFTPServerMTInstallService.exe
- TFTPServerMTRemoveService.exe
The TFTServerMT.exe and TFTPServerMT.ini files must remain in the same folder. You should amend the .ini file to specify a home directory that is the same as that specified during Entuity configure, and to permit TFTP server write and overwrite operations.
There are other configuration options available that you can use to amend TFTP server performance. You should always consult the TFTP server documentation.
Example TFTP server file configuration:
TFTP server can be configured through TFTPServerMT.ini, and is only required when not accepting the default TFTP server behavior. TFTPServerMT.ini must be in the same folder as the TFTP server executable, TFTPServerMT.exe.
This example provides a simple TFTPServerMT.ini:
[LISTEN-ON]
[HOME]
c:\Entuity\cm_transfer\
[LOGGING]
Errors
[ALLOWED-CLIENTS]
10.44.1.0-10.44.1.11
10.44.1.13-10.44.1.255
[TFTP-OPTIONS]
where
- LISTEN-ON section, is used when you have more than one NIC card on your server and/or want to the card/interface used to listen for TFTP requests. The default listening port is 69. TFTP server can support up to 8 interfaces. The default is all interfaces, and this example specifies interface 49:
69.254.185.131:49
- HOME section must be specified and is also specified during Entuity configure. Entuity recommend an explicit definition of drive and folder name, e.g.:
c:\Entuity\cm_transfer\
- LOGGING, determines level of logging, e.g. None, All, Errors (default). All is resource intensive and not recommended. TFTPServer.log is created in the same directory as the TFTP executable. Logging only runs when TFTP server is run as a Windows Service.
- ALLOWED-CLIENTS section specifies permitted clients for TFTP Access. By default, all clients are permitted. Through IP ranges you can control allowed clients, this range effectively disallows 10.44.1.12:
10.44.1.0-10.44.1.11
10.44.1.13-10.44.1.255 - [TFTP-OPTIONS] section through which you can further configure the TFTP server behavior:
- port-range, port range on which TFTP server would respond from (default is any free port). When operating with a firewall you may like to restrict this to a suitable range, e.g.:
port-range=30000-30100
- ThreadPoolSize, number of threads ready for handling server requests, by default 1. Range is between 0 and 100. When there are not enough ready threads to handle requests, TFTP server creates and after usage deletes additional threads.
ThreadPoolSize=5
- timeout, default timeout, in seconds, per interval. Default is three seconds, although valid range is from 1 to 120.
timeout=30
- blksize, is the maximum block size on client request. The default is 512, unless overridden by the client, with a maximum of 65464.
blksize=65464
- write, a flag for allowing, or disallowing, writing of files on the server. The default is disallowed, N. It should be set to Y to allow the creation of new files on the server.
write=Y
- overwrite, a flag for allowing, or disallowing, overwriting of files on the server. The default is disallowed, N. It should be set to Y to allow the overwriting of files on the server.
overwrite=Y
- port-range, port range on which TFTP server would respond from (default is any free port). When operating with a firewall you may like to restrict this to a suitable range, e.g.:
Example TFTPServerMT.ini
[LISTEN-ON]
#if you have more than one NIC card on your server
#can specify which cards will listen TFTP requests
#Specify the Interface you would like server to listen
#default listening port is 69, but can be overridden here
#up to 8 interfaces can be specified
#Default is All Interfaces
'128.254.185.131
'69.254.185.131:69
[HOME]
#You should specify home directory(s) here
#The home directory can be specified
#in two different ways, with alias or
#bare names without aliases. Using alias you
#can specify up to 8 directories like
#routers=c:\RouterImages\Images
#boot=d:\PXEBoot\Images
#installs=d:\PXEBoot\Images
#without aliases, only one directory can
#be specified, which will become root
#directory for tftp.
#mix-up of bare names and aliases not allowed
'c:\Installs
'routers=c:\RouterImages\Images
'boot=d:\PXEBoot\Images
'installs=c:\installs
c:\Entuity\cm_transfer\
[LOGGING]
#Logging is done in TFTPServer.log, in directory where exe is.
#Logging will be done only if run as NT Service.
#default is Errors
#Logging "All" is resources intensive, should not be normally used.
'None
Errors
'All
[ALLOWED-CLIENTS]
#These are permitted clients for TFTP Access.
#Hosts having IP address within these ip ranges
#only will be responded to DNS requests.
#32 ranges can be specified.
#If none is specified, then all are allowed
'192.168.0.1-192.168.0.254
'10.0.0.1-10.255.255.254
#block 10.44.1.12
10.44.1.0-10.44.1.11
10.44.1.13-10.44.1.255
[TFTP-OPTIONS]
#First Option is server port range on which tftpserver
#would respond from, if you have firewall
#issues, you may like to restrict this
#range. default is any free port
#do not use reserve ports less than 1024
#The Multithreaded TFTP Server listens the
#requests on port 69 but responds on any free
#port within these ranges, these are server
#ports not client ports, client can use any port
#if there is a fire wall issue, it should be
#opened for server ip for these ports.
'port-range=30000-30100
#Next is Thread Pool Size
#value of 0 means there is no thread pool
#threads will be created just in time and
#killed after serving requests.
#if simultaneous request are more than
#thread pool size, extra threads will be
#created and killed after serving requests
#but ready threads will never be less than this value
#min is 0, max can be 100, default is 1
'ThreadPoolSize=1
#Next is default timeout per interval
#if not overridden by client
#min is 1, max can be 120, default is 3 secs.
'timeout=3
#Next is max block size, allowed
#on client request. Max is 65464
#if not overridden by client
#it is always 512
'blksize=65464
#Next are the file operation permissions
#Clients can only read files if read is
#set to Y, default is Y
read=Y
#Clients can only create new files if write is
#set to Y, default is N
write=Y
#Clients can only overwrite existing files if
#overwrite is #set to Y, default is N
overwrite=Y
Comments
0 comments
Please sign in to leave a comment.