SUMMARY: trying to start in.tftpd ( tftp ) and PXE-E11 ARP Time out

Many thanks to everyone who replied.

The service doesn't start until a connection is made.
Here are some samples of the responses.
You guys are the best, thanks again.

I have some major problems with PXE and I thought it was related to
tftp.
But I don't think so now.

ORIGNAL MSG:
Dear Managers,
I am having problems trying to start and verify that in.tftpd is
running.

I checked /etc/inetd.conf.
I restarted inetsvc.
I ps -ef|grep tftp and I get nothing.
Can someone please help me?

Thanks

I am running Solaris 9

RESPONSES:
inet spawns the damon when a connection is made, you wont see it
otherwise.

Cool ways to test
Processes started out of inetd.conf are only started when there is
a request for them (they are not running daemons).
To activate a new entry in inetd.conf, you must 'pkill -HUP inetd'
Then from another host telnet to the tftpd port
telnet host 69
and see if it connects, and see if an in.tftpd is running on
the remote host.

There is a tftp client (/usr/bin/tftp) that you can use to try to
connect. Type tftp, then "?" will give you a list of commands.

From another machine, try running 'tftp' to that machine. If you get a

connection, then great. in.tftp only runs when a remote machine is
trying to connect to it. (It runs on demand.)

Since it is running out of inetd, it won't appear in a process list
until it is actually called. inetd listens on the tftp port, and when a

request comes in, calls the tftp daemon.
You can run 'netstat -a | grep LIST' to see if tftpd appears in the
list
of ports that are being "listened on."

No it is not a process it works thru port #69
#lsof -i:69

Debugging Jumpstart
Tftpd is like ftpd. You won't see anything in process table unless some
process tries to connect to your server on in.tftpd port. If you are
trying to debug jumpstart then I will recommend you using snoop ether
<Ethernet address> run on any box on that subnet and you will all the
arp/rarp/tftp requests.

If you are starting this using inetd you will not see the process until
tftpd is actually called by inetd when a connection request comes in on
the tftp service address (in this case 69/udp).

-----Original Message-----
From: Bill R. Williams [mailto:brw@xxxxxxxx]
Sent: Monday, April 24, 2006 8:31 AM
To: Al Saenz
Subject: Re: trying to start in.tftpd and PXE-E11 ARP Time out


Hi Al,

Things that run under the superdaemon (inetd) only run when they are
called; they do not run all the time so your
I ps -ef|grep tftp
will not see the 'tftp' until a connection is made to the system for
'tftp'.
How it works: the superdaemon (inetd) listens on all the potential
connections in the inetd.conf file, and when a connection comes into
one of the ports inetd spawns the appropriate process and hands off
the connection to that process. (In this case a connection to port 69
will cause inetd to run tftpd and hand off the incoming socket
connection.)

An easy way to at least see if it is running is just to do
(on the tftp host in question):
telnet localhost 69
and see if you get a connection.
--
---------------------------------------------
Bill R. Williams <brw@xxxxxxxx>
------------------------ ETSU Library Systems


On Fri, Apr 21, 2006 at 05:51:56PM -0400, Al Saenz wrote:
Dear Managers,
I am having problems trying to start and verify that in.tftpd is
running.

I checked /etc/inetd.conf.
I restarted inetsvc.
I ps -ef|grep tftp and I get nothing.
Can someone please help me?

Thanks

I am running Solaris 9
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • Re: need a linux script
    ... what Jan's saying is that the problem is definitely with inetd; ... In the old days, before inetd, each port that accepted incoming ... but each daemon had to run just in case somebody tried to ... entries in /etc/inetd.conf), starts it, and passes the connection on. ...
    (alt.os.linux.suse)
  • Re: FTP Service.
    ... > When somebody connects to your box to a service maintained by inetd, ... > and hooks the incoming connection up to it. ... > don't see in.ftpds because nobody is currently connected using ftp. ... > to make it reread its conf file; when it does so, it will look up port ...
    (comp.unix.admin)
  • DCOM worm with get.bat bot.rar
    ... I just got a new DCOM worm on our honeypot. ... After the exploit on port 135 ... TFTP -i 81.103.7.66 GET get.bat ... the connection timed out. ...
    (Incidents)
  • Re: [Full-Disclosure] W32/Welchia, W32/Nachi backdoor?
    ... > Telnetting to this port seems to disconnected after 1-5 characters have been ... > tftp client doesn't seem to offer any means of specifying a port to connect ... The client to infect opens the connection with the stdin/-out of CMD.EXE ...
    (Full-Disclosure)
  • tftp and tcp_wrappers
    ... We are implementing a tftp server to ... To assist in securing this server we are using ... When inetd accepts a connection on port ... connections that have queued) that spawned the connection. ...
    (SunManagers)