Re: Internet Access problems in Fedora Core 4

aldin wrote:

Snooz;

Thanks a lot for such a detailed and informative response. Much
appriciated mate.

Ok, Firstly as per your advise i tried to access google through the raw
ipaddress. Actually it did not help, there was an error message. Hence
that failed. I at that point thought that there is a problem with the
os not being able to see the DNS. I did not check if the email is
working or not. I assumed it wont.

As Mark Smith pointed out, that's not quite right, the point of
using the raw ip was to factor out DNS from the troubleshooting.
From what I see in this post, either your gateway value isn't
set right or your card's interface isn't setup right.

As per the your second option i checked my etc/resolv.conf file. This
was done to see if my DNS was misconfigured. The only entry i found
there was:

search localdomain

Ok, this is probably wrong, you want a nameserver entry as you do below:
Usually when you get an ISP account, they'll tell you where their
pop3 and smtp servers are, use that domain as one of the search entries,
for example if your isp is foonet, suppose their pop3 is at pop3.foonet.com
that's a hint the domain you'd want to add to search is foonet.com

search localdomain
search foonet.com
nameserver <proxy if proxy does dns to you or isp's dns>

the "nameserver" entry doesn't have to be there, it depends
on your arrangement with the ISP

If you use dhcp, it's possible you won't have a nameserver
entry in the resolv.conf file, in that case Linux is told each
time by the isp where to go for dns. If you have a Linksys style
hardware router proxy, usually it will do dhcp to the Isp
and then you can either get addresses from it or you will
use static addresses

I tried putting the proxy address as a value to nameserver, assuming
that it would be working as my DNS caching server. I then tried to
access google.com from firefox. It did not help either, so i assume
that my proxy is just a web proxy and not a DNS server.

I think it would be good to not assume and check with the
proxy to see what it's doing. When you say "proxy" do you
mean a hardware style firewall/router/proxy like a Linksys
or Netgear? Most of them have a web interface you can reach from
the green side and turn off/on things like web caching, port
forwarding and so on. The manual for it will tell you the
address to go to, something like http://192.168.0.1 or
the like


I then checked if my browser proxy configuration was set to direct
connection to internet, it actually was set to that. So i went ahead
and changed it to setting proxy manually, and entered my proxy address,
i was not sure of the port so i enetered 80. I tried to access
goole.com again. It falied once again.

Asper your fourth option, i checked to see if my ethernet card was
really up and running. Here is what i found. ( I d used eth1 becasue i
have two LAN interfaces and this is the one i m using on XP and fedora
core 4.)

OK, I'm getting confused here, in your first post you said you
had a 3com Etherlink XL 10/100 card implying you had just
the one? So you really have two of these 3Com cards?
If so things get more complex here, you'll want to check
that linux using the right card. If you have two, maybe the
card that's not plugged in is the one it's trying to use.
This is especially likely because you just showed the output
from interface eth1 and it shows a valid interface for
0.66

what does "ifconfig eth0" say?
or even better just post to me what all these files contain:

/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcfg-eth0 <-- might not exist?
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/hosts <-- host names and ips on your network
/etc/modprobe.conf <-- shows the aliases for your cards

and what these commands say

ifconfig eth0
ifconfig eth1
netstat -nr
netstat -i

[root@localhost ~]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:B0:D0:81:4F:64
inet addr:192.168.0.66 Bcast:192.168.0.255
Mask:255.255.255.0
inet6 addr: fe80::2b0:d0ff:fe81:4f64/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xe880

( *** Concern 1- Values of RX packets and TX packets is zero, is that
normal)


Nope, not good, that means no packets ever got sent on eth1 ever.
But the "UP" shows that the interface is UP


I then tried pinging 64.233.179.99 ( google.com)

[root@localhost ~]# ping 64.233.179.99
PING 64.233.179.99 (64.233.179.99) 56(84) bytes of data.
From 192.168.0.66 icmp_seq=0 Destination Host Unreachable
From 192.168.0.66 icmp_seq=1 Destination Host Unreachable
From 192.168.0.66 icmp_seq=2 Destination Host Unreachable
From 192.168.0.66 icmp_seq=4 Destination Host Unreachable
From 192.168.0.66 icmp_seq=5 Destination Host Unreachable
From 192.168.0.66 icmp_seq=6 Destination Host Unreachable
From 192.168.0.66 icmp_seq=8 Destination Host Unreachable
From 192.168.0.66 icmp_seq=9 Destination Host Unreachable
From 192.168.0.66 icmp_seq=10 Destination Host Unreachable
From 192.168.0.66 icmp_seq=12 Destination Host Unreachable
From 192.168.0.66 icmp_seq=13 Destination Host Unreachable
From 192.168.0.66 icmp_seq=14 Destination Host Unreachable

