Re: Problem with my NIC
From: Dave (NO_SPAM_drobbins_at_drobbins.net)
Date: 11/29/04
- Next message: Mark A. Odell: "Re: How to determine the size of cylinder?"
- Previous message: Jean-David Beyer: "Re: How to determine the size of cylinder?"
- In reply to: Alex Harsch: "Re: Problem with my NIC"
- Next in thread: Dave: "Re: Problem with my NIC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 29 Nov 2004 16:09:53 -0500
Alex Harsch wrote:
>> Thanx Again
> Have you ever tried to use a different cable? Is it a crosslink cable that
> you
> use? Have you tried to plug it in directly in the router? I am asking,
> because when you can ping your own IP, there is only a theoretical chance
> that there is something wrong with the setup/driver/whatever. Do you have
> the
> same behavior with the other NICs also?
> Can you post the output of ifconfig with the NIC up? Alex
I have two different hardrives
harddrive A has Fedora 1 on it
harddrive B has Fedora 3 on it
I boot off harddrive A and everything works perfect
shutdown and remove A and plug in B
reboot, network no longer works
I also at one point had Fedora 2 on harddrive B
same behaviour
Fedora changed from the 2.4.x to the 2.6.x kernel between 1 and 2
this is where the problem occures, I have no idea if it's related
this switching of drives make me pretty certain there can't be any cabling
issues (who knows, I've been wrong before ;-) )
oh yea, I've also ruled out cabling issues by running the ethereal packet
sniffer while I try to ping another machine. This show no outgoing ping
packets, but there are some outgoing ARP packets asking "who has
192.168.10.10" (this tells me the packets never get to the hardware)
I think it's querying for the MAC address of who I'm trying to ping
I think this is a hint to what's wrong
at what point in the flow of the packets is ethereal intercepting them??
for that matter, what is the flow of packets??
from the ping command to the TCP-IP stack to iptables to the driver to the
hardware??
I would think the packet sniffer would listen as close to the hardware as
possible, so maybe right at the driver
I've turned iptables on and off
I don't particularly want to use it, I use my little router as a firewall
with eth0 and lo interfaces both up, I can ping my own ip address
if I kill lo (ifdown lo) I get an error message when I ping myself
(Connect:Invalid argument)
bring lo back up and I can ping myself
this tell me that when I ping myself it's actually going thru the loopback
interface, so it still appears anything going thru eth0 fails
I've been messing with this on and off for months
it's eating my brain ;-)
any ideas appreciated
Dave
- Next message: Mark A. Odell: "Re: How to determine the size of cylinder?"
- Previous message: Jean-David Beyer: "Re: How to determine the size of cylinder?"
- In reply to: Alex Harsch: "Re: Problem with my NIC"
- Next in thread: Dave: "Re: Problem with my NIC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
