Did that. Now no net. WAS: Re: which upgrade path from woody?

[Hendrik Boom <hendrik@pooq.com>]

On Mon, Jul 26, 2004 at 11:44:20AM -0400, Alec Berryman wrote:
> begin  quotation of Hendrik Boom:
> 
> > This still leaves open which is the best way to go about it -- copy and
> > upgrade, or new install.
> 
> New install.  The new installer will recreate automatically most of
> the config files you'd be moving, and you'll have a cleaner system to
> start from.

Tried that, now no net.

Created a beta-4 iso for the debian net-installer, installed from that
onto /dev/hda3.  /dev/hda4 still contains my woodu system, which still works
perfectly.

But the new and very minimal sarge can't access the net.  Pings don't seem
to get as far as the ethernet card.

Here's the routing table:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.25.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         172.25.1.1      0.0.0.0         UG    0      0        0 eth0

It's identical to the routing table on the woody system.

Here's the output from ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:0A:E6:55:93:CD  
          inet addr:172.25.1.4  Bcast:172.25.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0xb400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:657 (657.0 b)  TX bytes:657 (657.0 b)


It's the same as the one from woody, except that
	woody gives me nonzero packet counts.
	etho has interrupt: 18 instead of interrupt:5  Aren't these
		dynamically assigned during boot, though?

Pinging to 172.25.1.4 and 127.0.0.1 work fine.  Both of them are,
of course, IP numbers for the machine doing the pinging, so it doesn't
need to get to the ethernet card.

What should I do to diagnose the problem.

Did the installer, which seemed pretty straightforward, miss some
essential component?  I did the default (I presume nonexpert 2.4 kernel)
installation.  Did I do something unobviously wrong?
Needless to say, I can't access any of the Debian archives
to get any further.

-- hendrik