On Wed, Aug 25, 1999 at 11:25:18PM +0900, Makoto Fujiwara wrote:
> Assuming sysinst has a problem on doing ifconfig (or nfs mounting),
> and you do ifconfig before running sysinst, does your question
> go away ?

Good thought, but one I already had, unfortunately.

It's when I ifconfig manually that I get the no-packet-sending ping.

I'll go try it in *exactly* those steps right now, though, and come
back to this email after I have.

That web page is mighty helpful, btw, too bad I didn't have the url
when I was figuring out what device was the floppy. :^>

[time passes]

Okay, I tried it, based on your web page. For starters, I'm not trying
to install via nfs but via ftp, but I don't even get so far as you do
in your example when you find that sysinst doesn't do nfs properly.

I can't even get *to* the ping test, at this point. Even if I ifconfig
before startin sysinst, sysinst still wants to set up the network
itself (though it does pick up the values I set in the manual
ifconfig), and needs to know the default route and DNS IP, of course.
I give those to it, tell it the settings are okay, and then hang.

Can't even get to the ping test.

If I could, then I would give up on ftp, download the files to a Sun
here at cs.swarthmore.edu, and nfs mount them from there (exactly as
Makoto Fujiwara's web page describes), but I don't even get so far as
failing to connect to an ftp server.

Breaking back out of sysinst (^C works), I try to ping the IP address
of the name server, which I have verified is reachable and pingable
from MacOS running on exactly the same hardware (Ethernet card, MAC
address, Ethernet port, so forth), and get the same 0 packets sent, 0
packets received response. Having truss or something on the boot
floppy might make it possible for me to diagnose what's actually going
on here. Maybe I should put some tools like truss, gdb, and a few
others on an nfs mount and check things out that way?

Incidentally, it would appear that lo0 is also configured (shows up in
ifconfig -a at IP 127.0.0.1), but when I try to ping that, I am still
unable to even send packets. Yes, that's right - no packets to the
kernel's loopback interface. No, that doesn't make any kind of sense.
No, ping doesn't produce any error messages, just happily refuses to
send ICMP.

Still clueless as to the real problem, but beginning to think with
more assurance that it has to do with /sbin/ping or even the TCP/IP
code in the kernel on the boot floppy...

Please, I really don't want to go back to LinuxPPC, but this machine
*will* be up and running by the end of this week even if I do have to.

       ~ g r @ granularity.net