Re: Internet Access problem on Fedora Core 4.
- From: "aldin" <jaldin80@xxxxxxxxxxxx>
- Date: 18 Mar 2006 13:14:52 -0800
Yuni;
Thanks a lot for responding. Much appriciated mate.
Ok, Firstly 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 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
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 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.
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.)
[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)
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)
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!!!
Thnak you and Kind Regards.
j,aldin
.
- Follow-Ups:
- Re: Internet Access problem on Fedora Core 4.
- From: yunikan
- Re: Internet Access problem on Fedora Core 4.
- References:
- Internet Access problem on Fedora Core 4.
- From: aldin
- Re: Internet Access problem on Fedora Core 4.
- From: yunikan
- Internet Access problem on Fedora Core 4.
- Prev by Date: Re: WiFi under Linux - rant no 7
- Next by Date: Re: CIDR Shorthand Question
- Previous by thread: Re: Internet Access problem on Fedora Core 4.
- Next by thread: Re: Internet Access problem on Fedora Core 4.
- Index(es):
Relevant Pages
|
