On LAN, but can't get to Internet on FC5 box

OK, installed a Fedora Core 5 machine to replace a FC2.
Same hardware, just completely new OS install (I saved the config files
of the old setup for assistance.)

I can access it from other machines on the LAN and vise versa, but I
can't get outside the LAN and access say, yahoo.com or even the
machines outside the LAN that are shown in my /etc/hosts from this new
box.
All I get when I try to connect to them are "Can't resolve hosts" and
time outs.
Like:

[root@fileserve etc]# ping yahoo.com
PING yahoo.com (216.109.112.135) 56(84) bytes of data.
--- yahoo.com ping statistics ---
30 packets transmitted, 0 received, 100% packet loss, time 29010ms

I've tried turning off IPTables and flushing them, no change.

The settings shown below all match the saved config files for the old
setup.
Any ideas?

[root@fileserve etc]# uname -a
Linux fileserve.localdomain 2.6.16-1.2096_FC5 #1 Wed Apr 19 05:14:36
EDT 2006 i686 i686 i386 GNU/Linux

[root@fileserve etc]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:40:05:8A:92:00
inet addr:192.168.2.2 Bcast:192.168.2.15
Mask:255.255.255.240
inet6 addr: fe80::240:5ff:fe8a:9200/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6862 errors:0 dropped:0 overruns:0 frame:0
TX packets:20292 errors:0 dropped:0 overruns:0 carrier:0
collisions:1517 txqueuelen:1000
RX bytes:577902 (564.3 KiB) TX bytes:4967835 (4.7 MiB)
Interrupt:10

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

