network problem (can't ping myself) - newb

Hi
I have a home network - netgear router, one wired PC, two wireless. All
connected to the internet via the router.
Just installed FC4 on the wired PC to run as dual boot with XP.
Everything seems OK, but, can't access the network.
On boot up eth0 is successfully assigned the IP address 192.168.0.2 as
expected by DHCP on the router and reports as active. However, I can't
ping anything (except the loopback).
Apologies if this has been asked many times. I am a Linux newbie - I did
search the newsgroup and elsewhere for a solution, but I couldn't find
anything which exactly matched my problem. I did find lots of similar
ones, but nothing I tried from them seemed to help. I suspect that it
is a combination of things that I need to do to get it working,
surprised that it doesn't sort itself out when it can successfully get
the IP address on bootup.
Many thanks in advance to anyone who can help.

George

GRM wrote:
> Hi
> I have a home network - netgear router, one wired PC, two wireless. All
> connected to the internet via the router.
> Just installed FC4 on the wired PC to run as dual boot with XP.
> Everything seems OK, but, can't access the network.
> On boot up eth0 is successfully assigned the IP address 192.168.0.2 as
> expected by DHCP on the router and reports as active. However, I can't
> ping anything (except the loopback).
> Apologies if this has been asked many times. I am a Linux newbie - I did
> search the newsgroup and elsewhere for a solution, but I couldn't find
> anything which exactly matched my problem. I did find lots of similar
> ones, but nothing I tried from them seemed to help. I suspect that it
> is a combination of things that I need to do to get it working,
> surprised that it doesn't sort itself out when it can successfully get
> the IP address on bootup.
> Many thanks in advance to anyone who can help.
>
> George
>

It probably isn't getting a default gateway or DNS information. It
SHOULD get those at the same time and in the same way as the IP address.
Check your settings in the Network Configuration gui.

Rod

Randomthots wrote:

> GRM wrote:
> > Hi
> > I have a home network - netgear router, one wired PC, two wireless. All
> > connected to the internet via the router.
> > Just installed FC4 on the wired PC to run as dual boot with XP.
> > Everything seems OK, but, can't access the network.
> > On boot up eth0 is successfully assigned the IP address 192.168.0.2 as
> > expected by DHCP on the router and reports as active. However, I can't
> > ping anything (except the loopback).
> > Apologies if this has been asked many times. I am a Linux newbie - I did
> > search the newsgroup and elsewhere for a solution, but I couldn't find
> > anything which exactly matched my problem. I did find lots of similar
> > ones, but nothing I tried from them seemed to help. I suspect that it
> > is a combination of things that I need to do to get it working,
> > surprised that it doesn't sort itself out when it can successfully get
> > the IP address on bootup.
> > Many thanks in advance to anyone who can help.
> >
> > George
> >
>
> It probably isn't getting a default gateway or DNS information. It
> SHOULD get those at the same time and in the same way as the IP address.
> Check your settings in the Network Configuration gui.
>
> Rod

Thanks Rod,

The DNS settings seem OK, but the default gateway is not being set (I don't
think). I'll try setting it manually again (it didn't seem to have any effect
- after the manual change should I just deactivate and then reactivate eth0,
or do I need to do more?

George

On Fri, 21 Oct 2005 08:49:18 +0100, GRM wrote:

> The DNS settings seem OK, but the default gateway is not being set
> (I don't think). I'll try setting it manually again (it didn't seem
> to have any effect
> - after the manual change should I just deactivate and then reactivate eth0,
> or do I need to do more?

Usually you can do a service network restart to get a feel for what
will happen on the next reboot. Any manual command line tweaks you did
will be lost unless you get them into the distribution's config files.

The dhcp server provides default gateway as part of the network packet
info. Depending on which dhcp client you are running you can look at the
dhcp info with (change eth0 to your WAN nic)
cat /etc/dhcpc/dhcpcd-eth0.info
cat /var/lib/dhcp/dhclient-eth0.leases

Here is a script to dump your network settings to a.txt.
Post the results, do not attach it.

Format a diskette on the windows system.
and copy the following to xx.txt using notepad.

#******** start of xx.txt ****************
cat /etc/*release > a.txt
echo $SECURE_LEVEL >> a.txt

echo ======== chkconfig --list ========== >> a.txt
chkconfig --list | grep n >> a.txt

echo ======== resolv.conf ========== >> a.txt
cat /etc/resolv.conf >> a.txt

echo "======== grep eth* /etc/mod*.conf ==========" >> a.txt
grep 'alias eth' /etc/mod*.conf >> a.txt

for nic in 0 1 2 ; do
_fn=/etc/sysconfig/network-scripts/ifcfg-eth$nic
if [ -e $_fn ] ; then

echo ======== mii-tool -v eth$nic ========== >> a.txt
mii-tool -v eth$nic >> a.txt

echo ======== ifcfg-eth$nic ========== >> a.txt
cat $_fn >> a.txt

_fn=/var/lib/dhcp/dhclient-eth${nic}.leases
if [ -e $_fn ] ; then
echo "======== $_fn ==========" >> a.txt
tail -18 $_fn >> a.txt
fi
fi
done

echo ======== ifconfig ========== >> a.txt
ifconfig -a >> a.txt

echo ======== route ========== >> a.txt
route -n >> a.txt

echo ======== network ========== >> a.txt
cat /etc/sysconfig/network >> a.txt

echo ======== hosts ========== >> a.txt
cat /etc/hosts >> a.txt

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

and then copy xx.txt to the diskette.

Move diskette to the linux box, do a
mcopy a:\xx.txt xx
chmod +x xx
../xx
mcopy a.txt a:

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

If mcopy does not exist, you will need to load the mtools package with
urpmi mtools

Bit Twister wrote:

>
> useful suggestions

Thanks, I'll try this later and post the results.

George

On Fri, 21 Oct 2005 03:58:02 -0500, Bit Twister <(E-Mail Removed)>
wrote:

>On Fri, 21 Oct 2005 08:49:18 +0100, GRM wrote:
>

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

For some reason the script wouldn't run, so I did the commands manually - here
is the output:

Fedora Core release 4 (Stentz)
LSB_VERSION="1.3"
Fedora Core release 4 (Stentz)

======= chkconfig --list ======
acpid 0ff 1ff 2ff 3n 4n 5n 6ff
anacron 0ff 1ff 2n 3n 4n 5n 6ff
apmd 0ff 1ff 2n 3n 4n 5n 6ff
arptables_jf 0ff 1ff 2n 3n 4n 5n 6ff
atd 0ff 1ff 2ff 3n 4n 5n 6ff
auditd 0ff 1ff 2n 3n 4n 5n 6ff
autofs 0ff 1ff 2ff 3n 4n 5n 6ff
bluetooth 0ff 1ff 2n 3n 4n 5n 6ff
canna 0ff 1ff 2n 3n 4n 5n 6ff
cpuspeed 0ff 1n 2n 3n 4n 5n 6ff
crond 0ff 1ff 2n 3n 4n 5n 6ff
cups 0ff 1ff 2n 3n 4n 5n 6ff
cups-config-daemon 0ff 1ff 2ff 3n 4n 5n 6ff
gpm 0ff 1ff 2n 3n 4n 5n 6ff
haldaemon 0ff 1ff 2ff 3n 4n 5n 6ff
hpoj 0ff 1ff 2n 3n 4n 5n 6ff
iiim 0ff 1ff 2n 3n 4n 5n 6ff
ip6tables 0ff 1ff 2n 3n 4n 5n 6ff
iptables 0ff 1ff 2n 3n 4n 5n 6ff
irqbalance 0ff 1ff 2n 3n 4n 5n 6ff
isdn 0ff 1ff 2n 3n 4n 5n 6ff
kudzu 0ff 1ff 2ff 3n 4n 5n 6ff
lm_sensors 0ff 1ff 2n 3n 4n 5n 6ff
mDNSResponder 0ff 1ff 2ff 3n 4n 5n 6ff
mdmonitor 0ff 1ff 2n 3n 4n 5n 6ff
messagebus 0ff 1ff 2ff 3n 4n 5n 6ff
netfs 0ff 1ff 2ff 3n 4n 5n 6ff
network 0ff 1ff 2n 3n 4n 5n 6ff
nfslock 0ff 1ff 2ff 3n 4n 5n 6ff
nifd 0ff 1ff 2ff 3n 4n 5n 6ff
pcmcia 0ff 1ff 2n 3n 4n 5n 6ff
portmap 0ff 1ff 2ff 3n 4n 5n 6ff
readahead 0ff 1ff 2ff 3ff 4ff 5n 6ff
readahead_early 0ff 1ff 2ff 3ff 4ff 5n 6ff
rhnsd 0ff 1ff 2ff 3n 4n 5n 6ff
rpcgssd 0ff 1ff 2ff 3n 4n 5n 6ff
rpcidmapd 0ff 1ff 2ff 3n 4n 5n 6ff
sendmail 0ff 1ff 2n 3n 4n 5n 6ff
smartd 0ff 1ff 2n 3n 4n 5n 6ff
sshd 0ff 1ff 2n 3n 4n 5n 6ff
syslog 0ff 1ff 2n 3n 4n 5n 6ff
sysstat 0ff 1n 2n 3n 4n 5n 6ff
xfs 0ff 1ff 2n 3n 4n 5n 6ff
xinetd 0ff 1ff 2ff 3n 4n 5n 6ff
======= resolv.conf ======
; generated by /sbin/dhclient-script
nameserver 212.159.11.150
nameserver 212.159.13.150
search localdomain
======= grep eth* /etc/mod*.conf ======
alias eth0 tulip
======= mii-tool -v eth0 ======
eth0: negotiated 100baseTx-FD, link ok
product info: vendor 00:00:20, model 32 rev 1
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
======= ifcfg-eth0 ======
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:0B:6A:9B:B6:0A
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
DHCP_HOSTNAME=Bruckner
======= /var/lib/dhcp/dhclient-eth0.leases ======
lease {
interface "eth0";
fixed-address 192.168.0.2;
option subnet-mask 255.255.255.0;
option dhcp-lease-time 259200;
option routers 192.168.0.1;
option dhcp-message-type 5;
option dhcp-server-identifier 192.168.0.1;
option domain-name-servers 212.159.11.150,212.159.13.150;
renew 5 2005/10/21 07:20:12;
rebind 6 2005/10/22 13:39:40;
expire 6 2005/10/22 22:39:40;
}
lease {
interface "eth0";
fixed-address 192.168.0.2;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
option dhcp-lease-time 259200;
option dhcp-message-type 5;
option domain-name-servers 212.159.11.150,212.159.13.150;
option dhcp-server-identifier 192.168.0.1;
renew 0 2005/10/23 05:53:09;
rebind 1 2005/10/24 11:52:32;
expire 1 2005/10/24 20:52:32;
}
======= ifconfig ======
eth0 Link encap:Ethernet HWaddr 00:0B:6A:9B:B6:0A
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20b:6aff:fe9b:b60a/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:3 dropped:0 overruns:0 carrier:3
collisions:0 txqueuelen:1000
RX bytes:1164 (1.1 KiB) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x6c00

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

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)

======= route ======
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.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.0.1 0.0.0.0 UG 0 0 0 eth0
======= network ======
NETWORKING=yes
HOSTNAME=localhost.localdomain
======= hosts ======
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost

Thanks for any help you can give

On Fri, 21 Oct 2005 22:23:43 +0100, (E-Mail Removed) wrote:
Sorry, should have noted that (E-Mail Removed) is my home addy
- I'm the same person as GRM

George

On Fri, 21 Oct 2005 22:23:43 +0100, (E-Mail Removed) wrote:
>
> For some reason the script wouldn't run,

Hmm, I would like to know why.

> so I did the commands manually - here is the output:
>
> Fedora Core release 4 (Stentz)
> LSB_VERSION="1.3"
> Fedora Core release 4 (Stentz)
>
> ======= chkconfig --list ======

<snip>
> mDNSResponder 0ff 1ff 2ff 3n 4n 5n 6ff
> nifd 0ff 1ff 2ff 3n 4n 5n 6ff

Let's stop some services for testing.

service nifd stop
service mDNSResponder stop

I would disable them on boot, your call.
chkconfig -del nifd
chkconfig -del mDNSResponder



> ======= resolv.conf ======
> ; generated by /sbin/dhclient-script
> nameserver 212.159.11.150
> nameserver 212.159.13.150
> search localdomain

well, that matches what the router gave you.
you can click up CMD on windows and verify with
ipconfig /all


> ======= grep eth* /etc/mod*.conf ======
> alias eth0 tulip

Good, nic driver is defined for loading.


> ======= mii-tool -v eth0 ======
> eth0: negotiated 100baseTx-FD, link ok
> product info: vendor 00:00:20, model 32 rev 1
> basic mode: autonegotiation enabled
> basic status: autonegotiation complete, link ok
> capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD

Nic is running full duplex and negotiated 100 mb/sec with your router.

> ======= ifcfg-eth0 ======
> DEVICE=eth0
> BOOTPROTO=dhcp
> HWADDR=00:0B:6A:9B:B6:0A
> ONBOOT=yes
> TYPE=Ethernet
> USERCTL=no
> PEERDNS=yes
> IPV6INIT=no
> DHCP_HOSTNAME=Bruckner

Ok

> ======= /var/lib/dhcp/dhclient-eth0.leases ======
> lease {
> interface "eth0";
> fixed-address 192.168.0.2;
> option subnet-mask 255.255.255.0;
> option routers 192.168.0.1;
> option dhcp-lease-time 259200;
> option dhcp-message-type 5;
> option domain-name-servers 212.159.11.150,212.159.13.150;
> option dhcp-server-identifier 192.168.0.1;
> renew 0 2005/10/23 05:53:09;
> rebind 1 2005/10/24 11:52:32;
> expire 1 2005/10/24 20:52:32;
> }

You obtained a lease from the router. Should be good to go.

> ======= ifconfig ======
> eth0 Link encap:Ethernet HWaddr 00:0B:6A:9B:B6:0A
> inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::20b:6aff:fe9b:b60a/64 Scope:Link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:9 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:3 dropped:0 overruns:0 carrier:3
> collisions:0 txqueuelen:1000
> RX bytes:1164 (1.1 KiB) TX bytes:0 (0.0 b)
> Interrupt:3 Base address:0x6c00

Looks good. ignore three TX errors/carrier faults.

>
> 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)

Hmmm, let's try turning off ipv6 translation in /etc/sysconfig/network
Stop the network with
service network stop

add the next line to /etc/sysconfig/network, with carriage return after no.
NETWORKING_IPV6=no
then do a
service network start

> ======= route ======
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.0.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.0.1 0.0.0.0 UG 0 0 0 eth0

Your gateway matches
option routers 192.168.0.1; given in your dhcp lease.
See the line with UG.

> ======= network ======
> NETWORKING=yes
> HOSTNAME=localhost.localdomain

> ======= hosts ======
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost.localdomain localhost

looks ok,

> Thanks for any help you can give

If a
cat /etc/sysconfig/network
looks something like

[root@localhost ~]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=localhost.localdomain
NETWORKING_IPV6=no
[root@localhost ~]#

there is a return after NETWORKING_IPV6=no
which is good.

And you have done a
service network restart

You should be able to prove ping works locally with
ping -c 1 localhost

No idea if
ping -c 1 192.168.0.1
will get a response from your router,

but, you should be able to ping yahoo.com with
ping -c 1 216.109.112.135
to prove connectivity to the internet and
ping -c 1 yahoo.com
to prove dns resolution.

On Fri, 21 Oct 2005 20:40:27 -0500, Bit Twister <(E-Mail Removed)>
wrote:

>On Fri, 21 Oct 2005 22:23:43 +0100, (E-Mail Removed) wrote:
>>
>> For some reason the script wouldn't run,
>
>Hmm, I would like to know why.
>

Tried running it again - the output I got was

: command not found
: command not found
: command not found
: command not found
'/xx: line 14: syntax error near unexpected token 'do
'/xx: line 14: 'for nic in 0 1 2 ; do

Does that explain it?

>If a
>cat /etc/sysconfig/network
>looks something like
>
>[root@localhost ~]# cat /etc/sysconfig/network
>NETWORKING=yes
>HOSTNAME=localhost.localdomain
>NETWORKING_IPV6=no
>[root@localhost ~]#

yep done that

>
>there is a return after NETWORKING_IPV6=no
>which is good.
>
>And you have done a
>service network restart

yep - however, can't get IP info for eth0 now worked OK on boot, but not on
restart. Not sure if it is relevant, but last night it didn't work on boot
either! was OK tonight on boot.

>
>You should be able to prove ping works locally with
>ping -c 1 localhost

Works OK (as does ping -c 1 192.168.0.2)
>
>No idea if
>ping -c 1 192.168.0.1
>will get a response from your router,

Unreachable, but not surprising given the failure to get the IP info

>
>but, you should be able to ping yahoo.com with
>ping -c 1 216.109.112.135
>to prove connectivity to the internet and

also unreachable

>ping -c 1 yahoo.com
>to prove dns resolution.

Sorry this is a rather slow conversation, I am not devoting too much time to
getting Linux working at the moment - I need to have the internet access and as
it is OK when running XP I a just spending an hour or so each evening to look at
this network problem.

Many thanks for your advice so far and for the time you have spent on looking at
my output

George

On Sun, 23 Oct 2005 22:03:17 +0100, GRM wrote:
>
> Does that explain it?

It was my problem, instead of
mcopy a:\xx.txt xx
should have been
mcopy -a a:\xx.txt xx
to remove windows carriage return.

instruction also needed to have
mcopy -t a.txt a:
instead of mcopy a.txt a:
to add windows carriage returns.

> yep - however, can't get IP info for eth0 now worked OK on boot, but not on
> restart. Not sure if it is relevant, but last night it didn't work on boot
> either! was OK tonight on boot.

That indicates an intermittent problem.
For some reason the dhcp server is not giving you a lease.
Anytime it fails, I would try a
service network restart until it is OK

>
>>
>>You should be able to prove ping works locally with
>>ping -c 1 localhost
>
> Works OK (as does ping -c 1 192.168.0.2)
>>
>>No idea if
>>ping -c 1 192.168.0.1
>>will get a response from your router,
>
> Unreachable, but not surprising given the failure to get the IP info

Yes, network has to have received a dhcp lease from your dhcp server
before you can ping beyond your PC.