Subject: Re: [vserver] tftp server problem
From: Corin Langosch <corinl@gmx.de>
Date: Mon, 18 Feb 2008 17:22:39 +0100
Mon, 18 Feb 2008 17:22:39 +0100
Hi!

I now changed my config to use inetd too, but it still does not work:

inetd.conf
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd 
--tftpd-timeout 300 --retry-timeout 5 --no-multicast --maxthread 100 
--verbose=7 --no-blksize /tftpboot

pstree
init???cron
     ??dhcpd3
     ??inetutils-inetd???in.tftpd???2*[{in.tftpd}]
     ??ntpd
     ??syslog-ng

netstat
udp        0      0 192.168.1.203:tftp      
*:*                                22675/inetutils-ine

syslog
Feb 18 17:20:52 system in.tftpd[22675]: connect from 192.168.1.32 
(192.168.1.32)
Feb 18 17:20:52 system atftpd[22675]: Advanced Trivial FTP server 
started (0.7)
Feb 18 17:20:52 system atftpd[22675]:   started by inetd
Feb 18 17:20:52 system atftpd[22675]:   logging level: 7
Feb 18 17:20:52 system atftpd[22675]:   directory: /tftpboot/
Feb 18 17:20:52 system atftpd[22675]:   user: nobody.nogroup
Feb 18 17:20:52 system atftpd[22675]:   log file: syslog
Feb 18 17:20:52 system atftpd[22675]:   server timeout: 300
Feb 18 17:20:52 system atftpd[22675]:   tftp retry timeout: 5
Feb 18 17:20:52 system atftpd[22675]:   maximum number of thread: 100
Feb 18 17:20:52 system atftpd[22675]:   option timeout:   enabled
Feb 18 17:20:52 system atftpd[22675]:   option tzise:     enabled
Feb 18 17:20:52 system atftpd[22675]:   option blksize:   disabled
Feb 18 17:20:52 system atftpd[22675]:   option multicast: disabled
Feb 18 17:20:52 system atftpd[22675]:      address range: 239.255.0.0-255
Feb 18 17:20:52 system atftpd[22675]:      port range:    1758
Feb 18 17:20:52 system atftpd[22675]: Creating new socket: 
192.168.1.203:32947
Feb 18 17:20:52 system atftpd[22675]: Serving pxelinux.0 to 
192.168.1.32:2070
Feb 18 17:20:52 system atftpd[22675]: tsize option -> 13992
Feb 18 17:20:52 system atftpd[22675]: Creating new socket: 
192.168.1.203:32948
Feb 18 17:20:52 system atftpd[22675]: Serving pxelinux.0 to 
192.168.1.32:2071
Feb 18 17:20:57 system atftpd[22675]: timeout: retrying...
Feb 18 17:20:57 system atftpd[22675]: timeout: retrying...

any more hints? may be there is a bug in vserver with udp traffic?

Corin

Ben Green schrieb:
> On Mon, 18 Feb 2008 12:05:13 -0000, Corin Langosch <corinl@gmx.de> wrote:
>
>   
>> cat /etc/default/atftpd
>> USE_INETD=false
>> OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5 --maxthread 100
--verbose=7  /tftpboot"
>>     
>
> Mine looks like this:
>
> USE_INETD=true
> OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5     --mcast-port
1753 --mcast-addr 239.255.0.0-255 --mcast-ttl 16 --maxthread 100 --verbose=7  /tftpboot"
>
> I wasn't aware I was using inetd! inetd.conf line looks like this:
>
> tftp            dgram   udp     wait    nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout
300 --retry-timeout 5     --mcast-port 1753 --mcast-addr 239.255.0.0-255 --mcast-ttl
16 --maxthread 100 --verbose=1  --no-blksize /tftpboot
>
>   


Hi!

I now changed my config to use inetd too, but it still does not work:

inetd.conf
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --no-multicast --maxthread 100 --verbose=7 --no-blksize /tftpboot

pstree
init─┬─cron
     ├─dhcpd3
     ├─inetutils-inetd───in.tftpd───2*[{in.tftpd}]
     ├─ntpd
     └─syslog-ng

netstat
udp        0      0 192.168.1.203:tftp      *:*                                22675/inetutils-ine

syslog
Feb 18 17:20:52 system in.tftpd[22675]: connect from 192.168.1.32 (192.168.1.32)
Feb 18 17:20:52 system atftpd[22675]: Advanced Trivial FTP server started (0.7)
Feb 18 17:20:52 system atftpd[22675]:   started by inetd
Feb 18 17:20:52 system atftpd[22675]:   logging level: 7
Feb 18 17:20:52 system atftpd[22675]:   directory: /tftpboot/
Feb 18 17:20:52 system atftpd[22675]:   user: nobody.nogroup
Feb 18 17:20:52 system atftpd[22675]:   log file: syslog
Feb 18 17:20:52 system atftpd[22675]:   server timeout: 300
Feb 18 17:20:52 system atftpd[22675]:   tftp retry timeout: 5
Feb 18 17:20:52 system atftpd[22675]:   maximum number of thread: 100
Feb 18 17:20:52 system atftpd[22675]:   option timeout:   enabled
Feb 18 17:20:52 system atftpd[22675]:   option tzise:     enabled
Feb 18 17:20:52 system atftpd[22675]:   option blksize:   disabled
Feb 18 17:20:52 system atftpd[22675]:   option multicast: disabled
Feb 18 17:20:52 system atftpd[22675]:      address range: 239.255.0.0-255
Feb 18 17:20:52 system atftpd[22675]:      port range:    1758
Feb 18 17:20:52 system atftpd[22675]: Creating new socket: 192.168.1.203:32947
Feb 18 17:20:52 system atftpd[22675]: Serving pxelinux.0 to 192.168.1.32:2070
Feb 18 17:20:52 system atftpd[22675]: tsize option -> 13992
Feb 18 17:20:52 system atftpd[22675]: Creating new socket: 192.168.1.203:32948
Feb 18 17:20:52 system atftpd[22675]: Serving pxelinux.0 to 192.168.1.32:2071
Feb 18 17:20:57 system atftpd[22675]: timeout: retrying...
Feb 18 17:20:57 system atftpd[22675]: timeout: retrying...

any more hints? may be there is a bug in vserver with udp traffic?

Corin

Ben Green schrieb:
On Mon, 18 Feb 2008 12:05:13 -0000, Corin Langosch <corinl@gmx.de> wrote:

  
cat /etc/default/atftpd
USE_INETD=false
OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5 --maxthread 100 --verbose=7  /tftpboot"
    

Mine looks like this:

USE_INETD=true
OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5     --mcast-port 1753 --mcast-addr 239.255.0.0-255 --mcast-ttl 16 --maxthread 100 --verbose=7  /tftpboot"

I wasn't aware I was using inetd! inetd.conf line looks like this:

tftp            dgram   udp     wait    nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5     --mcast-port 1753 --mcast-addr 239.255.0.0-255 --mcast-ttl 16 --maxthread 100 --verbose=1  --no-blksize /tftpboot