Destination Host Unreachable

[Phi]

I have a computer on a local network (192.168.1.0) that dual boots Win
XP and FC8. When I boot XP, I have full network functionality and
internet access. I am making this post from that boot.

When I boot FC8, I have no network or internet access. I can not even
reach the gateway router.

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.118 icmp_seq=1 Destination Host Unreachable
From 192.168.1.118 icmp_seq=2 Destination Host Unreachable
From 192.168.1.118 icmp_seq=5 Destination Host Unreachable
From 192.168.1.118 icmp_seq=6 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
7 packets transmitted, 0 received, +4 errors, 100% packet loss, time
5998ms
, pipe 2

My interface is up and appears to be working. I can ping the local
interface (127.0.0.1) and even the IP6 local interface.

The interface reports the following:

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1A:92:6B:ED:4B
inet addr:192.168.1.118 Bcast:192.168.1.255 Mask:
255.255.255.0
inet6 addr: fe80::21a:92ff:fe6b:ed4b/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:12755 (12.4 KiB)
Interrupt:22 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:1A:92:6B:F9:03
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:21 Base address:0x4000

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:5126 errors:0 dropped:0 overruns:0 frame:0
TX packets:5126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:259224 (253.1 KiB) TX bytes:259224 (253.1 KiB)

At the moment, eth1 is not active, or used, or needed.

The gateway seems to be available in the routing table.

route -v
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.1.0 * 255.255.255.0 U 0 0
0 eth0
link-local * 255.255.0.0 U 0 0
0 eth0
default 0.0.0.0 UG 0 0
0 eth0

netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
192.168.1.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
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0
0 eth0

(I don't know what the purpose of the link-local reference is, but FC8
put it in, so I left it.)

I have defined the gateway and another host on the system in /etc/
hosts.

cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 XENON localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

192.168.1.1
192.168.1.117 oxygen

I have not changed hosts.allow or hosts.deny.

I would appreciate any help on how I can fix this.

[Bit Twister]

On Sun, 2 Dec 2007 14:12:08 -0800 (PST), Phi wrote:
> I have a computer on a local network (192.168.1.0) that dual boots Win
> XP and FC8. When I boot XP, I have full network functionality and
> internet access. I am making this post from that boot.
>
> When I boot FC8, I have no network or internet access. I can not even
> reach the gateway router.
>

> ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:1A:92:6B:ED:4B
> inet addr:192.168.1.118 Bcast:192.168.1.255 Mask:
> 255.255.255.0
> inet6 addr: fe80::21a:92ff:fe6b:ed4b/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

But not packets RX/TX

>
> cat hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 XENON localhost.localdomain localhost
>::1 localhost6.localdomain6 localhost6
>
> 192.168.1.1

I would put at least a name there

192.168.1.1 gateway

-------- standard debug network problem text/script follows: ------------
dump_net.txt version 4.1

If you read http://www.catb.org/~esr/faqs/smart-questions.html
it will suggest you provide any information about your setup which might
help troubleshoot your problem. Example, Internet connection type,
(cable, adsl,,,), it's hardware, (vendor/model of the modem).
Maybe that your system is hooked to a hub/switch/router and type of
hookup, (Ethernet,usb, wireless,...), distribution, config file values,... .

We need to know about your network hardware and see your config settings.

Something does not start up, try
dmesg
and/or look through /var/log/messages for an error message.

If your problem is slow network give a URL so we can try it.

Once you get your network running, you may want to run xx one last time
and save the output file for disk crash/new installs :)

Might not hurt to save xx for one of a network debugging checklist steps.

The following ambidextrous script is for suse, mandriva, ubuntu, kubuntu
and will dump your hardware status, network settings and config files used
in network setup. We need that information to troubleshoot your problem.

If you are having to use windows to access Usenet:
Format a diskette on the windows system.

Copy the following xx.txt script into xx.txt using notepad.exe
then save xx.txt to the diskette/cd/usb stick.

To get the script results back to Windows and
none of the above hardware works, you can use http://www.fs-driver.org/

If you do not want some malware writing to linux. You can replace it
with http://www.diskinternals.com/linux-reader/ which does not
provide write access to linux.

The above assumes you have not created a FAT partition to exchange
files between OSs. If you did, copy dosa.txt to it from linux and read
it from windows.

I do recommend remove/installing the windows/linux file system
driver after you get the linux network up.

Makes your Windows Anti Virus scanner run much faster after removal.

Also, if logged into windows, it would be nice to include your windows
network settings. Click up a Prompt/cmd/terminal and add in contents from
ipconfig /all
when you reply with linux settings.

If using linux for Usenet access, su - root, copy script text into xx
chmod +x xx
./xx

and include a.txt (if on linux) or dosa.txt (if on windows) in your reply.

NOTE: to become root, you need to do a
su - root
not su root

For the suse, ubuntu, kubuntu users,
sudo -i
chmod +x xx
./xx

exit will exit the sudo -i command.

If xx is not in your home directory, you will have to provide the full
path in place of $HOME. Example:
sudo -i
chmod +x /some/where/xx
/some/where/xx

------------------ Script starts below this line ---------
#!/bin/bash
#*************************************************************
#*
#* xx - Dump network config files and network hardware status
#*
#* Output: a.txt linux file
#* dosa.txt Windows file
#*
#*************************************************************

_fn=a.txt
_out_fn=$PWD/$_fn
_dos_fn=$PWD/dos${_fn}
_home=$PWD

function cat_fn
{
_fn=$1
if [ -f $_fn ] ; then
_count=$(stat -c %s $_fn )
if [ $_count -gt 0 ] ; then
echo "======== cat $_fn ==========" >> $_out_fn
cat $_fn >> $_out_fn
fi
fi
} # end cat_fn

function grep_fn
{
_fn=$1
if [ -e $_fn ] ; then
_count=$(stat -c %s $_fn )
if [ $_count -gt 0 ] ; then
_count=$(grep -v '^#' $_fn | wc -l)
if [ $_count -gt 0 ] ; then
echo "======== grep -v '^#' $_fn ==========" >> $_out_fn
if [ "$_fn" != "shorewall.conf" ] ; then
grep -v '^#' $_fn >> $_out_fn
else
awk 'empty{if (!/^#/) print; empty=0} /^$/{empty=1}' $_fn >> $_out_fn
fi
fi
fi
fi
} # end grep_fn

function ls_dir
{
_dr=$1
if [ -d $_dr ] ; then
echo "========= cd $_dr ; ls -al ========" >> $_out_fn
cd $_dr
ls -al >> $_out_fn
fi
} # end ls_dir

function tail_fn
{
_fn=$1
if [ -e $_fn ] ; then
echo "======== tail -18 $_fn ==========" >> $_out_fn
tail -18 $_fn >> $_out_fn
fi
} # end tail_fn

#********************************
# check if commands are in $PATH
# and if not add them to PATH
#********************************

