Port-i386 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 6.0.1 upgrade dhcp problem

    Date:        Wed, 30 Jan 2013 10:18:39 +0100
    From:        Martin Husemann <martin%duskware.de@localhost>
    Message-ID:  <20130130091839.GA24130%mail.duskware.de@localhost>

  | This all looks correct so far, however:

I still suspect that "looks correct" is the issue here, and that while
the right things are supposed to be happening, for some reason on the
system with the problem, they're not.

  | Is your dhpc server configured to not answer pings?

While that would be a problem if it were the case, it clearly is
not immediately relevant here.   The "ping: sendto: No route to host"
error indicates that the ICMP echo packets were never sent anywhere.
Whether the server would reply or not is kind of a moot point.

Something is preventing this particular host from ever getting configured
properly (using the NetBSD 6 CD).

Another possible difference is the CD format - did NetBSD 5 still use the
embedded mini-root format, or had that already switched to the root on
cd boot method that NetBSD 6 uses?   Maybe there's something odd about the
CD drive on the system that's failing?

What would probably be most instructive would be to boot from the NetBSD 6
CD, and then escape to the shell from sysinst, and simply try manually
configuring the interface - we know from the dhcp output what values should
be configured, so ...

        ifconfig fxp0 inet up
        route add default

in theory anyway, should work.  If they do, then the problem must be
something with the way those commands are being (or not being) correctly
executed when from from dhcpcd.   If they fail, then the way they fail
may give a clue what the problem is.

The fact that two different network interfaces fail the same way on one
system, and everything works on a different system (with apparently the
same networking hardware) means I'd be looking at something else that's
different between the two systems, like perhaps the CD (or DVD) drive,
or ...   It all looks very odd, and the root cause is likely to be something
simple but obscure.


Home | Main Index | Thread Index | Old Index