[OLUG] failures
Nathan Brown
tbrown at radiks.net
Fri Jan 28 00:59:50 UTC 2000
This thread is positively not obsolete. I just dont' have any more questions that seem
pertinent . but i followed the instructions and here is a print of my terminal screen
as things were carried out... it works on my side but not the other side .
A friend of mine took my instructions for installing red hat 6.1 and did so to his
machine. He has no problem at all getting connected to the internet so it must be
something quirky about my machine .
thanks for the attention,
Nate
______________________________________________________________________________________________________________________
[root at localhost /]# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) from 127.0.0.1 : 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.1 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.1 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.1 ms
--- 127.0.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.1/0.1 ms
[root at localhost /]#
[root at localhost /]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:207.3.66.154 P-t-P:207.3.66.109 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:7 errors:1 dropped:0 overruns:0 frame:1
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
[root at localhost /]# ping 207.3.66.154
PING 207.3.66.154 (207.3.66.154) from 207.3.66.154 : 56(84) bytes of data.
64 bytes from 207.3.66.154: icmp_seq=0 ttl=255 time=0.1 ms
64 bytes from 207.3.66.154: icmp_seq=1 ttl=255 time=0.1 ms
64 bytes from 207.3.66.154: icmp_seq=2 ttl=255 time=0.1 ms
--- 207.3.66.154 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.1/0.1 ms
[root at localhost /]# ping 207.3.66.109
PING 207.3.66.109 (207.3.66.109) from 207.3.66.154 : 56(84) bytes of data.
--- 207.3.66.109 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss
[root at localhost /]# rout -n
bash: rout: command not found
[root at localhost /]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
207.3.66.109 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 207.3.66.109 0.0.0.0 UG 0 0 0 ppp0
[root at localhost /]# ping 207.71.200.67
PING 207.71.200.67 (207.71.200.67) from 207.3.66.154 : 56(84) bytes of data.
--- 207.71.200.67 ping statistics ---
14 packets transmitted, 0 packets received, 100% packet loss
[root at localhost /]# telnet 204.71.200.67
Trying 204.71.200.67...
^^
^^
[root at localhost /
_________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________
tetherow at nol.org wrote:
> On 17 Jan, Nathan Brown wrote:
> > I'm not getting my problem solved here something very simple and very strange is
> > happening and I am not gonna get it ... I was wondering if anyone knew of another
> > LUG anywhere that would possibly be able to help.
> > Thanks again very much,
> > Nate
>
> Sorry I am so behind on mail and this thread is hopefully obsolete but
> just in case...
>
> Lets try starting from the begining:
> 0. Ping localhost (127.0.0.1). This will insure that your TCP/IP stack
> works.
>
> 1. Once you dial in try pinging your side of the PPP connection.
> Check ifconfig for the ip address on ppp0 for your side
> If this succeeds then you know your side of the ppp connection is up
> and running.
>
> 2. Try pinging the remote side of the PPP connection should be the PtP
> address in ifconfig.
> If this succeeds then you know that the remote side of the ppp
> connection is up and the static route works.
> If this fails check your routing table for a static route to the
> remote side of the ppp connection
> # route -n
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 206.222.217.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 127.0.0.0 0.0.0.0 255.255.255.255 UH 0 0 0 lo
> 0.0.0.0 206.222.217.xxx 0.0.0.0 UG 0 0 0 ppp0
>
> What you are looking for is like the first line in the output
> 206.222.217.xxx is the P-t-P address from ifconfig. This is the
> route that tells you machine how to get to the remote side of the
> ppp connection which is your gateway.
>
> 3. Try pinging anything else (say 204.71.200.67 which is yahoo)
> If this works then you know it is not a routing or communications
> issue but is really a DNS problem more than likely.
> If it doesn't work check the route table again (see above) and look
> for the line like the last one. Again 206.222.217.xxx should be the
> P-t-P address listed in ifconfig. This is your default route (hence
> the Destination of 0.0.0 and Genmask of 0.0.0 as well as the G in
> flags). Make sure that the Iface matches the ppp connection
> interface (should be ppp0 but doesn't HAVE to be). If that line
> exists but you can't ping outside try something else, such as
> # telnet 204.71.200.67 80
> Connected to 204.71.200.67.
> Escape character is '^]'.
> Then type GET / and hit enter. You should get the HTML for Yahoo's
> homepage from this. If not things have now gotten very strange in
> the routing setup, possible culprit is a firewall on your machine (I
> wouldn't think you are dialed in to anything that doesn't allow www
> access out).
> # ipchains -L
> If you get output from this command email it to the list and we'll
> see if that is what is causing problems.
>
> In all the above use IP addresses. If these work the issues is name
> service and not networking.
>
> If it is nameservice try the following:
> # nslookup www.yahoo.com 205.138.126.6
> This will use dns.radiks.net to lookup the IP address for yahoo. If
> this works cat /etc/resolv.conf it should look something like:
> search radiks.net
> nameserver 205.138.126.6
>
> If you have gotten this far and things still aren't working mail me
> back.
>
> ------------------------------------------------------------------------
> Sam Tetherow tetherow at nol.org
> Director of Development
> Nebrask@ Online http://www.nol.org/
>
> -------------------------------------------------------------------------
> Sent by OLUG Mailing list Manager, run by ezmlm. http://olug.bstc.net/
> To unsubscribe: `echo unsubsribe | mail olug-unsubscribe at bstc.net`
-------------------------------------------------------------------------
Sent by OLUG Mailing list Manager, run by ezmlm. http://olug.bstc.net/
To unsubscribe: `echo unsubsribe | mail olug-unsubscribe at bstc.net`
More information about the OLUG
mailing list