Re: tftp hangs after 1037 blocks

["Arno Schuring" <aelschuring@hotmail.com>]

Hello again!

I have some tcpdump output which might indicate where things go wrong. It
seems indeed the network card (client) just disappears from the network
after block 1037, at least that's how I would interpret the sudden ARP
requests. Does anyone have any suggestion other than "try a new network
card" - which I will try tomorrow?


16:49:16.301816 IP server.LooS.org.1047 > 192.168.10.65.1045: UDP, length:
516
16:49:16.303952 IP 192.168.10.65.1045 > server.LooS.org.1047: UDP, length: 4
16:49:16.304377 IP server.LooS.org.1047 > 192.168.10.65.1045: UDP, length:
516
16:49:16.306513 IP 192.168.10.65.1045 > server.LooS.org.1047: UDP, length: 4
16:49:16.307035 IP server.LooS.org.1047 > 192.168.10.65.1045: UDP, length:
516
16:49:18.623501 arp who-has 192.168.10.65 tell server.LooS.org
16:49:19.623243 arp who-has 192.168.10.65 tell server.LooS.org
16:49:20.622989 arp who-has 192.168.10.65 tell server.LooS.org
16:49:21.302970 IP server.LooS.org.1047 > 192.168.10.65.1045: UDP, length:
516
16:49:21.622734 arp who-has 192.168.10.65 tell server.LooS.org
16:49:22.622483 arp who-has 192.168.10.65 tell server.LooS.org
16:49:23.622226 arp who-has 192.168.10.65 tell server.LooS.org
16:49:26.301691 arp who-has 192.168.10.65 tell server.LooS.org
16:49:27.301298 arp who-has 192.168.10.65 tell server.LooS.org
16:49:28.301040 arp who-has 192.168.10.65 tell server.LooS.org
16:49:31.300414 arp who-has 192.168.10.65 tell server.LooS.org
16:49:32.300025 arp who-has 192.168.10.65 tell server.LooS.org
16:49:33.299770 arp who-has 192.168.10.65 tell server.LooS.org
16:49:36.299134 arp who-has 192.168.10.65 tell server.LooS.org
16:49:37.298750 arp who-has 192.168.10.65 tell server.LooS.org
16:49:38.298497 arp who-has 192.168.10.65 tell server.LooS.org


My second problem has been solved. Using tcpdump (again), I noticed nfs was
flooding the network when executing passwd or login, and using
nfsd --log-transfers I saw it was happening when accessing /etc/shadow. I
had misconfigured the nfsroot network share - it missed no_root_squash.

Anyways,

thanks for the help,
Arno Schuring


  np: Nature And Organisation - My Black Diary
----- Original Message ----- 
From: "Arno Schuring" <aelschuring@hotmail.com>
To: <netboot@baghira.han.de>
Sent: Monday, March 15, 2004 9:44 AM
Subject: Re: tftp hangs after 1037 blocks


>
>
> Thanks for your reply. It hadn't occurred to me this might just as well be
a
> server problem, so thank you for pointing this out. Will try to find out
> more soon.
>
> slightly off-topic:
> Using a stripped-down kernel, I have managed to remote boot my machine.
> However, I can't login because of "Out of memory - killed process login".
> Executing sulogin results in the same. When I boot init=/bin/sh,
everything
> works fine, except when I try to run 'login' or 'passwd <user>' - it
results
> again in the out of memory message. Can anyone tell me where is the right
> place to ask such a question (I'm using shadow-4.0)?
>
> >
> > How about a different network card? What type if TFTP server do you use?
> > Does the server print anything in the logs? You should also check the
> > TFTP traffic using tcpdump or ethereal. Does the client send out a
request
> > for block 1038, but doesn't get a response from the server?
> tftp server? uhm... don't know. Have just compiled the one from gnu
> inetutils-1.4.2, and the result is the same.
> About a different card: the only ones I have directly available are
> Cabletron E21xx cards, for which I haven't created a succesful
> bootrom(floppy) yet. Will try to get a 3com card for further testing.
> The server logs only the request and filename:
> Mar 14 23:45:56 server tftpd[2848]: in.tftpd[2847]: connect from
> 192.168.10.65
> Mar 14 23:45:56 server tftpd[2848]: tftpd: trying to get file:
> /tftpboot/vmlinux-i486
> tcpdump might reveal more, though I haven't much experience with it.
>
>
> Thanks,
> Arno
>
>
>
>   np: Capercaillie - The Tree
>
===========================================================================
> This Mail was sent to netboot mailing list by:
> "Arno Schuring" <aelschuring@hotmail.com>
> To get help about this list, send a mail with 'help' as the only string in
> it's body to majordomo@baghira.han.de. If you have problems with this
list,
> send a mail to netboot-owner@baghira.han.de.
>
>
===========================================================================
This Mail was sent to netboot mailing list by:
"Arno Schuring" <aelschuring@hotmail.com>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.