_path=""
type ifconfig > /dev/null 2>&1
if [ $? -ne 0 ] ; then
_path="${_path}/sbin:"
fi

type cat > /dev/null 2>&1
if [ $? -ne 0 ] ; then
_path="${_path}/bin:"
fi

type id > /dev/null 2>&1
if [ $? -ne 0 ] ; then
_path="${_path}/usr/bin:"
fi

if [ -n "$_path" ] ; then
PATH=${_path}$PATH
export PATH
fi

#********************************
# check if root and logged in correctly
#********************************

_uid=$(id --user)

if [ $_uid -ne 0 ] ; then
echo " "
echo "You need to be root to run $0"
echo "Click up a terminal and do the following:"
echo " "
echo "su - root"
echo "$PWD/xx"
echo " "
echo "or "
echo " "
echo "sudo -i"
echo "$PWD/xx"
echo " "
exit 1
fi

root_flg=1

if [ -n "$LOGNAME" ] ; then
if [ "$LOGNAME" != "root" ] ; then
root_flg=0
fi
fi

if [ -n "$USER" ] ; then
if [ "$USER" != "root" ] ; then
root_flg=0
fi
fi

if [ $root_flg -eq 0 ] ; then
echo " "
echo "Guessing you did a su root"
echo "instead of a su - root"
echo "please exit/logout of this session and do the following:"
echo " "
echo "su - root"
echo "$PWD/xx"
echo " "
echo "or "
echo " "
echo "sudo -i"
echo "$PWD/xx"
echo " "
exit 1
fi

#********************************
# main code starts here
#********************************

echo "Working, output will be in $_out_fn "

date > $_out_fn
chmod 666 $_out_fn

if [ -n "$_path" ] ; then
echo "======== echo $PATH ==========" >> $_out_fn
echo "$PATH" >> $_out_fn 2>&1
fi

cat_fn /etc/product.id

