Re: [aclug-L] ping

[Steven Saner <ssaner@xxxxxxxxxxxxx>]

Well, actually, since you are trying to ping an IP address, ping isn't
going to complain even if there is nothing on the network with that
IP. It's just not going to do anything. The thing you need to do is
this: First, as root, type ifconfig on both machines. You should get
somehting like this:

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:44885 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44885 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0      Link encap:Ethernet  HWaddr 00:80:AD:AC:9B:00
          inet addr:10.0.0.3  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:429511 errors:0 dropped:0 overruns:0 frame:0
          TX packets:836687 errors:0 dropped:0 overruns:0 carrier:0 coll:2
          Interrupt:9 Base address:0x300

This tells you that the ethernet card is up, tcp/ip is working, and
you have an ip address assigned correctly. Then type netstat -r on
both machines. You should get something like:

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window irtt Iface
loopback        *               255.0.0.0       U      3584 0         0 lo
10.0.0.0        *               255.0.0.0       U      1500 0         0 eth0

This tells you that you have a route to your network established.

Tell us what the output of these commands are on your systems and we
can probably come to a solution. I am guessing that you don't have a
route setup.



On Mon, Jan 25, 1999 at 10:21:51PM -0600, Nate Bargmann wrote:
> phrostie wrote:
> > 
> > what is supposed to happen when i do ping 192.168.1.2(the other
> > machine)
> > i get     PING 192.168.1.1(192.168.1.1) 56 data bytes
> > 
> > then nothing until i CTRL C
> > 
> > then     27 packets transmitted, 0 packets recieved, 100% packet loss
> > 
> > i think this is what's called bating zero.
> > 
> > how do i test what's happening?
> 
> Not stupid at all.  One of the first tests to try when putting a new
> machine on a network is ping.  First off, ping didn't complain about an
> unknown host, so the computer you're running ping on knows about the
> destination machine, the one you're pinging.  That's good.
> 
> In my limited experience, I can think of two problems as to why it isn't
> working.  First, the other machine doesn't know about the machine you're
> pinging from or doesn't know a network route back to it.  If other
> network services work between the two machines, it may be that machine 2
> has ping responses disabled in some way or is behind a firewall.
> 
> Beyond that, I'm not much help.  I do know ping has a switch, -i that
> you can use to tell ping to try every so many seconds, e.g.
> 
> ping -i 15 host2
> 
> will send a ping packet every 15 seconds.  This is useful for amateur
> radio networks (like I'm used to) where network latencies are much
> higher than found on wired networks.
> 
> - Nate >>
> 
> -- 
> 
>  Packet   | N0NB @ WF0A.#SCKS.KS.USA.NOAM       | "The more you
>  Internet | ka0rny@xxxxxxxxxx                   | complain, the
>  Location | Valley Center, Kansas USA EM17hs    | longer God lets
>         Visit my Linux + Ham Radio pages        | you live."
>    http://homepage.netspaceonline.com/~ka0rny/  |
> ---
> This is the Air Capital Linux Users Group discussion list.  If you
> want to unsubscribe, send the word "unsubscribe" to
> aclug-L-request@xxxxxxxxxxxx.  If you want to post to the list, send your
> message to aclug-L@xxxxxxxxxxxx.

-- 
==================================================================
Steven Saner                            SouthWind Internet Access, Inc.
ssaner@xxxxxxxxxxxxx                    Technical Support
http://www2.southwind.net/~ssaner       support@xxxxxxxxxxxxx
                                        http://www.southwind.net
                                        263-7963 Wichita  (800)525-7963

---
This is the Air Capital Linux Users Group discussion list.  If you
want to unsubscribe, send the word "unsubscribe" to
aclug-L-request@xxxxxxxxxxxx.  If you want to post to the list, send your
message to aclug-L@xxxxxxxxxxxx.