--- 64.233.179.99 ping statistics ---
15 packets transmitted, 0 received, +12 errors, 100% packet loss, time
14000ms
, pipe 4

( *** Concern - 2 Host was not reachable, why if i may ask)

I then tried to ping my loopback ip (lo) by using:

[root@localhost ~]# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.151 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.112 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.107 ms
64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.118 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.109 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=0.117 ms
64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=0.114 ms
64 bytes from 127.0.0.1: icmp_seq=10 ttl=64 time=0.133 ms
64 bytes from 127.0.0.1: icmp_seq=11 ttl=64 time=0.133 ms
64 bytes from 127.0.0.1: icmp_seq=12 ttl=64 time=0.116 ms
64 bytes from 127.0.0.1: icmp_seq=13 ttl=64 time=0.108 ms
64 bytes from 127.0.0.1: icmp_seq=14 ttl=64 time=0.117 ms
64 bytes from 127.0.0.1: icmp_seq=15 ttl=64 time=0.140 ms
64 bytes from 127.0.0.1: icmp_seq=16 ttl=64 time=0.138 ms
64 bytes from 127.0.0.1: icmp_seq=17 ttl=64 time=0.140 ms
64 bytes from 127.0.0.1: icmp_seq=18 ttl=64 time=0.108 ms

--- 127.0.0.1 ping statistics ---
19 packets transmitted, 19 received, 0% packet loss, time 17997ms
rtt min/avg/max/mdev = 0.107/0.122/0.151/0.016 ms, pipe 2
You have mail in /var/spool/mail/root

[root@localhost ~]#

( *** Concern - 3, as you could see that pinging the loopback interface
did work. Is that a normal occurance, if it is then why it failed to
reach 64.233.179.99 (google.com)

Yes, that's normal to ping to loopback, in fact the loopback will
show as an interface if you type:

ifconfig lo
or you will also see it mentioned from the output of netstat -i:

netstat -i (mine says:)
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 2406 0 0 0 2226 0 0 0 BMRU
lo 16436 0 16 0 0 0 16 0 0 0 LRU



Now since i can not reach out to 64.233.179.99, i m assuming that
there is absolutely nothing working. I m assuming there is a problem
with my ethenet interface configuration. There may also be an ill
configured routing table, it can be checked with netstat -rn, but i
dont know what to see there and how to correct it if it is incorrect.

There can also be a possibility that device configuration with ifconfig
is not functioning properly( RX and TX values being 0 gives that clue).
Please suggest if my ip, broadcast and subnet mask addresses are
defined properly. Also please shed some light on my concerns stated
above.

As far as name resolution is concerned i guess i should put proper info
in resolv.conf file and/or change the rote to the name server. How can
i do that? I guess i d need your help there.

Please help!!!

yeah, I'd say post that stuff (5 files and 4 commands) I requested above
that should do it.

Mark (snooze)

Thnak you and Kind Regards.
j,aldin

.

Relevant Pages

  • Re: Internet Access problem on Fedora Core 4.
    ... was done to see if my DNS was misconfigured. ... I tried putting the proxy address as a value to nameserver, ... I then checked if my browser proxy configuration was set to direct ... PING 64.233.179.99 56bytes of data. ...
    (comp.os.linux.networking)
  • Re: Internet Access problem in Fedora Core 4
    ... was done to see if my DNS was misconfigured. ... I tried putting the proxy address as a value to nameserver, ... I then checked if my browser proxy configuration was set to direct ... PING 64.233.179.99 56bytes of data. ...
    (linux.redhat)
  • Re: Internet Access problem in Fedora Core 4
    ... was done to see if my DNS was misconfigured. ... I tried putting the proxy address as a value to nameserver, ... I then checked if my browser proxy configuration was set to direct ... PING 64.233.179.99 56bytes of data. ...
    (linux.redhat)
  • Re: Internet Access problems in Fedora Core 4
    ... was done to see if my DNS was misconfigured. ... I tried putting the proxy address as a value to nameserver, ... I then checked if my browser proxy configuration was set to direct ... PING 64.233.179.99 56bytes of data. ...
    (comp.os.linux.misc)
  • Re: Frage zum Routing (DNS)
    ... > Dann am ISA aber am internen Interface den ISA DNS eingetragen?! ... Ping geht. ...
    (microsoft.public.de.german.isaserver)