Destination Unreachanble: Fedora Core 2 : Network Does not work.

Hi,
I have just installed Fedora Core 2 in my system (Dual OS : Windows and
Linux)
I can ping any system on the network under windows.

But, when i ping any system on the network under Linux I get,
Undestination Unreachable error.


I have Inter Pro 100 Ethernet card on my system.

The Static IP is same for Windows and Linux.


When i do ifconfig ; i am getting ip, netmask everything is ok. except
Tx Packets and Rx Packets which are 0.



I tried

cardctl ident

I got an message saying no devices in /proc/devices.

I dont know what is the problem.

I checked The driver is e100 it is loaded. but still network is not
working.

Please advice.

Would appreciate if you could tell me what (steps) i should do inorder
to correct my problem.


Regards,
John

(E-Mail Removed) wrote:

> cardctl ident
>
> I got an message saying no devices in /proc/devices.

So the ethernet interface is NOT a pcmcia/cardbus device.....

Try using something like; /sbin/lspci -v

> I dont know what is the problem.
>
> I checked The driver is e100 it is loaded. but still network is not
> working.
>
> Please advice.
>
> Would appreciate if you could tell me what (steps) i should do inorder
> to correct my problem.

Sound like iptables might be blocking everything, try as root turning it
off to verify;

service iptables stop
ping xxx.xxx.xxx.xxx <-- some address on your network
service iptables start
ping xxx.xxx.xxx.xxx <-- same address as the first time

Please read;

http://www.linuxguruz.com/iptables/howto/
man iptables



--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759

In article <(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

>I have just installed Fedora Core 2 in my system (Dual OS : Windows and
>Linux)
>I can ping any system on the network under windows.
>
>But, when i ping any system on the network under Linux I get,
>Undestination Unreachable error.

That says the networking is not operating.

>I have Inter Pro 100 Ethernet card on my system.

Look in the boot messages (/var/log/messages) and see how the card is
being configured. Pay attention to the speed (10 vs 100) and duplex
(half vs full).

>When i do ifconfig ; i am getting ip, netmask everything is ok. except
>Tx Packets and Rx Packets which are 0.

It might seem OK to you, but show us. If you are paranoid about someone
seeing your IP address, change the first two or three octets ONLY of
the address (IP, network and broadcast)m and tell people that you have
done so. DO NOT CHANGE ANYTHING ELSE.

>I tried
>
>cardctl ident
>
>I got an message saying no devices in /proc/devices.

So, it's not a PCMCIA card. What's the output of 'lspci -vv' (the stuff
that relates to your card, not everything else).

>I dont know what is the problem.

What does the routing table show? (/sbin/route -n)
What firewall rules? (/sbin/iptables -L)

>I checked The driver is e100 it is loaded. but still network is not
>working.

Something screwy in the network setup. Assuming static addresses, what's
the contents of /etc/sysconfig/network and
/etc/sysconfig/network-scripts/ifcfg-eth0 (assuming the first interface card).
Same rules about changing things - only the first two or three octets.

>Would appreciate if you could tell me what (steps) i should do inorder
>to correct my problem.

First, you have to identify the problem. Then we can talk about corrections.

Old guy

Hi,

I am giving the outputs of the following command for assitance.


Name Network Card: Inter Pro 100
Nature Of Problem: Network Works while in Windows (i am able to ping to
any machine). But, in Linux it does Not Work, unable to ping to any
machine on network.
get Errror: Destination Host Unrechable.


Details Of Commands Executed:
---------------------------------------------
Command: cardctl ident

no pcmcia driver in /proc/devices
------------------------------------------------

Command: ifconfig -a
-----------------------------------------------

eth0 Link encap:Ethernet HWaddr 00:00:E2:49:1A:A9
inet addr:XX.YY.13.88 Bcast:192.168.13.255
Mask:255.255.255.0
inet6 addr: fe80::200:e2ff:fe49:1aa9/64 Scope:Link
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)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2389 errors:0 dropped:0 overruns:0 frame:0
TX packets:2389 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2724120 (2.5 Mb) TX bytes:2724120 (2.5 Mb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
--------------------------------------------------
Command: /sbin/iptables -L

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
--------------------------------------------------------
Command: /sbin/route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
XX.YY.13.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 XX.YY.13.1 0.0.0.0 UG 0 0 0
eth0
--------------------------------------------------------
Command: cat /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=ShriRama
--------------------------------------------------------
Command: cat /etc/sysconfig/network

DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=XX.YY.13.88
NETMASK=255.255.255.0
GATEWAY=XX.YY.13.1
---------------------------------------------------------
Command: cat /etc/resolv.conf

nameserver XX.YY.10.1
------------------------------------------------------------
Command : /sbin/lsmod
Module Size Used by
iptable_filter 2048 0
ip_tables 13440 1 iptable_filter
parport_pc 19392 1
lp 8236 0
parport 29640 2 parport_pc,lp
autofs4 10624 0
sunrpc 101064 1
e100 25348 0
mii 3584 1 e100
floppy 47440 0
sg 27552 0
scsi_mod 91344 1 sg
microcode 4768 0
dm_mod 33184 0
joydev 6976 0
uhci_hcd 23708 0
button 4504 0
battery 6924 0
asus_acpi 8472 0
ac 3340 0
ipv6 184288 8
ext3 102376 3
jbd 40216 1 ext3


I could not find the following command : /sbin/ispci on my system.


Regards,
John

> eth0 Link encap:Ethernet HWaddr 00:00:E2:49:1A:A9
> inet addr:XX.YY.13.88 Bcast:XX.YY.13.255
> Mask:255.255.255.0
> inet6 addr: fe80::200:e2ff:fe49:1aa9/64 Scope:Link
> 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)

