bproc help request

[lothar at triumf.ca]

Michal Jaegermann wrote:

>>aftpd start up does not change anything either.
>>    
>>
>
>This usually runs from xinetd so starting that up should fail with
>"port busy" or similar.
>
>If you will type 'chkconfig --list' you see close to the bottom
>'tftp: on'  (that name can be slightly different).
>  
>
tftp is 'on'



>  
>
>>I am sure how you do this. That's the file.
>>
>>
>># default: off
>># description: The tftp server serves files using the trivial file 
>>transfer \
>># protocol. The tftp protocol is often used to boot diskless \
>># workstations, download configuration files to network-aware printers, \
>># and to start the installation process for some operating systems.
>>service tftp
>>{
>>disable = no
>>socket_type = dgram
>>protocol = udp
>>wait = yes
>>user = nobody
>>group = nobody
>>server = /usr/sbin/in.tftpd
>>server_args = /tftpboot
>>}
>>    
>>
>
>Looks sane.  '/tftpboot' should be a default. Files you want to
>serve from /tftpboot/ directory are readable by nobody.nobody, I
>presume?
>
>  
>
>>>Or maybe you are blocking it with your
>>>ipchains or iptables setup or through tcp_wrappers (files
>>>/etc/hosts.allow and /etc/hosts.deny)?
>>>
>>>      
>>>
>>Don't think so, but these are the files:
>>    
>>
>
>Would be nice if you could use a mailer able not mangle this by
>wrapping lines.
>
>  
>
>>in.tftpd: 192.168.0.0/24
>>    
>>
>
>Without knowing on which network are really clients trying to reach
>your tftp server I cannot tell if this is correct or not.
>
>  
>
>>As of ipchains:
>>
>>ipchains -L
>>ipchains: Incompatible with this kernel
>>    
>>
>
>Well, this really means that a corresponding module is not loaded
>(likely because it was not configured and or started).  Until this
>modules is absent things are "incompatible". :-)
>You cannot load support for and run ipchains and iptables at the
>same time. One or another.
>
>  
>
>>The kernel is from a bproc distribution.
>>    
>>
>
>???  'uname -a'?
>  
>

kernel 2.4.18-hddcs.17.2.smp

>  
>
>>iptables -L
>>    
>>
>....
>
>Really no rules; so nothing blocks here.
>
>There are chances that after a failed attempt your
>/var/log/messages, or maybe /var/log/secure, recorded some useful
>information.
>
>A trival way to check a sanity of a setup and a contact it to
>write a shell script like that
>
>#!/bin/sh
>echo "Hello, I am a net service"
>( echo -n "Got a contact: " ; date ) >> /tmp/junk.log
>exit
>
>make it executable, write an xinetd config file like the one you
>have above but for 'protocol = tcp' (different name, of course) and
>restart xinetd service.  If things are ok then after
>'telnet <server> tftp' from a prospective client it should talk back
>to you and record that event in /tmp/junk.log.
>
> Michal
>
>  
>
Well, I made a tcpdump (-i eth1), when starting up teh slave node , and 
the only dialog is:

rarp who-is .1 tell .1
rarp reply .1 at .-1

Lothar