linux box troubles

Thu, 15 Nov 2001 15:38:06 -0700 (MST)

On Thu, 15 Nov 2001, Jeff wrote:

> I use slackware 8 with an AMD K6 II as a firewall/misc server and haven't had that problem..
>
> Is it a default slack install with the 2.2.19 kernel?

Yes.

> I updated mine to 2.4.14 yesterday going through the IP MASQ howto from the IP masq resource site and it got rid of several misc errors I was getting.
>
> You may want to do this just for shits.
>
> What eth card do you have?  what driver is it using? what does ifconfig tell you? Are you on COX using DHCP?

rtl8139.  I'm not sure what driver it's using.  When I first installed
linux, the cards were already installed.  During the installation they
were detected.

Here's what ifconfig says:

eth0      Link encap:Ethernet  HWaddr 00:02:96:02:0D:D0
          inet addr:207.55.74.132  Bcast:207.55.74.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:308055 errors:0 dropped:0 overruns:0 frame:0
          TX packets:233574 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:311763283 (297.3 Mb)  TX bytes:26646443 (25.4 Mb)
          Interrupt:11 Base address:0x6100

eth1      Link encap:Ethernet  HWaddr 00:02:96:02:3A:3B
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35782 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58030 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2508111 (2.3 Mb)  TX bytes:78433661 (74.8 Mb)
          Interrupt:10 Base address:0x6200

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10667 (10.4 Kb)  TX bytes:10667 (10.4 Kb)

> Sounds like a card problem to me....  but need more details.
>
> let me get this straight, after it acts up, you can still telnet into it but not ping?

I can't get into it at all.  No ping, no telnet no http, nothing.