I dont't like the 0's here. At the very least, ping should have
generated some ARP packets.


> Command: /sbin/route -n
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> XX.YY.13.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 0.0.0.0 XX.YY.13.1 0.0.0.0 UG 0 0 0
> eth0

> Command: cat /etc/sysconfig/network
>
> NETWORKING=yes
> HOSTNAME=ShriRama
> --------------------------------------------------------
> Command: cat /etc/sysconfig/network
This is really network-scripts/ifcfg-eth0, right?
>
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=static
> IPADDR=XX.YY.13.88
> NETMASK=255.255.255.0
> GATEWAY=XX.YY.13.1

This all looks OK, so...

- are you sure the gateway is XX.YY.13.1? Given the values for XX and
YY, the 13 is unusual if this is a home network.
- are you sure the hardware is connected correctly? I know you said
things were working from Windows, but a rechecking is a Good Idea.
- are you sure the static IP address is OK?
- how are you hooked up to the network? Are all the appropriate
(green?) lights on?
- right now, the only thing you should be trying to ping is the gateway,
or maybe something else on XX.YY.13.

In article <(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

>Name Network Card: Inter Pro 100

Let's check that - I'm pretty sure you mean 'Intel', not Inter

>Command: cardctl ident
>no pcmcia driver in /proc/devices

That's saying it's not a PCMCIA card. Are you saying that it is?

>eth0 Link encap:Ethernet HWaddr 00:00:E2:49:1A:A9

[compton ~]$ etherwhois 00:00:E2
00-00-E2 (hex) ACER TECHNOLOGIES CORP.
0000E2 (base 16) ACER TECHNOLOGIES CORP.
401 CHARCOT AVE.
SAN JOSE CA 95131
[compton ~]$

This is saying that the hardware is from Acer, not Intel (though it
could be a re-branded or OEM version).

>Command: /sbin/iptables -L

OK

>Command: /sbin/route -n

OK - the 169.254.0.0 isn't needed (setting 'NOZEROCONF=yes' in the
/etc/sysconfig/network file would disable this "feature" but it has
no relevance to your current problem.

>Command: cat /etc/sysconfig/network
>
>NETWORKING=yes
>HOSTNAME=ShriRama

OK, but the hostname should be a full name (with 'dots' like
ShriRama.example.com), and there should be a corresponding entry in the
/etc/hosts file.

>Command: cat /etc/sysconfig/network
>
>DEVICE=eth0
>ONBOOT=yes
>BOOTPROTO=static
>IPADDR=XX.YY.13.88
>NETMASK=255.255.255.0
>GATEWAY=XX.YY.13.1

This is saying that the way to the Internet is through XX.YY.13.1. If that's
not the case, this entry should be empty.

>Command: cat /etc/resolv.conf
>
>nameserver XX.YY.10.1

OK. It would be desirable to have a second one listed, in case this one
goes pear shaped for some reason.

>Command : /sbin/lsmod

>e100 25348 0
>mii 3584 1 e100

OK - that's the Intel E100 driver, along with the mii module.

>I could not find the following command : /sbin/ispci on my system.

check the typo '/sbin/lspci' (in uppercase only to show '/SBIN/LSPCI')

What about the boot messages in /var/log/messages relating to this card?

Old guy

Hi,
The Output of lspci corresponding to my adapter is
01:08:0 Ethernet Controller: Intel Corp
82801 BA/BAM/CA/CAM Ethernet Controller (rev 01)


Hope this helps to identify my problem.



Regards,
John

In article <(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

> The Output of lspci corresponding to my adapter is
>01:08:0 Ethernet Controller: Intel Corp
>82801 BA/BAM/CA/CAM Ethernet Controller (rev 01)

OK, lots of hits on groups.google.com, but mainly for the (apparently)
later (rev 03) release. The card can use either Donald Becker's 'eepro100'
driver, or the Intel developed 'e100'. People seem to think the latter is
better.

>Hope this helps to identify my problem.

Well, it does, and it doesn't. Let's go back and look at the clues.

-------------------

]Date: 5 May 2005 02:13:35 -0700
]The Static IP is same for Windows and Linux.