[root@fileserve etc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.2.2
NETMASK=255.255.255.240
GATEWAY=192.168.2.1

[root@fileserve etc]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.2.0 0.0.0.0 255.255.255.240 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.2.1 0.0.0.0 UG 0 0 0
eth0

[root@fileserve etc]# cat /etc/resolv.conf
nameserver 192.168.2.1
nameserver 64.89.70.2
nameserver 64.89.74.2

[root@fileserve etc]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain localhost
72.3.xx.xx. beta
72.3.yy.yy alpha

(the IP's are actual IP's in the real file, of course.)


What else can I look for? What should I focus on to try to figure this
out?
Thanks for any suggestions.

On 23 Apr 2006 19:50:46 -0700, (E-Mail Removed) wrote:
> OK, installed a Fedora Core 5 machine to replace a FC2.
> Same hardware, just completely new OS install (I saved the config files
> of the old setup for assistance.)
>
> I can access it from other machines on the LAN and vise versa, but I
> can't get outside the LAN and access say, yahoo.com or even the
> machines outside the LAN that are shown in my /etc/hosts from this new
> box.

Usually caused when /etc/resolv.conf does not have your ISP's
nameservers.

> All I get when I try to connect to them are "Can't resolve hosts" and
> time outs.

If
ping -c 1 66.94.234.13
works, you are routing all the way to yahoo.com. This must work first.
If
ping -c 1 yahoo.com
fails, it is a DNS problem.
>
> [root@fileserve etc]# cat /etc/resolv.conf
> nameserver 192.168.2.1
> nameserver 64.89.70.2
> nameserver 64.89.74.2

Hmmm, first entry makes me think tmdns is running. Stop and prevent it
from running. On my Mandriva linux install, the commands would be
chkconfig --del tmdns
service tmdns stop

Then make resolv.conf look like

cat /etc/resolv.conf
nameserver 64.89.70.2
nameserver 64.89.74.2

now try the two ping tests.

> [root@fileserve etc]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost localhost.localdomain localhost
> 72.3.xx.xx. beta
> 72.3.yy.yy alpha

Thought the short name should be on the end.
127.0.0.1 localhost.localdomain localhost

Also, I would make it look something like mine, if me.

$ head -3 /etc/hosts
127.0.0.1 localhost
192.168.2.1 fw.home.invalid fw
192.168.2.10 wb.home.invalid wb <======

$ cat /etc/sysconfig/network
HOSTNAME=wb.home.invalid <====== my LAN node and LAN domain name
NETWORKING=yes
NETWORKING_IPV6=no
GATEWAY=192.168.2.1
GATEWAYDEV=eth0

(E-Mail Removed) wrote:
> OK, installed a Fedora Core 5 machine to replace a FC2.
> Same hardware, just completely new OS install (I saved the config files
> of the old setup for assistance.)
>
> I can access it from other machines on the LAN and vise versa, but I
> can't get outside the LAN and access say, yahoo.com or even the
> machines outside the LAN that are shown in my /etc/hosts from this new
> box.
> All I get when I try to connect to them are "Can't resolve hosts" and
> time outs.
> Like:
>
> [root@fileserve etc]# ping yahoo.com
> PING yahoo.com (216.109.112.135) 56(84) bytes of data.
> --- yahoo.com ping statistics ---
> 30 packets transmitted, 0 received, 100% packet loss, time 29010ms
>
> I've tried turning off IPTables and flushing them, no change.
>
> The settings shown below all match the saved config files for the old
> setup.
> Any ideas?
>
> [root@fileserve etc]# uname -a
> Linux fileserve.localdomain 2.6.16-1.2096_FC5 #1 Wed Apr 19 05:14:36
> EDT 2006 i686 i686 i386 GNU/Linux
>
> [root@fileserve etc]# ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:40:05:8A:92:00
> inet addr:192.168.2.2 Bcast:192.168.2.15
> Mask:255.255.255.240
> inet6 addr: fe80::240:5ff:fe8a:9200/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:6862 errors:0 dropped:0 overruns:0 frame:0
> TX packets:20292 errors:0 dropped:0 overruns:0 carrier:0
> collisions:1517 txqueuelen:1000
> RX bytes:577902 (564.3 KiB) TX bytes:4967835 (4.7 MiB)
> Interrupt:10
>
> 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:27 errors:0 dropped:0 overruns:0 frame:0
> TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1679 (1.6 KiB) TX bytes:1679 (1.6 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)
>
> [root@fileserve etc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=static
> IPADDR=192.168.2.2
> NETMASK=255.255.255.240
> GATEWAY=192.168.2.1
>
> [root@fileserve etc]# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.2.0 0.0.0.0 255.255.255.240 U 0 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
^^^^^^^^^^^^^^^^^^^^^^^^
What is that entry for?

> eth0
> 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0
> eth0
>
> [root@fileserve etc]# cat /etc/resolv.conf
> nameserver 192.168.2.1
> nameserver 64.89.70.2
> nameserver 64.89.74.2
>
> [root@fileserve etc]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost localhost.localdomain localhost
> 72.3.xx.xx. beta
> 72.3.yy.yy alpha
>
> (the IP's are actual IP's in the real file, of course.)
>
>
> What else can I look for? What should I focus on to try to figure this
> out?
> Thanks for any suggestions.
>

Try traceroute -n 216.109.112.135 and see where it stops?

The Natural Philosopher wrote:
> (E-Mail Removed) wrote:
> > OK, installed a Fedora Core 5 machine to replace a FC2.
> > Same hardware, just completely new OS install (I saved the config files
> > of the old setup for assistance.)
> >
> > I can access it from other machines on the LAN and vise versa, but I
> > can't get outside the LAN and access say, yahoo.com or even the
> > machines outside the LAN that are shown in my /etc/hosts from this new
> > box.
> > All I get when I try to connect to them are "Can't resolve hosts" and
> > time outs.
> > Like:
> >
> > [root@fileserve etc]# ping yahoo.com
> > PING yahoo.com (216.109.112.135) 56(84) bytes of data.
> > --- yahoo.com ping statistics ---
> > 30 packets transmitted, 0 received, 100% packet loss, time 29010ms
> >
> > I've tried turning off IPTables and flushing them, no change.
> >
> > The settings shown below all match the saved config files for the old
> > setup.
> > Any ideas?
> >
> > [root@fileserve etc]# uname -a
> > Linux fileserve.localdomain 2.6.16-1.2096_FC5 #1 Wed Apr 19 05:14:36
> > EDT 2006 i686 i686 i386 GNU/Linux
> >
> > [root@fileserve etc]# ifconfig -a
> > eth0 Link encap:Ethernet HWaddr 00:40:05:8A:92:00
> > inet addr:192.168.2.2 Bcast:192.168.2.15
> > Mask:255.255.255.240
> > inet6 addr: fe80::240:5ff:fe8a:9200/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:6862 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:20292 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:1517 txqueuelen:1000
> > RX bytes:577902 (564.3 KiB) TX bytes:4967835 (4.7 MiB)
> > Interrupt:10
> >
> > 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:27 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:1679 (1.6 KiB) TX bytes:1679 (1.6 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)
> >
> > [root@fileserve etc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
> > DEVICE=eth0
> > ONBOOT=yes
> > BOOTPROTO=static
> > IPADDR=192.168.2.2
> > NETMASK=255.255.255.240
> > GATEWAY=192.168.2.1
> >
> > [root@fileserve etc]# route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 192.168.2.0 0.0.0.0 255.255.255.240 U 0 0 0
> > eth0
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> ^^^^^^^^^^^^^^^^^^^^^^^^
> What is that entry for?
>
I have absolutely no idea. The first two octets don't look familiar.
How can I find out more?
I did an nslookup on the IP and got:

[root@webserve ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.2.0 * 255.255.255.252 U 0 0 0
eth0
169.254.0.0 * 255.255.0.0 U 0 0 0
eth0
default 192.168.2.1 0.0.0.0 UG 0 0 0
eth0
[root@webserve ~]# nslookup 169.254.0.0
Server: 64.89.70.2
Address: 64.89.70.2#53

** server can't find 0.0.254.169.in-addr.arpa: NXDOMAIN

> > eth0
> > 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0
> > eth0
> >
> > [root@fileserve etc]# cat /etc/resolv.conf
> > nameserver 192.168.2.1
> > nameserver 64.89.70.2
> > nameserver 64.89.74.2
> >
> > [root@fileserve etc]# cat /etc/hosts
> > # Do not remove the following line, or various programs
> > # that require network functionality will fail.
> > 127.0.0.1 localhost localhost.localdomain localhost
> > 72.3.xx.xx. beta
> > 72.3.yy.yy alpha
> >
> > (the IP's are actual IP's in the real file, of course.)
> >
> >
> > What else can I look for? What should I focus on to try to figure this
> > out?
> > Thanks for any suggestions.
> >
>
> Try traceroute -n 216.109.112.135 and see where it stops?

[root@webserve ~]# traceroute -n 216.109.112.135
traceroute to 216.109.112.135 (216.109.112.135), 30 hops max, 40 byte
packets
1 192.168.2.1 (192.168.2.1) 0.977 ms 0.659 ms 0.874 ms
2 192.168.1.1 (192.168.1.1) 2.890 ms 4.026 ms 2.755 ms
3 209.248.164.97 (209.248.164.97) 9.150 ms 8.891 ms 8.863 ms
4 65.77.99.181 (65.77.99.181) 39.232 ms 38.557 ms 39.073 ms
5 65.77.99.181 (65.77.99.181) 40.200 ms 39.771 ms 38.230 ms
6 64.200.249.41 (64.200.249.41) 47.346 ms 47.055 ms 47.561 ms
7 64.200.183.37 (64.200.183.37) 49.207 ms 48.529 ms 48.203 ms
8 64.200.240.81 (64.200.240.81) 47.456 ms 48.042 ms 48.233 ms
9 64.200.105.78 (64.200.105.78) 49.919 ms 50.780 ms 49.082 ms
10 64.200.232.218 (64.200.232.218) 50.308 ms 51.410 ms 51.549 ms
11 216.115.101.144 (216.115.101.144) 76.185 ms 74.694 ms 74.027
ms
12 216.115.96.185 (216.115.96.185) 75.208 ms 216.115.96.165
(216.115.96.165) 75.616 ms 75.335 ms
13 216.109.120.249 (216.109.120.249) 76.673 ms 79.094 ms
216.109.120.219 (216.109.120.219) 75.841 ms
14 * * *
15 * * *

Am Montag, den 24.04.2006, 20:39 +0100 schrieb The Natural Philosopher:

> >
> > [root@fileserve etc]# route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 192.168.2.0 0.0.0.0 255.255.255.240 U 0 0 0
> > eth0
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> ^^^^^^^^^^^^^^^^^^^^^^^^
> What is that entry for?

This might be an adress added by zeroconf.

Greets
Chris Scheurer

The Natural Philosopher wrote:
> (E-Mail Removed) wrote:
>
>> OK, installed a Fedora Core 5 machine to replace a FC2.
>> Same hardware, just completely new OS install (I saved the config files
>> of the old setup for assistance.)
>>
>> I can access it from other machines on the LAN and vise versa, but I
>> can't get outside the LAN and access say, yahoo.com or even the
>> machines outside the LAN that are shown in my /etc/hosts from this new
>> box.
>> All I get when I try to connect to them are "Can't resolve hosts" and
>> time outs.
>> Like:
>>
>> [root@fileserve etc]# ping yahoo.com
>> PING yahoo.com (216.109.112.135) 56(84) bytes of data.
>> --- yahoo.com ping statistics ---
>> 30 packets transmitted, 0 received, 100% packet loss, time 29010ms
>>
>> I've tried turning off IPTables and flushing them, no change.
>>
>> The settings shown below all match the saved config files for the old
>> setup.
>> Any ideas?
>>
>> [root@fileserve etc]# uname -a
>> Linux fileserve.localdomain 2.6.16-1.2096_FC5 #1 Wed Apr 19 05:14:36
>> EDT 2006 i686 i686 i386 GNU/Linux
>>
>> [root@fileserve etc]# ifconfig -a
>> eth0 Link encap:Ethernet HWaddr 00:40:05:8A:92:00
>> inet addr:192.168.2.2 Bcast:192.168.2.15
>> Mask:255.255.255.240
>> inet6 addr: fe80::240:5ff:fe8a:9200/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:6862 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:20292 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:1517 txqueuelen:1000
>> RX bytes:577902 (564.3 KiB) TX bytes:4967835 (4.7 MiB)
>> Interrupt:10
>>
>> 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:27 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:1679 (1.6 KiB) TX bytes:1679 (1.6 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)
>>
>> [root@fileserve etc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
>> DEVICE=eth0
>> ONBOOT=yes
>> BOOTPROTO=static
>> IPADDR=192.168.2.2
>> NETMASK=255.255.255.240
>> GATEWAY=192.168.2.1
>>
>> [root@fileserve etc]# route -n
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref Use
>> Iface
>> 192.168.2.0 0.0.0.0 255.255.255.240 U 0 0 0
>> eth0
>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
>
> ^^^^^^^^^^^^^^^^^^^^^^^^
> What is that entry for?
>

That's the "Zero Conf" entry, RedHat puts that in by default. Zero
configuration is a new thing (Ref http://www.zeroconf.org/ ) that's
supposed to help manage different protocol usages with
different computer makes on the same network. You can turn that
route off in Red Hat Fedora by adding to the /etc/sysconfig/network file:

NOZEROCONF=yes

Mark