Menu

tftp: sendto: Permission denied

Help
2009-05-31
2020-08-26
  • Roger Moore

    Roger Moore - 2009-05-31

    When I attempt to startup TFTP, here is what I receive,

    [root@vm-centos5 tftpserversp]# ./tftpserver -v
    TFTP Server SinglePort Version 1.62 Unix Built 1621

    starting TFTP...
    username: john1726
    alias / is mapped to /home/john1726/
    permitted clients: all
    max blksize: 65464
    default blksize: 512
    default timeout: 3
    file read allowed: Yes
    file create allowed: No
    file overwrite allowed: No
    listening on: 0.0.0.0:69

    Accepting requests..

    Then in another terminal, I attempt to obtain a file I have placed in the home directory, but I receive the following error message,

    [root@vm-centos5 tftpserversp]# !tf
    tftp 127.0.0.0
    tftp> get test.txt
    tftp: sendto: Permission denied

    Here is the tftpserver.ini file,

    #This file stores configuration settings.
    #It should be edited and moved to /etc directory
    #unless overridden by -i flag
    #Anything starting with punctuation would be comment
    #comment ' should be removed in front of sample values if used/changed

    #IMPORTANT WARNING Never Edit this file using Windows Editor

    [LISTEN-ON]
    #if you have more than one NIC card on your server
    #can specify which cards/ports will listen TFTP requests
    #Specify the Interface you would like server to listen
    #default listening port is 69, but can be overridden here
    #listening on ports less than 1024 needs root account
    #upto 8 interfaces can be specified
    #Default is All Interfaces
    '128.254.185.131
    '192.168.0.40:69
    '127.0.0.1:3000

    [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 upto 8 directories like
    #routers=c:/RouterImages/Images
    #without aliases, only one directory can
    #be specified, which will become root
    #directory for tftp.
    #mixup of bare names and aliases not allowed
    #default will be home directory of user
    'routers=/hda1/RouterImages/Images
    'boot=/mnt/pc1/PXEBoot/Images
    'installs=/hda5/installs
    '/ldaphome/n9912747/tftpservermt
    '/home/john1726

    [LOGGING]
    #Logging is done to SYSLOG,
    #Logging will be done only if run as Service (without -v flag)
    #default is None
    #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 hosts or 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
    '33.67.8.123

    [TFTP-OPTIONS]
    #First option is username (login), this is the user, who
    #will be owner of process, the process can be started as
    #privileged user and after opening privileged ports,
    #would run as this user. This user would be owner
    #of new files put to server. When overwriting files,
    #this user should have write access and for reading
    #files, this user should have read access to the files.
    username=john1726

    #next is default timeout per interval
    #if not overridden by client
    #min is 1, max can be 255, default is 3
    '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=N

    Could you please tell me, what am I missing?  I've set the test.txt file permissions using chmod 777 test.txt.

    TIA.

     
    • Roger Moore

      Roger Moore - 2009-06-01

      Please disregard my previous message--I've resolved the issue.

       
  • Donald1010

    Donald1010 - 2020-08-26

    Killing selinux is never the correct answer in the long haul, you can utilize this to check whether selinux is preventing you from accomplishing something as a fast test before walking out on and fixing the selinux setting. However, killing selinux is just a moronic thought.

     

Log in to post a comment.