Reading through the threads I realized this has become somewhat of a
convoluted topic. I wanted to figure out a sure-fire, quick and simple
approach not only for Rich but for myself and others that could be followed
and would help folks determine where the problem might be.
>
> So here's the method, I've come up with.
>
> 1. Run the command "ifconfig" from a terminal shell.
> It the command results show an "eth" interface with a "HWaddr" then the
> OS sees the NIC. Which means the NIC drvier module is loaded. Go to step 5
> *
> *
> *ifconfig eth0*
> *eth0 Link encap:Ethernet HWaddr 00:1c:25:18:3c:78 *
> * UP BROADCAST 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:20 Memory:fe000000-fe020000 *
>
> 2. If you don't see any "eth" interfaces listed then run the command
> "dmesg | grep Ethernet" to get information on the physical card
>
> *lspci | grep Ethernet*
> *00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network
> Connection (rev 03)*
> *
> *
>
* If no Ethernet controller is listed than you have a serious hardware
problem with either the NIC or computer.
> **
> 3.* *Then run the command "dmesg | grep Network" to get driver information
> *
> *
> *dmesg | grep Network*
> *[ 1.382194] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k*
>
* If no Network driver is listed or there are error messages than either
there's no Ethernet driver installed or it's the wrong wrong.
> *
> *
> 4. Then run the command "lsmod | grep <network driver>". In this example
> the command would be "lsmod | grep e1000e"
>
> If the right driver is installed, you should get a result like this.
>
*lsmod | grep e1000e*
*e1000e 139997 0 *
If not, you've got a NIC driver problem. You can try to load the driver
manually via the "modprobe" command or do some research to find the right
driver.
5. The simplest, quickest and easiest way I can think of to actually test
the NIC, driver and network config is to either connect it to a LAN with a
DHCP server or directly to a router that is handing out DHCP addresses or
connect it to another computer via a cross-over cable and configure
statically assigned ip addresses on the both computers.
5A. Connect either a cross-over cable between two computers or connect a
regular straight through Ethernet cable to ether a LAN jack or directly to
a hub/switch/router and check to see that you get a link light on your NIC
to very the card, the cable and the other device is functional before doing
an ip connectivity test.
I often use the following ip addr scheme for internal testing between
devices.
Device #1 ip addr = 1.2.3.4. / 255.255.255.0
Device #2 ip addr = 1.2.3.5. / 255.255.255.0
5B. Then do a simple ping test to either the other computer (no routing /
gateway config needed) or to the default gateway address that is provided
by the DHCP server or router. This can be found by running the command
"route -n". Just look for the "Gateway" address for the Network Interface
your're working on. It should also have the "G" flag, (gateway), set.
*Destination Gateway Genmask Flags Metric Ref Use
Iface*
*0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
0 eth0*
I hope this helpful. It can be easily adopted for wireless testing too.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