for _d in /etc/*release ; do
if [ ! -d $_d ] ; then
echo "======== cat $_d ==========" >> $_out_fn
cat $_d >> $_out_fn
fi
done

echo "======== uname -rvi =============" >> $_out_fn
uname -rvi >> $_out_fn

for _d in /etc/*version ; do
if [ ! -d $_d ] ; then
echo "======== cat $_d ==========" >> $_out_fn
cat $_d >> $_out_fn
fi
done

cat_fn /proc/*version

type lsb_release > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "======== lsb_release -a ==========" >> $_out_fn
lsb_release -a >> $_out_fn 2>&1
fi

echo " " >> $_out_fn
if [ -n "$SECURE_LEVEL" ] ; then
echo "msec security level is $SECURE_LEVEL" >> $_out_fn
fi

echo "
$(grep 'model name' /proc/cpuinfo)
$(grep 'cpu MHz' /proc/cpuinfo)

" >> $_out_fn

echo "======== free ==========" >> $_out_fn
free >> $_out_fn 2>&1
echo " " >> $_out_fn

if [ -e /etc/inittab ] ; then
_line=$(grep :initdefault /etc/inittab)
set -- $(IFS=':'; echo $_line)
echo " " >> $_out_fn
echo "Default run level is $2" >> $_out_fn
echo " " >> $_out_fn
fi

type chkconfig > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "======== chkconfig --list ==========" >> $_out_fn
for _serv in avahi named tmdns ; do
chkconfig --list | grep -i $_serv > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "Double check if /$_serv/ needs to be disabled on boot" >> $_out_fn
chkconfig --list | grep -i $_serv >> $_out_fn
fi
done

chkconfig --list >> $_out_fn

else
echo "======== ls -o /etc/rcS.d/ ==========" >> $_out_fn
for _serv in avahi named tmdns ; do
ls /etc/rcS.d/S* | grep $_serv > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "Double check if /$_serv/ needs to be disabled on boot" >> $_out_fn
fi
done

ls -o /etc/rcS.d >> $_out_fn
fi

_fn=/etc/nsswitch.conf
if [ -e $_fn ] ; then
echo "======== grep hosts: $_fn ==========" >> $_out_fn
grep hosts: $_fn >> $_out_fn
fi

grep_fn /etc/resolv.conf

grep_fn /etc/resolvconf/resolv.conf.d/head
cat_fn /etc/resolvconf/resolv.conf.d/base
cat_fn /etc/resolvconf/resolv.conf.d/tail

echo "======== hostname --fqdn ==========" >> $_out_fn
hostname --fqdn >> $_out_fn

cat_fn /etc/netprofile/profiles/default/files/etc/hosts
cat_fn /etc/hostname
cat_fn /etc/HOSTNAME

ls /etc/mod*.conf > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "======== grep eth /etc/mod*.conf ==========" >> $_out_fn
grep eth /etc/mod*.conf >> $_out_fn
fi

cat_fn /etc/dhclient-enter-hooks
cat_fn /etc/dhclient-exit-hooks

grep_fn /etc/host.conf

echo "================ ifconfig -a ==============" >> $_out_fn
ifconfig -a >> $_out_fn

cat_fn /etc/iftab
cat_fn /etc/udev/rules.d/61-net_config.rules

echo "============== route -n =================" >> $_out_fn
route -n >> $_out_fn

cat_fn /etc/sysconfig/network/routes

cat_fn /etc/sysconfig/network
grep_fn /etc/mkinitramfs/initramfs.conf

echo "========== head -15 /etc/hosts ===========" >> $_out_fn
head -15 /etc/hosts >> $_out_fn

cat_fn /etc/network/interfaces
cat_fn /var/run/network/ifstate

_cmd=""
type ethtool > /dev/null 2>&1
if [ $? -eq 0 ] ; then
_cmd="ethtool"
fi

type mii-tool > /dev/null 2>&1
if [ $? -eq 0 ] ; then
_cmd="mii-tool -v"
fi

if [ -z "$_cmd" ] ; then
echo "==== mii-tool/ethtool NOT INSTALLED ====" >> $_out_fn
fi

for nic in 0 1 2 ; do

if [ -n "$_cmd" ] ; then
$_cmd eth$nic > /dev/null 2>&1
if [ $? -eq 0 ] ; then
echo "======== $_cmd eth$nic ==========" >> $_out_fn
$_cmd eth$nic >> $_out_fn
fi
fi

echo "=== dmesg | grep eth$nic | grep -v SRC= ===" >> $_out_fn
dmesg | grep eth$nic | grep -v SRC= >> $_out_fn

echo "=== grep eth$nic /var/log/messages | tail -10 ===" >> $_out_fn
grep eth$nic /var/log/messages | tail -10 >> $_out_fn

cat_fn /etc/sysconfig/network-scripts/ifcfg-eth$nic
cat_fn /etc/sysconfig/networking/devices/ifcfg-eth$nic
cat_fn /etc/sysconfig/networking/profiles/default/ifcfg-eth$nic

ifconfig eth$nic > /dev/null 2>&1
if [ $? -eq 0 ] ; then
set $(ifconfig eth$nic | tr [A-Z] [a-z])
cat_fn /etc/sysconfig/network/ifcfg-eth-id-$5
fi

tail_fn /var/lib/dhcp/dhclient-eth${nic}.leases
tail_fn /var/lib/dhclient/dhclient-eth${nic}.leases
tail_fn /etc/dhcpc/dhcpcd-eth${nic}.info

done # end for nic in 0 1 2 ; do

_dir=/etc/NetworkManager/dispatcher.d
if [ -d $_dir ] ; then
ls_dir $_dir

for _d in "if-up.d" "if-down.d" "if-pre-up.d" "if-post-down.d" ; do
if [ -e /etc/network/${_d} ] ; then
echo "==== cd /etc/network/${_d} ; ls -al ===" >> $_out_fn
cd /etc/network/${_d}
ls -al >> $_out_fn
fi
done
fi

if [ -d /etc/sysconfig/network-scripts ] ; then
for _d in "ifdown.d" "ifup.d" ; do
if [ -e /etc/sysconfig/network-scripts/${_d} ] ; then
_cmd="cd /etc/sysconfig/network-scripts/${_d} ; ls -al "
echo "===== $_cmd ====" >> $_out_fn
cd /etc/sysconfig/network-scripts/${_d}
ls -al >> $_out_fn
fi
done
fi

ls_dir /etc/dhcp3/dhclient-exit-hooks.d
ls_dir /etc/resolvconf/update.d

if [ -d /etc/shorewall ] ; then
_count=$(chkconfig --list shorewall | grep -c :on )
if [ $_count -gt 0 ] ; then
echo "======= Shorewall settings =========" >> $_out_fn
cd /etc/shorewall
for _f in $(ls) ; do
echo "======= $_f =========" >> $_out_fn
grep_fn $_f
done
fi
fi

cd $_home

grep_fn /etc/hosts.allow
grep_fn /etc/hosts.deny
echo "==== end of config/network data dump =======" >> $_out_fn

awk '{print $0 "\r" }' $_out_fn > $_dos_fn
chmod 666 $_dos_fn

echo " "
echo "If posting via linux, post contents of $_out_fn"
echo "You might want to copy it to your account with the command"
echo "cp $_out_fn ~your_login"
echo " "
echo "If posting via windows, post contents of $_dos_fn"
echo " "
echo "If using diskette,"
echo "Copy $_dos_fn to diskette with the following commands:"
echo " "
echo "mkdir -p /floppy"
echo "mount -t auto /dev/fd0 /floppy"
echo "cp $_dos_fn /floppy"
echo "umount /floppy "
echo " "
echo "and $_dos_fn is ready for windows from diskette"
echo " "

#*********** end of dump xx.txt script *********

----------- script ends above this line ------------------------

and then copy xx.txt to the diskette.

On some linux distributions, you may need to get into the User/Group
screen, show all users, double click root, create the password, and
enable root. Root's password should never be the same as anyone else's.

To move xx.txt from diskette to the linux box, click up a linux terminal
su - root
(root's passwd)

mkdir -p /floppy
mount -t auto /dev/fd0 /floppy
tr -d '\015' < /floppy/xx.txt > xx
chmod +x xx
./xx

Back on the windows OS, you can cut/paste the a:\dosa.txt into your reply
under windows.
Do not attach it.

When you do reply, please remove/trim my response/text/script from your reply
before you add in the results/output of the script.

If you are dual booting the box, you can copy xx.txt to linux from windows.
Note: The following assumes /dev/hda1 is where windows is installed on the
first partition on the C: drive
If you have sata drive, you may have to use /dev/sda1 instead of /dev/hda1.

cat /etc/fstab to see which value will be required.
Do keep quotes used in the following:
mkdir -p /doze
mount -t auto /dev/hda1 /doze
tr -d '\015' < "/doze/wherever/you_saved/xx.txt" > xx
umount /doze

On windows you can read dosa.txt from a linux partition if you installed
windows linux file system driver from
http://uranus.it.swin.edu.au/~jn/linux/explore2fs.htm

Remember to remove/uninstall it to allow your Windows Anti Virus
scanner to run faster.

[david]

On Sun, 02 Dec 2007 14:12:08 -0800, Phi rearranged some electrons to say:

>
> route -v
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
> link-local * 255.255.0.0 U 0 0 0 eth0
> default 0.0.0.0 UG 0 0 0 eth0
>

Something seems wrong with the gateway on your default route.. it
shouldn't be blank, should it?

[Allen McIntosh]

Phi wrote:
> I have a computer on a local network (192.168.1.0) that dual boots Win
> XP and FC8. When I boot XP, I have full network functionality and
> internet access. I am making this post from that boot.
>
> When I boot FC8, I have no network or internet access. I can not even
> reach the gateway router.
>
> ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> From 192.168.1.118 icmp_seq=1 Destination Host Unreachable

> At the moment, eth1 is not active, or used, or needed.

My first reaction was "Did FC8 get eth0 and eth1 reversed?" BTDT
entirely too often.

[Phi]

Thank you for your comprehensive reply. I will try to give you the
information you requested.

The network is in a star configuration with a SonicWall router as the
hub connected to a cablemodem. All the computers connected to the
network are Windows based computers, in at least one boot
configuration. All the Windows computers can connect to each other,
and to the Internet.

This computer dual boots Windows XP and Linux Fedora Core 8. In the
Windows configuration, it has access to the network and to the
Internet. In the FC8 configuration, it has no access to the network,
or the Internet. Given that this computer can and does access the
network and the Internet, it is unlikely that the problem lies with
the network.

As you requested, I copied and ran the script you provided, and
obtained the results of ipconfig on the Windows boot. The results are
posted below.

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : xenon

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : TechTriad.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : TechTriad.local

Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller

Physical Address. . . . . . . . . : 00-1A-92-6B-ED-4B

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.118

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.2

DNS Servers . . . . . . . . . . . : 192.168.1.2

Primary WINS Server . . . . . . . : 192.168.1.2

Lease Obtained. . . . . . . . . . : Sunday, December 02, 2007
10:38:55 PM

Lease Expires . . . . . . . . . . : Monday, December 10, 2007
10:38:55 PM

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller #2

Physical Address. . . . . . . . . : 00-1A-92-6B-F9-03

Sun Dec 2 22:30:42 EST 2007
======== cat /etc/fedora-release ==========
Fedora release 8 (Werewolf)
======== cat /etc/redhat-release ==========
Fedora release 8 (Werewolf)
======== cat /etc/system-release ==========
Fedora release 8 (Werewolf)
======== uname -rvi =============
2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:18:33 EDT 2007 x86_64
======== cat /etc/*version ==========
======== lsb_release -a ==========
LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-
noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: Fedora
Description: Fedora release 8 (Werewolf)
Release: 8
Codename: Werewolf

model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
cpu MHz : 2399.970
cpu MHz : 2399.970

======== free ==========
total used free shared buffers
cached
Mem: 1027496 527928 499568 0 17500
174208
-/+ buffers/cache: 336220 691276
Swap: 2031608 0 2031608

Default run level is 5

======== chkconfig --list ==========
Double check if /avahi/ needs to be disabled on boot
avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ConsoleKit 0:off 1:off 2:on 3:on 4:on 5:on 6:off
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
NetworkManagerDispatcher 0:off 1:off 2:off 3:off 4:off 5:off 6:off
acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
autofs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
bluetooth 0:off 1:off 2:on 3:on 4:on 5:on 6:off
btseed 0:off 1:off 2:off 3:off 4:off 5:off 6:off
bttrack 0:off 1:off 2:off 3:off 4:off 5:off 6:off
capi 0:off 1:off 2:off 3:off 4:off 5:off 6:off
cpuspeed 0:off 1:on 2:on 3:on 4:on 5:on 6:off
crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off
dund 0:off 1:off 2:off 3:off 4:off 5:off 6:off
firstboot 0:off 1:off 2:off 3:on 4:off 5:on 6:off
gpm 0:off 1:off 2:on 3:on 4:on 5:off 6:off
haldaemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
irda 0:off 1:off 2:off 3:off 4:off 5:off 6:off
irqbalance 0:off 1:off 2:off 3:on 4:on 5:on 6:off
isdn 0:off 1:off 2:on 3:on 4:on 5:on 6:off
kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off
lm_sensors 0:off 1:off 2:off 3:off 4:off 5:off 6:off
mdmonitor 0:off 1:off 2:on 3:on 4:on 5:on 6:off
messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off
microcode_ctl 0:off 1:off 2:on 3:on 4:on 5:on 6:off
multipathd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
netplugd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
nscd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ntpd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
pand 0:off 1:off 2:off 3:off 4:off 5:off 6:off
pcscd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
psacct 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rdisc 0:off 1:off 2:off 3:off 4:off 5:off 6:off
restorecond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rpcbind 0:off 1:off 2:on 3:on 4:on 5:on 6:off
rpcgssd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
rpcidmapd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
rpcsvcgssd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rsyslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off
saslauthd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
sendmail 0:off 1:off 2:on 3:on 4:on 5:off 6:off
setroubleshoot 0:off 1:off 2:off 3:on 4:on 5:on 6:off
smartd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
smolt 0:off 1:off 2:off 3:off 4:off 5:off 6:off
sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
udev-post 0:off 1:off 2:off 3:on 4:on 5:on 6:off
winbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off
wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off
ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off
yum-updatesd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
======== grep hosts: /etc/nsswitch.conf ==========
#hosts: db files nisplus nis dns
hosts: files dns
======== grep -v '^#' /etc/resolv.conf ==========
nameserver 29.25.5.60
nameserver 29.25.5.61
======== hostname --fqdn ==========
XENON

======== grep eth /etc/mod*.conf ==========

alias eth0 forcedeth
alias eth1 forcedeth
======== grep -v '^#' /etc/host.conf ==========
order hosts,bind
================ ifconfig -a ==============

eth0 Link encap:Ethernet HWaddr 00:1A:92:6B:ED:4B
inet addr:192.168.1.118 Bcast:192.168.1.255 Mask:
255.255.255.0
inet6 addr: fe80::21a:92ff:fe6b:ed4b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:510 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:43923 (42.8 KiB)

Interrupt:22 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:1A:92:6B:F9:03
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:21 Base address:0x4000

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:4594 errors:0 dropped:0 overruns:0 frame:0
TX packets:4594 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:239914 (234.2 KiB) TX bytes:239914 (234.2 KiB)

============== route -n =================

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface

192.168.1.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
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0
0 eth0

======== cat /etc/sysconfig/network ==========
NETWORKING=yes
HOSTNAME=XENON

========== head -15 /etc/hosts ===========

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 XENON localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

192.168.1.1
192.168.1.117 oxygen

=== dmesg | grep eth0 | grep -v SRC= ===
eth0: forcedeth.c: subsystem: 01043:cb84 bound to 0000:00:11.0
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032
eth0: Ring at 3dac2000
eth0: Dumping tx registers
eth0: Dumping tx ring
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032
eth0: Ring at 3dac2000
eth0: Dumping tx registers
eth0: Dumping tx ring
=== grep eth0 /var/log/messages | tail -10 ===
Dec 2 22:18:51 XENON kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Dec 2 22:18:51 XENON kernel: eth0: Got tx_timeout. irq: 00000032
Dec 2 22:18:51 XENON kernel: eth0: Ring at 3dac2000
Dec 2 22:18:51 XENON kernel: eth0: Dumping tx registers
Dec 2 22:18:51 XENON kernel: eth0: Dumping tx ring
Dec 2 22:27:01 XENON kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Dec 2 22:27:01 XENON kernel: eth0: Got tx_timeout. irq: 00000032
Dec 2 22:27:01 XENON kernel: eth0: Ring at 3dac2000
Dec 2 22:27:01 XENON kernel: eth0: Dumping tx registers
Dec 2 22:27:01 XENON kernel: eth0: Dumping tx ring
======== cat /etc/sysconfig/network-scripts/ifcfg-eth0 ==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:1a:92:6b:ed:4b
ONBOOT=yes
DHCP_HOSTNAME=XENON
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
IPADDR=192.168.1.118
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
======== cat /etc/sysconfig/networking/devices/ifcfg-eth0 ==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:1a:92:6b:ed:4b
ONBOOT=yes
DHCP_HOSTNAME=XENON
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
IPADDR=192.168.1.118
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
======== cat /etc/sysconfig/networking/profiles/default/ifcfg-eth0
==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:1a:92:6b:ed:4b
ONBOOT=yes
DHCP_HOSTNAME=XENON
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
IPADDR=192.168.1.118
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
======== tail -18 /var/lib/dhclient/dhclient-eth0.leases ==========
=== dmesg | grep eth1 | grep -v SRC= ===
eth1: forcedeth.c: subsystem: 01043:cb84 bound to 0000:00:12.0
=== grep eth1 /var/log/messages | tail -10 ===
Dec 1 17:37:20 XENON system-config-network[3618]: -+ //etc/
modprobe.conf #011eth1 alias forcedeth
Dec 1 17:37:20 XENON system-config-network[3618]: chmod 0644 //etc/
sysconfig/networking/devices/ifcfg-eth1
Dec 1 17:37:30 XENON system-config-network[3618]: -+ //etc/
modprobe.conf #011eth1 alias forcedeth
Dec 1 17:37:30 XENON system-config-network[3618]: chmod 0644 //etc/
sysconfig/networking/devices/ifcfg-eth1
Dec 1 17:39:09 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
Dec 2 01:43:37 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
Dec 2 14:19:57 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
Dec 2 16:06:24 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
Dec 2 21:07:36 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
Dec 2 22:12:26 XENON kernel: eth1: forcedeth.c: subsystem: 01043:cb84
bound to 0000:00:12.0
======== cat /etc/sysconfig/network-scripts/ifcfg-eth1 ==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet
======== cat /etc/sysconfig/networking/devices/ifcfg-eth1 ==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet
======== cat /etc/sysconfig/networking/profiles/default/ifcfg-eth1
==========
# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet
=== dmesg | grep eth2 | grep -v SRC= ===
=== grep eth2 /var/log/messages | tail -10 ===
========= cd /etc/NetworkManager/dispatcher.d ; ls -al ========
total 16
drwxr-xr-x 2 root root 4096 2007-10-27 01:23 .
drwxr-xr-x 4 root root 4096 2007-10-27 01:23 ..

==== end of config/network data dump =======

Again, thank you for your help.

[Bit Twister]

On Sun, 2 Dec 2007 19:55:29 -0800 (PST), Phi wrote:
> ======== lsb_release -a ==========
> LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-

Guessing a 64 bit install, not a 32 bit install

> ======== chkconfig --list ==========

> avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off

Disable the avahi-daemon from booting. You do not need it running.
The command to do so is:

chkconfig --del avahi-daemon

> ======== hostname --fqdn ==========
> XENON

Some daemon/services like a FQDN or they will not run, more about that later.

> ================ ifconfig -a ==============
> eth0 Link encap:Ethernet HWaddr 00:1A:92:6B:ED:4B
> inet addr:192.168.1.118 Bcast:192.168.1.255 Mask:
> 255.255.255.0
> inet6 addr: fe80::21a:92ff:fe6b:ed4b/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:510 errors:0 dropped:0 overruns:0 carrier:0

At least you have some TX packets this time.

> ======== cat /etc/sysconfig/network ==========
> NETWORKING=yes
> HOSTNAME=XENON

Here is where I suggest giving your node a Fully Qualified Domain Name
(FQDN). I would make it HOSTNAME=xenon.mylan.invalid

Not part of you problem but can help later. Your webserver, Mail
Transport Agent (postfix), print daemon (cups), usenet reader
(tin).... need a FQDN.

You can change .mylan to whatever you like, do leave the .invalid.

> ========== head -15 /etc/hosts ===========
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 XENON localhost.localdomain localhost
>::1 localhost6.localdomain6 localhost6
>
> 192.168.1.1
> 192.168.1.117 oxygen

I see you did not take/make my recommendation. :(
Change /etc/hosts to look as follows:

# Do not remove the following line, or various programs
# that require network functionality will fail.

127.0.0.1 xenon.mylan.invalid xenon localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

192.168.1.1 gateway
192.168.1.117 oxygen

Dang it, for some reason, the command
mii-tool -v eth0
or ethtool eth0

did not run. No idea why. but may indicate module to drive nic
is not working and is the problem. Do try both commands to see if you
get any indication why they did not work.

> ======== cat /etc/sysconfig/network-scripts/ifcfg-eth0 ==========

> IPADDR=192.168.1.118

Just for fun, I would try changing ip address to 192.168.1.130
using the gui network configuration tool.

I am not sure if upline device will talk to 192.168.1.118 if Windows
did not release the dhcp lease.

I am at a loss to see where else the problem may be.

I do know, Micro$not did an update to my onboard Realtek Semiconductor
RTL-8139 nic and linux was no longer able to use the nic.

I wiped windows partition, reinstalled XP Home, did all updates minus
the network driver update, and linux was able to use the nic.

Of course, I had installed a LinkSys nic until I figured out what happened.

[Phi]

Thank you for your response. I checked the script you sent, and it
appeared to include the ethtool commands. I extracted that section and
simplified it so that it generated the following file.

Some of the information on the web indicates that there have been
problems with forcedeth. Is there any way to check the forcedeth
driver to see if it is working?

Again, thank you for your help.

start processing
Note: ethtool works, mii-tool does not
======== ethtool eth0 ==========
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 19
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes

=== dmesg | grep eth0 | grep -v SRC= ===
eth0: forcedeth.c: subsystem: 01043:cb84 bound to 0000:00:11.0
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032

eth0: Ring at 3d540000

eth0: Dumping tx registers
eth0: Dumping tx ring
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032

eth0: Ring at 3d540000

eth0: Dumping tx registers
eth0: Dumping tx ring
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032

eth0: Ring at 3d540000

eth0: Dumping tx registers
eth0: Dumping tx ring
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032

eth0: Ring at 3d540000

eth0: Dumping tx registers
eth0: Dumping tx ring
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Got tx_timeout. irq: 00000032

eth0: Ring at 3d540000

eth0: Dumping tx registers
eth0: Dumping tx ring
=== grep eth0 /var/log/messages | tail -10 ===

cat: /etc/sysconfig/network/ifcfg-eth-id-00:1a:92:6b:ed:4b: Not a
directory
tail: cannot open `/var/lib/dhcp/dhclient-eth0.leases' for reading: No
such file or directory
tail: cannot open `/etc/dhcpc/dhcpcd-eth0.info' for reading: No such
file or directory
======== ethtool eth1 ==========
Settings for eth1:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: MII
PHYAD: 19
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: no

=== dmesg | grep eth1 | grep -v SRC= ===
eth1: forcedeth.c: subsystem: 01043:cb84 bound to 0000:00:12.0
=== grep eth1 /var/log/messages | tail -10 ===

# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet
# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet
# nVidia Corporation MCP55 Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1A:92:6B:F9:03
ONBOOT=no
DHCP_HOSTNAME=XENON
TYPE=Ethernet

cat: /etc/sysconfig/network/ifcfg-eth-id-00:1a:92:6b:f9:03: Not a
directory
tail: cannot open `/var/lib/dhcp/dhclient-eth1.leases' for reading: No
such file or directory
tail: cannot open `/var/lib/dhclient/dhclient-eth1.leases' for
reading: No such file or directory
tail: cannot open `/etc/dhcpc/dhcpcd-eth1.info' for reading: No such
file or directory
======== ethtool eth2 ==========
Settings for eth2:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

=== dmesg | grep eth2 | grep -v SRC= ===
=== grep eth2 /var/log/messages | tail -10 ===

cat: /etc/sysconfig/network-scripts/ifcfg-eth2: No such file or
directory
cat: /etc/sysconfig/networking/devices/ifcfg-eth2: No such file or
directory
cat: /etc/sysconfig/networking/profiles/default/ifcfg-eth2: No such
file or directory
eth2: error fetching interface information: Device not found
eth2: error fetching interface information: Device not found
BASH=/bin/bash
BASH_ARGC=()
BASH_ARGV=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="./ethtool.txt")
BASH_VERSINFO=([0]="3" [1]="2" [2]="25" [3]="1" [4]="release" [5]="x86_64-
redhat-linux-gnu")
BASH_VERSION='3.2.25(1)-release'
COLORTERM=gnome-terminal
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-
pr4FJfyLBa,guid=7f44c6c6c92910ebacf399004754775a
DESKTOP_SESSION=default
DESKTOP_STARTUP_ID=
DIRSTACK=()
DISPLAY=:0.0
EUID=0
GDMSESSION=default
GDM_LANG=en_US.UTF-8
GDM_XSERVER_LOCATION=local
GNOME_DESKTOP_SESSION_ID=Default
GNOME_KEYRING_PID=2655
GNOME_KEYRING_SOCKET=/tmp/keyring-U89zhf/socket
GROUPS=()
GTK_MODULES=gnomebreakpad
GTK_RC_FILES=/etc/gtk/gtkrc:/root/.gtkrc-1.2-gnome2
G_BROKEN_FILENAMES=1
HISTSIZE=1000
HOME=/root
HOSTNAME=XENON
HOSTTYPE=x86_64
IFS=$' \t\n'
INPUTRC=/etc/inputrc
LANG=en_US.UTF-8
LESSOPEN='|/usr/bin/lesspipe.sh %s'
LOGNAME=root
LS_COLORS='no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:'
MACHTYPE=x86_64-redhat-linux-gnu
MAIL=/var/spool/mail/root
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/
bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
PIPESTATUS=([0]="1")
PPID=3651
PS4='+ '
PWD=/temp
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2656,unix/unix:/tmp/.ICE-
unix/2656
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=3
SSH_AGENT_PID=2706
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SSH_AUTH_SOCK=/tmp/ssh-geCodI2656/agent.2656
TERM=xterm
UID=0
USER=root
WINDOWID=52446567
WINDOWPATH=7
XAUTHORITY=/tmp/.gdmY1I62T
XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/usr/share/gdm/
XDG_SESSION_COOKIE=9667b29d748022a6a59a6e0047504e00-1196717913.715928-1405831146
_=eth2
nic=2
cat: /etc/sysconfig/network/ifcfg-eth-id-00:1a:92:6b:f9:03: Not a
directory
tail: cannot open `/var/lib/dhcp/dhclient-eth2.leases' for reading: No
such file or directory
tail: cannot open `/var/lib/dhclient/dhclient-eth2.leases' for
reading: No such file or directory
tail: cannot open `/etc/dhcpc/dhcpcd-eth2.info' for reading: No such
file or directory

[Moe Trin]

On Mon, 3 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <slrnfl7367.t...@wb.home.invalid>, Bit Twister wrote:

>Phi wrote:

>> eth0 Link encap:Ethernet HWaddr 00:1A:92:6B:ED:4B

>Dang it, for some reason, the command

> mii-tool -v eth0
>or ethtool eth
>

>did not run. No idea why. but may indicate module to drive nic
>is not working and is the problem. Do try both commands to see if you
>get any indication why they did not work.

[compton ~]$ etherwhois 00:1A:92
00-1A-92 (hex) ASUSTek COMPUTER INC.
001A92 (base 16) ASUSTek COMPUTER INC.
No.5 Shing Yeh Street,Kwei Shan Haiang,Tao Yuan
Taipei 333
TAIWAN, REPUBLIC OF CHINA
[compton ~]$

No indication of what type of card, but at least the kernel can talk to
it. Two possibilities - card doesn't support Mii-tools, or the desired
binaries aren't installed.

>I do know, Micro$not did an update to my onboard Realtek Semiconductor
>RTL-8139 nic and linux was no longer able to use the nic.

How long ago? Early in the life of the 8139 driver, there was a problem
with the power management. From a long forgotten post to c.o.l.n:

---------------------------------
>So once again I booted up the machine in Windows (98 SE) and then
>rebooted into Linux again and ... the hardware adress was once again 0.
>Shutting down the power and the booting up in Linux again gives the card
>the right address again.

This can be solved by using the 'pci-scan' module and updated driver
from
http://www.scyld.com/network/updates.html

You have a RTL8139B or RTL8139C with PCI power management.
Windows leaves PCI power management capable devices in D3-warm power
state. Neither the BIOS nor Linux knows about PCI power management.
The 'pci-scan' module, combined with the updated driver set, knows how
to restore the device to full power "D0" state before using it.
bec...@beta.scyld.com (Donald Becker)
---------------------------------

Old guy

[Bit Twister]

On Mon, 3 Dec 2007 14:55:23 -0800 (PST), Phi wrote:

> Some of the information on the web indicates that there have been
> problems with forcedeth. Is there any way to check the forcedeth
> driver to see if it is working?

I would guess
ping -c 1 192.168.1.118

can you ping any other box, say 192.168.1.117

> Note: ethtool works, mii-tool does not

You can remove the mii-tool if statement then.

> ======== ethtool eth0 ==========
> Settings for eth0:

> Speed: 100Mb/s
> Duplex: Full
> Link detected: yes

There is what I was after. ehtool seems to indicate nothing wrong
as far as the card goes under linux.

> IPADDR=192.168.1.118

Looks like you did not take my suggestion to change ip address to
192.168.1.130

[Bit Twister]

On Mon, 03 Dec 2007 19:06:29 -0600, Moe Trin wrote:
>
>>I do know, Micro$not did an update to my onboard Realtek Semiconductor
>>RTL-8139 nic and linux was no longer able to use the nic.
>
> How long ago? Early in the life of the 8139 driver, there was a problem
> with the power management. From a long forgotten post to c.o.l.n:

Guessing September or October 2008. I even powered off the system.
Did not think to remove power cord.

Does pinging the card's ip address test the RX/TX chips/code?

[Pascal Hambourg]

Hello,

Bit Twister a écrit :

> On Mon, 03 Dec 2007 19:06:29 -0600, Moe Trin wrote:
>>
>>How long ago? Early in the life of the 8139 driver, there was a problem
>>with the power management. From a long forgotten post to c.o.l.n:
>
>
>
> Guessing September or October 2008.

2008 ?

> Does pinging the card's ip address test the RX/TX chips/code?

No, it tests the loopback interface lo.

[Bit Twister]

On Tue, 04 Dec 2007 09:47:58 +0100, Pascal Hambourg wrote:
>>
>> Guessing September or October 2008.
>
> 2008 ?

Hahaha, should be 2007. Mandriva release level is 2008.0 and I get
used to typing it so much I cannot keep my year straight. :(

>> Does pinging the card's ip address test the RX/TX chips/code?
>
> No, it tests the loopback interface lo.

Frap, I knew pinging localhost tested loopback, and was hopping ip
addy would check TX/RX without having to use another machine.

Thank you.

[goarilla]

he's right do this (as root):
/sbin/route del default
/sbin/route add default gw 192.168.1.1 netmask 255.255.255.0
<eth_device( eg eth0,eth1,...)>

[Moe Trin]

On Tue, 4 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <slrnfl9akg.f...@wb.home.invalid>, Bit Twister wrote:

>>>>I do know, Micro$not did an update to my onboard Realtek Semiconductor
>>>RTL-8139 nic and linux was no longer able to use the nic.
>>
>> How long ago? Early in the life of the 8139 driver, there was a problem
>> with the power management. From a long forgotten post to c.o.l.n:
>
>Guessing September or October 2008. I even powered off the system.
>Did not think to remove power cord.

Ack on the typo - this problem should have been solved in the current
kernel driver. Becker hasn't posted here in several years.

>Does pinging the card's ip address test the RX/TX chips/code?

The kernel looks to see if the address belongs "here". It will belong
if there wasn't a failure in bringing up the card, but the card itself
might be a charred ruin and things will still work. The transmit and
receive buffers on the card are not "connected" to each other in the
same manner as the (single) buffer on the loopback interface, so there
is no useful purpose in trying to send stuff there if it's not going
out onto the wire.

Old guy`

[Moe Trin]

On Tue, 04 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <47556a3f$0$29252$ba62...@news.skynet.be>, goarilla wrote:

>david wrote:

>> Phi rearranged some electrons to say:

>> route -v
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref Use Iface
>> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>> link-local * 255.255.0.0 U 0 0 0 eth0
>> default 0.0.0.0 UG 0 0 0 eth0
>>
> Something seems wrong with the gateway on your default route.. it
> shouldn't be blank, should it?
>
>he's right do this (as root):
>/sbin/route del default
>/sbin/route add default gw 192.168.1.1 netmask 255.255.255.0

^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
<eth_device( eg eth0,eth1,...)>

Ummmm.... you realy need to re-read that man page, usless this is one
hell of a typ0. The "default" route is defined in the terms of a
programming choice. If the other choices don't work to get you where you
are going, send it here _by default_ (which in the Linux tools sense
really means this is the route to the entire world). Last time I checked,
the world doesn't exist in a 255.255.255.0 mask, and the correct mask is
the default for a default route - which is to say 0.0.0.0.

Old guy

[Phi]

On Dec 4, 9:54 am, goarilla <"kevin DOT paulus AT skynet DOT be">
wrote:

Thank you.

My understanding of route -v is that it responds using symbolic names
for the hosts it finds. So, it shows link-local as a host. Since the
gateway has no symbolic name, it shows as a blank.

I also posted netstat -rn. That shows the IP addresses for the
connections. It shows 192.168.1.1 for the gateway address.

I think your advice is good advice, but I suspect it is not applicable
here. If I have misunderstood something, please let me know.

[Phi]

This computer used to run FC7 successfully, with full network access.
I ran into a problem when I got a second monitor and screwed things up
badly. So, I decided to install FC8 when it became available.

I just installed FC8 (64 bit version for Intel Core 2 duo) from a DVD
I created from downloading. Now, I can't get on the network.

I am reasonably certain that it is not a hardware problem, since the
computer works fine in WinXP and it used to work in FC7. There's a
software glitch here somewhere, and I don't know how to diagnose it.

I have received really good advice from this group and I appreciate it
greatly. I'd like not to go back, but it may be easier to reload FC7
or Ubuntu than to continue with this. I am about at the point where I
kiss off linux and recapture that disk space for other things.

That says more about me than linux.

[goarilla]

mmm yes you're right
i sometimes confuse syntax of ifconfig,ip,route :S

[david]

On Wed, 05 Dec 2007 09:27:17 -0800, Phi rearranged some electrons to say:

When you configured the network during the install, what entries did
you use for default gateway, DNS, etc. ?

[Phi]

Thank you for your help.

The gateway is 192.168.1.1
It did not show in route -v, because there is no symbolic name for it.
It does show correctly for netstat -rn.
DNS was entered as shown in resolv

======== grep -v '^#' /etc/resolv.conf ==========
nameserver 29.25.5.60
nameserver 29.25.5.61

Using nameserves outside the local network is normal. I may set up the
linux system to do dns for itself for nodes on the local network.

Of course, it's all moot if I can not access the local network.

[Moe Trin]

On Wed, 5 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <ffc2d0d7-aeb9-4832...@e67g2000hsc.googlegroups.com>,
Phi wrote:

NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.

>My understanding of route -v is that it responds using symbolic names
>for the hosts it finds.

Have you looked at the man page? It's fairly well explained there.

[compton ~]$ whatis route
route (8) - show / manipulate the IP routing table
[compton ~]$

>So, it shows link-local as a host. Since the gateway has no symbolic
>name, it shows as a blank.

No on both counts. Let's recopy your display here:

]route -v

]Kernel IP routing table
]Destination Gateway Genmask Flags Metric Ref Use Iface
]192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
]link-local * 255.255.0.0 U 0 0 0 eth0
]default 0.0.0.0 UG 0 0 0 eth0

The names 'link-local' and 'default' translate to a network named
'link-local' (169.254.0.0/16), and a route to use when no other route
will take your packets where they need to go. The 'link-local' is an
Apple invention copied by windoze, and used when a computer can't find
a DHCP server to get a "real" address. It gets included in some Linux
distributions because of the abundance of mis-configured windoze systems
often found on home networks. It's a "don't bother fixing the problem,
just make it work and I don't care about security" solution from windoze.
You can disable this "feature" by including a line in the file
'/etc/sysconfig/network' that says "NOZEROCONF=yes".

The 'default' route is that route used when no other listed route will
take you where you want to go. This is _NORMALLY_ considered to be the
route to "the world". The lack of a name or the '*' character indicates
that '/sbin/route' is finding some name for that gateway device, but is
unable to display the name - generally a screwed up nameserver, or bad
entry in the /etc/hosts file.

Note that none of the routes you show are routes to individual hosts.
These would be identified by a 'Genmask' of '255.255.255.255' and an
'H' flag. I'm not exactly sure where you got this routing table, as
it has several problems. This _should_ look like this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0

127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

Finally, when the 'route' command is unable to determine a name for
a host or network, it puts in the numeric address. You could use the
-n option to get this behavior by default.

>I also posted netstat -rn. That shows the IP addresses for the
>connections. It shows 192.168.1.1 for the gateway address.

[compton ~]$ whatis netstat
netstat (8) - Display network connections, routing tables,
interface statistics, masquerade connections and netlink messages
[compton ~]$

If you looked at the man page for 'netstat' (actual syntax 'man netstat')
you would find

-r, --route
With the -r, --route option, you get the kernel routing tables in
the same format as route -e use. netstat -er will use the output
format of route. Please see route(8) for details.

-n, --numeric
shows numerical addresses instead of trying to determine symbolic
host, port or user names.

so the data shown by '/bin/netstat -rn' should be essentially the same
as shown by '/sbin/route -n'

Old guy

[Moe Trin]

On Wed, 5 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in

article <02b637cb-ed2f-45a6...@a35g2000prf.googlegroups.com>,
Phi wrote:

NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.

>The gateway is 192.168.1.1

>It did not show in route -v, because there is no symbolic name for it.

Not true, but you could fix that by entering the hostname and address
in /etc/hosts. What does 'route -vn' show?

>It does show correctly for netstat -rn.
>DNS was entered as shown in resolv
>======== grep -v '^#' /etc/resolv.conf ==========
>nameserver 29.25.5.60
>nameserver 29.25.5.61
>Using nameserves outside the local network is normal.

Generally, it's frowned upon to try to use nameservers other than your
own, or those of your ISP. External users asking a name server to resolve
names/addresses it's not authoratative for is considered abuse by some,
and I've know people to configure their nameserver to respond with an
NXDOMAIN rather than the more correct REFUSED result code.

>I may set up the linux system to do dns for itself for nodes on the
>local network.

The addresses you show certainly won't work from here - my routers tell
me that no one admits to knowing how to send packets to that military
network. As you are posting from

NNTP-Posting-Host: 70.60.226.186

maybe you'd have better luck using one of the name servers associated
with Road Runner Commercial (24.30.200.19, 24.30.201.19, or 65.24.0.172),
or one associated with the techtriad.com (there are five to choose from).

Old guy

[Unruh]

ibup...@painkiller.example.tld (Moe Trin) writes:

>On Tue, 04 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
>article <47556a3f$0$29252$ba62...@news.skynet.be>, goarilla wrote:

>>david wrote:

>>> Phi rearranged some electrons to say:

>>> route -v
>>> Kernel IP routing table
>>> Destination Gateway Genmask Flags Metric Ref Use Iface
>>> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>>> link-local * 255.255.0.0 U 0 0 0 eth0
>>> default 0.0.0.0 UG 0 0 0 eth0
>>>
>> Something seems wrong with the gateway on your default route.. it
>> shouldn't be blank, should it?

Nope, it is fine, assuming that any of the machines that he wants to reach
are on his local ethernet so the arp table can get to them.
If that assumption is not true, then yes, he needs a gateway host which
knows how to send on the packets.

>>
>>he's right do this (as root):
>>/sbin/route del default
>>/sbin/route add default gw 192.168.1.1 netmask 255.255.255.0
> ^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^

Why in the world would you want a netmask other than 0.0.0.0 on the
default. Yours says that the ONLY addresses to be sent to the gateway have
the IP addresses of 0.0.0.x where x is any 8 bit number. I do not think
that is what you want. YOu want
netmask 0.0.0.0 but then that is the default with default.

><eth_device( eg eth0,eth1,...)>

>Ummmm.... you realy need to re-read that man page, usless this is one
>hell of a typ0. The "default" route is defined in the terms of a
>programming choice. If the other choices don't work to get you where you
>are going, send it here _by default_ (which in the Linux tools sense
>really means this is the route to the entire world). Last time I checked,
>the world doesn't exist in a 255.255.255.0 mask, and the correct mask is
>the default for a default route - which is to say 0.0.0.0.

Are there any valid IP addresses of the form 0.0.0.x?

> Old guy

[david]

On Fri, 07 Dec 2007 04:58:17 +0000, Unruh rearranged some electrons to
say:

> ibup...@painkiller.example.tld (Moe Trin) writes:
>
>>On Tue, 04 Dec 2007, in the Usenet newsgroup comp.os.linux.networking,
>>in article <47556a3f$0$29252$ba62...@news.skynet.be>, goarilla wrote:
>
>>>david wrote:
>
>>>> Phi rearranged some electrons to say:
>
>>>> route -v
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric Ref Use
>>>> Iface 192.168.1.0 * 255.255.255.0 U 0 0
>>>> 0 eth0 link-local * 255.255.0.0 U 0 0
>>>> 0 eth0 default 0.0.0.0 UG 0 0
>>>> 0 eth0
>>>>
>>> Something seems wrong with the gateway on your default route.. it
>>> shouldn't be blank, should it?
>
> Nope, it is fine, assuming that any of the machines that he wants to
> reach are on his local ethernet so the arp table can get to them. If
> that assumption is not true, then yes, he needs a gateway host which
> knows how to send on the packets.

The OP said he could not ping his router, nor access the outside world:

[Moe Trin]

On Fri, 07 Dec 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <Jp46j.41370$Zn.37189@edtnps90>, Unruh wrote:

>(Moe Trin) writes:

>> goarilla wrote:

>>> david wrote:

>>>> Phi rearranged some electrons to say:

>>>> route -v
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric Ref Use Iface
>>>> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>>>> link-local * 255.255.0.0 U 0 0 0 eth0
>>>> default 0.0.0.0 UG 0 0 0 eth0
>>>>
>>> Something seems wrong with the gateway on your default route.. it
>>> shouldn't be blank, should it?

>Nope, it is fine, assuming that any of the machines that he wants to
>reach are on his local ethernet so the arp table can get to them.

Bill, please read the original posts before making wild assumptions.
First, notice that the two other entries on this output show a '*' for
the gateway, and the default route does not. As the O/P is not using
the -n option to /sbin/route, the command will try to display the
hostname if it can determine it. IT IS DOING SO HERE, except that the
name it's trying to display is screwed up - either a bunch of leading
spaces in the name, or non-ASCII characters. IF THERE WAS NO GATEWAY,
THE COMMAND WOULD DISPLAY A '*' IN THAT FIELD. A further clue is
that the O/P also included the output of '/bin/netstat -nr' which,
because of the -n option, is displaying the dotted quad IP address.

>>>he's right do this (as root):
>>>/sbin/route del default
>>>/sbin/route add default gw 192.168.1.1 netmask 255.255.255.0
> ^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
>Why in the world would you want a netmask other than 0.0.0.0 on the
>default.

If you read the rest of the thread, this poster admitted his mistake.

>Are there any valid IP addresses of the form 0.0.0.x?

Yes. See RFC1122 section 3.2.1.3 which discusses RFC0791 section 3.2.
Briefly, 0,0 (network address 0 and within that network, host address
0) means "this" host - where I don't know my address. It's generally
seen in the start of DHCP/BOOTP conversations. The 0, host-id address
(network part zeroed, host part specific to some host) is also allowed.
However, routers should not forward these packets except in specific
special circumstances (one example being a DHCP relay agent).

Old guy

[Phi]

Thanks to all who tried to help me with this problem. Unfortunately,
nothing suggested worked.

I reinstalled FC8 in the 32-bit version. That didn't work either.

I reinstalled FC7 and that worked without effort.

I guess I'll just wait for FC9.