_Probably_ not an address or mask problem

]Tx Packets and Rx Packets which are 0.

Bad sign - nothing using the card

]The driver is e100 it is loaded

As noted above, this _should_ be the correct driver.

]Date: 6 May 2005 06:02:09 -0700
]get Errror: Destination Host Unrechable.

This error occurs when you have the "correct" routing table, a driver is
loaded that is not incompatible with your card, and the kernel believes
that the card must be working. The specific cause of the error is that
the kernel networking code sent out several (probably 3) ARP (Address
Resolution Protocol) packets, but got no response back. Normally, this
would imply that the remote host was down, OR bad/incorrect cabling, OR
a bad card downstream of the computer bus interface (your windoze operating
basically rules these out). So, it's not to likely to be hardware.

]no pcmcia driver in /proc/devices

If my reading of google is correct, this is an built-in on-the-motherboard
interface - there shouldn't be anything in PCMCIA which is the small plug
in cards used in laptops. Completely different interface with the CPU.

]eth0 Link encap:Ethernet HWaddr 00:00:E2:49:1A:A9

Good news. The fact that you have a HWaddr means you can talk to the card,
and _probably_ you have the right driver. As noted in my response, this
hardware address is assigned to Acer Technologies.

] 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

Bad sign - no packets in or out. Good sign, no errors

]Command: /sbin/iptables -L

Good sign - firewall isn't in the way

]Command: /sbin/route -n

Doesn't look bad, but the 'Use' column is at zero.

]Command : /sbin/lsmod

]e100 25348 0
]mii 3584 1 e100

The driver and it's dependency is there.

-------------------

I don't see any reason for it not to be working. Your hardware is working
in windoze, and you state that the addresses/mask are the same. That rules
out a lot. The '82801 BA/BAM/CA/CAM' does indeed use the driver that you
have selected. You can talk to the card, and it's not giving errors, which
says that the driver seems to be working About the only thing I can think
of would be a speed mismatch - this is a 10/100 card. It's not likely to be
a half/full duplex problem, as this should show up as collisions in the
ifconfig output. See if your system has miitools or ethtool - the program
you are looking for is mii-diag

Other things to try: Try running '/usr/sbin/tcpdump -i eth0 -n' and then
do something with the network - ping another host, try to telnet - ANYTHING.
What do you see? You should see the card ARPing for the peer. Is there ANY
response?

You could also try using the eepro100 driver in place of the e100. This
change is probably effected by editing /etc/modules.conf.

I don't know if it would help, but it would be nice to see the messages
in /var/log/messages at boot time, when the kernel is setting up the card.
There should be four to six lines - look for 'eth0' or the hardware
address you noted earlier (00:00:E2:49:1A:A9).

Old guy

>> The Output of lspci corresponding to my adapter is
>>01:08:0 Ethernet Controller: Intel Corp
>>82801 BA/BAM/CA/CAM Ethernet Controller (rev 01)
FWIW, I have a machine with the same chipset:
02:08.0 Ethernet controller: Intel Corp.
82801BA/BAM/CA/CAM Ethernet Controller (rev 01)

only it's a Compaq:

> ]eth0 Link encap:Ethernet HWaddr 00:00:E2:49:1A:A9
> this hardware address is assigned to Acer Technologies.

eth0 Link encap:Ethernet HWaddr 00:02:A5:XX:XX:XX

It works fine with the e100 driver.

> ]e100 25348 0
> ]mii 3584 1 e100
> The driver and it's dependency is there.

The use count on e100 is zero. Either eth0 wasn't up, or there is a
second network card lurking somewhere.

> See if your system has miitools or ethtool - the program
> you are looking for is mii-diag

mii-tool on my system. FWIW, for this hardware:

$ ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: puag
Wake-on: g
Link detected: yes

$ mii-tool eth0
eth0: negotiated 100baseTx-FD flow-control, link ok


> I don't know if it would help, but it would be nice to see the messages
> in /var/log/messages at boot time, when the kernel is setting up the card.
> There should be four to six lines - look for 'eth0' or the hardware
> address you noted earlier (00:00:E2:49:1A:A9).

Look for both, and anything else that looks like a network card.

Have we seen /etc/modules.conf yet?