LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Linux - Distributions (http://www.linuxquestions.org/questions/forumdisplay.php?f=5)
-   -   debian tftpd (http://www.linuxquestions.org/questions/showthread.php?t=381011)

JJX 11-08-2005 02:34 AM

debian tftpd
 
I have found a lot howto but all are about fedora :(

I installed tfpd package
Where are the configs now? xinetd doesnt exist to debian

Anyone can point me to the correct direction?
(a debian based howto or something...)

thx


oops - wrong category :(
should be moved to debian :rolleyes: :rolleyes:

MensaWater 11-09-2005 11:07 AM

Debian uses the older inetd setup. Redhat/Fedora use xinetd.

For inetd you edit the /etc/inetd.conf file instead of having multiple files as in xinetd. In inetd each service is a separate line.

I don't fun tftp on my Debian but an example line from one of my HP-UX boxes (they also use inetd rather than xinetd) would be:

tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite

The "\" at the end of each line above means "continuation" so that all 3 lines are read as if they are one. The above setup is what we do for are HP-UX Ignite Server setup. You wouldn't want the ignite stuff but hopefully between that and what you've found for Redhat/Fedora you'll be able to dope out what you need.

JJX 01-04-2006 06:14 AM

i replaced tftpd package with tftpd-hpa
but still i cant connect

inetd.conf is:
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd -l -a 10.32.52.9:69 -c -p -s /tftpboot


Quote:

debian:/tftpboot# nmap -v -sU 10.32.52.9

Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2006-01-04 15:09 EET
Initiating UDP Scan against XX.XXXXXXXXXXX.XXXX (10.32.52.9) [1480 ports] at 15:09
The UDP Scan took 1.75s to scan 1480 total ports.
Host XX.XXXXXXXXXXX.XXXX (10.32.52.9) appears to be up ... good.
Interesting ports on ns.eagelidis2.awmn (10.32.52.9):
(The 1471 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
53/udp open|filtered domain
69/udp open|filtered tftp
111/udp open|filtered rpcbind
161/udp open|filtered snmp
883/udp open|filtered unknown
886/udp open|filtered unknown
1645/udp open|filtered radius
1646/udp open|filtered radacct
5060/udp open|filtered sip
but

Quote:

debian:/tftpboot# nmap 10.32.52.9
....................
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
113/tcp open auth
199/tcp open smux
512/tcp open exec
513/tcp open login
514/tcp open shell
889/tcp open unknown
2000/tcp open callbook
if i redo port scanning after 10 minutes tftpd doesnt appear in the list:

the problem is that still i cant connect from anywhere

any idea?


thx

JJX 01-04-2006 08:23 AM

for the history:

increasing the level of logging:
Quote:

Jan 4 17:15:33 debian in.tftpd[23366]: cannot set groups for user nobody
Jan 4 17:15:38 debian in.tftpd[23368]: cannot set groups for user nobody
Jan 4 17:15:43 debian in.tftpd[23369]: cannot set groups for user nobody
if i swap the "nobody" with "root" works...
so is something wrong with user nobody...

MensaWater 01-04-2006 12:31 PM

Since inetd only starts the daemon when it is called its possible it doesn't show up depending on how you're scanning. Try doing a telnet to the port tftpd uses. This should make it start the daemon. (You can just do a for loop on the system like:
while true
do ps -ef |grep tftpd
sleep 1
done

This will let you know if it starts the daemon. From your other messages it appears it is trying to however.

Looking for nobody in my /etc/inetd.conf I see:
Code:

talk            dgram  udp    wait    nobody.tty      /usr/sbin/in.talkd    in.talkd

ntalk          dgram  udp    wait    nobody.tty      /usr/sbin/in.ntalkd    in.ntalkd

finger          stream  tcp    nowait  nobody  /usr/sbin/tcpd  /usr/sbin/in.fingerd

Looking at nobody I see in /etc/passwd:
Code:

nobody:x:65534:65534:nobody:/home:/bin/sh
Looking in /etc/group there is no "nobody".

Looking in /etc/group for 65534 I see:
Code:

nogroup:x:65534:
Doing a test from another system it worked fine so nobody itself is not an issue for me.

Your message complains about groups. You can change the entry in inetd.conf to specify user.group - The "nobody.tty" in my debian is specifying group tty which is in /etc/groups:
Code:

tty:x:5:
It might be worthwhile to specify a group


All times are GMT -5. The time now is 05:31 AM.