Re: Malformed Release file

[Scott Hussey <scott@matrix.lcl.lib.mo.us>]

On Tue, Nov 13, 2001 at 10:29:36AM +0100, Guido Guenther wrote:
> On Mon, Nov 12, 2001 at 10:29:13PM -0600, Scott Hussey wrote:
> > I've tried the 3.0.15 boot floppies with no better success. I get to exactly
> > the same point w/ the installer and then get the malformed release file trying
> > to install with either woody or sid. Any pointers?
> O.k. this is not 3.0.16 related then - good. The installer suggestts
> http.us.debian.org as default download location - I know this worked for
> me several times - did you try these servers? Does the installer at
> least download the release file? Can you compare the downloaded one with
> the one found on http.us.debian.org (md5sum)?

Ok, I did a tcpdump analysis when the indy tries to get the Release
file and all I see are a bunch of nfs packets, no ftp packets. Below
is a small segment of the packets I saw w/ tcpdump while the indy was
trying to get the Release file/base system:

192.168.1.20 - The Indy booted with bootp and an NFS root using bf 3.0.15
192.168.1.2 - My Intel debian box running the bootpd and the NFS daemon
192.168.1.1 - Mysteriously not involved, but it should be. This is our gateway to broadband

11:10:23.673866 192.168.1.20.2751444638 > 192.168.1.2.nfs: 112 lookup [|nfs] (DF)
11:10:23.674306 192.168.1.2.nfs > 192.168.1.20.2751444638: reply ok 128 lookup [|nfs] (DF)
11:10:23.676197 192.168.1.2.32768 > proxy1.clmba1.mo.home.com.domain: 6431+ (42)
11:10:23.677084 192.168.1.20.2751444639 > 192.168.1.2.nfs: 116 lookup [|nfs] (DF)
11:10:23.677275 192.168.1.2.nfs > 192.168.1.20.2751444639: reply ok 128 lookup [|nfs] (DF)
11:10:23.679085 192.168.1.20.2751444640 > 192.168.1.2.nfs: 104 getattr [|nfs] (DF)
11:10:23.679211 192.168.1.2.nfs > 192.168.1.20.2751444640: reply ok 96 getattr [|nfs] (DF)
11:10:23.680927 192.168.1.20.2751444641 > 192.168.1.2.nfs: 272 write [|nfs] (DF)
11:10:23.681193 192.168.1.2.nfs > 192.168.1.20.2751444641: reply ok 96 write [|nfs] (DF)
11:10:23.682365 192.168.1.20.2751444642 > 192.168.1.2.nfs: 112 lookup [|nfs] (DF)
11:10:23.682539 192.168.1.2.nfs > 192.168.1.20.2751444642: reply ok 128 lookup [|nfs] (DF)
11:10:23.698109 192.168.1.20.2751444643 > 192.168.1.2.nfs: 120 lookup [|nfs] (DF)
11:10:23.698281 192.168.1.2.nfs > 192.168.1.20.2751444643: reply ok 128 lookup [|nfs] (DF)
11:10:23.699619 192.168.1.20.2751444644 > 192.168.1.2.nfs: 112 lookup [|nfs] (DF)
11:10:23.699882 192.168.1.2.nfs > 192.168.1.20.2751444644: reply ok 128 lookup [|nfs] (DF)
11:10:23.700683 192.168.1.20.2751444645 > 192.168.1.2.nfs: 116 lookup [|nfs] (DF)
11:10:23.700857 192.168.1.2.nfs > 192.168.1.20.2751444645: reply ok 128 lookup [|nfs] (DF)
11:10:23.706681 192.168.1.20.2751444646 > 192.168.1.2.nfs: 112 lookup [|nfs] (DF)
11:10:23.706851 192.168.1.2.nfs > 192.168.1.20.2751444646: reply ok 128 lookup [|nfs] (DF)
11:10:23.707637 192.168.1.20.2751444647 > 192.168.1.2.nfs: 124 lookup [|nfs] (DF)
11:10:23.707764 192.168.1.2.nfs > 192.168.1.20.2751444647: reply ok 28 lookup [|nfs] (DF) 

This segment was taken while requesting woody from 141.213.4.21 (one of the http.us.debian.org
servers). I typed the IP in manually to see if DNS problems were causing this. No where throughout
the tcpdump output do I see any connection being made from 192.168.1.20 to 141.213.4.21:ftp, so
I assume that the Indy is not even getting a Release file. 
-- 
Scott Hussey
scott@matrix.lcl.lib.mo.us
stha44@mizzou.edu