Operating System - HP-UX
1828233 Members
2743 Online
109975 Solutions
New Discussion

TFTP Problem: Can't resolve hostname (tusc output included)

 
Gus Larsson
Advisor

TFTP Problem: Can't resolve hostname (tusc output included)

Hello,

Several months ago I posted a question to the newsgroups wondering why my tftpd can't resolve a hostname while ftpd can. The net effect is that my tftp entry in /var/adm/inetd.sec has to specify IP addresses to grant access to, while my ftp entry in that file can use either hostnames or IP addresses.

Rick Jones responded that it might be interesting to see a tusc trace of inetd to see what it does differently between the two invocations. So, since I had a little spare time, I decided to install tusc and do a test of these services.

My test procedure was as follows:
1) Edit tftp line in /var/adm/inetd.sec to grant access to
my hostname (npas17) only.
2) Kill any running tftp process.
3) In one terminal window, run "tusc -f -v -o outfile1.txt 953", where 953 was the PID of inetd
4) In another window, type "tftp npas17".
4a) At tftp prompt, type "get efile", which is a 26-byte text file in the tftp home dir.
4b) Process hangs for about 30 seconds as it tries to connect with the tftp server, and it eventually times out.
4c) Quit tftp.
5) Kill the tusc run.
6) Edit /var/adm/inetd.sec, change the tftp line to allow
access to my IP address.
7) Repeat steps 2-5, except that 4b is successful this time.
8) Run tusc again, as in step 3.
9) Run "ftp npas17" in another window, successfully logging in and exiting.
10) Kill tusc.

So the inetd tusc output I have covers the following three cases :
1) TFTP fails due to hostname being in inetd.sec.
2) TFTP succeeds due to IP address being in inetd.sec
3) FTP succeeds with hostname being in inetd.sec.

Since it looks like I can attach only one file at a time here, I'll put the first case below and attach the other two in successive messages.

Thanks for any help,

Gus




3 REPLIES 3
Gus Larsson
Advisor

Re: TFTP Problem: Can't resolve hostname (tusc output included)

And here is the case where the tftp was SUCCESSFUL (due to the IP address - not the hostname - being in the inetd.sec file)
Gus Larsson
Advisor

Re: TFTP Problem: Can't resolve hostname (tusc output included)

Finally, this is the FTP case, which had the hostname in the inetd.sec file and was successful. Since there was an excessive amount of output here, I chopped it off once the identd process was forked.
Gus Larsson
Advisor

Re: TFTP Problem: Can't resolve hostname (tusc output included)

PLEASE DISREGARD THE SECOND MESSAGE - I INCLUDED THE WRONG FILE! Below is the SUCCESSFUL tftp session.

Sorry about that! I knew that would happen...