Very Computer

I'm trying to SLIP into my work computer on which I have successfully
installed The Internet Adapter (TIA).  I have successfully connected via
a dip chat script and verified that dip starts up TIA.  However, I still
can't ping or telnet my work computer after dip is connected.  Below are some
diagnostics.

Before starting the dip chat script I can ping myself, and I've included
the output from ifconfig and netstat:

bash# /etc/ifconfig
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:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:0 errors:0 dropped:0 overruns:0

bash# netstat -r
Kernel routing table
Destination     Gateway         Genmask         Flags Metric Ref Use    Iface
localhost       *               255.255.255.255 UH    0      0        0 lo

bash# /sbin/ping localhost
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=1.3 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=1.4 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=1.4 ms

--- localhost ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.3/1.3/1.4 ms

However, After dip chat script:
(TIA successfully starts up with "The Internet Adapter" message which I see
by running dip with "echo on")
Dip script prints success message:
CONNECTED to hops.larc.nasa.gov with address 128.155.17.47 we are 192.0.2.1

bash# netstat -r
Kernel routing table
Destination     Gateway         Genmask         Flags Metric Ref Use    Iface
localhost       *               255.255.255.255 UH    0      0        6 lo
hops.larc.nasa. *               255.255.255.255 UH    0      0        0 sl0
default         hops.larc.nasa. 0.0.0.0         UG    0      0        0 sl0

bash# /etc/ifconfig
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:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:6 errors:0 dropped:0 overruns:0

sl0       Link encap:Serial Line IP  
          inet addr:192.0.2.1  P-t-P:128.155.17.47  Mask:255.255.255.0
          UP POINTOPOINT RUNNING  MTU:296  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:0 errors:0 dropped:0 overruns:0

But if I try to ping hops, I get:

PING hops.larc.nasa.gov (128.155.17.47): 56 data bytes

--- hops.larc.nasa.gov ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

Same for telnet:

bash# telnet hops
Trying 128.155.17.47...

and it just hangs there.

My Linux box correctly maps "hops.larc.nasa.gov" to 128.155.17.47, but that's
all.  Can someone suggest some diagnostics to try and get to the bottom of
this?

Thanks,
Guy Beaver

--
 Guy M. Beaver                          *    --
 G & A Technical Software, Inc. (GATS)  *  / / __  

 (804) 864-5763                         *   \___/

|>
|> I'm trying to SLIP into my work computer on which I have successfully
|> installed The Internet Adapter (TIA).  I have successfully connected via
|> a dip chat script and verified that dip starts up TIA.  However, I still
|> can't ping or telnet my work computer after dip is connected.  Below are some
|> diagnostics.

  <snip>

Well, I am successfully using the TIA connection my internet provider supplies
to post this with xrn, so it is possible. One piece of advice that I can give
right away, because it caused me trouble when I started trying to use TIA, is
to give up on ping - TIA doesn't support ping. Once I was informed of this,
I tried telnet anyway, and sure enough, it worked! Debugging network connections
without ping - how depressing...

        How do you know that it starts Tia? If you can't telnet to the
*host*, chances are you haven't. To telnet to other sites, you need to
have a nameserver defined in etc/resolv.conf.

Quote:>Well, I am successfully using the TIA connection my internet provider supplies
>to post this with xrn, so it is possible. One piece of advice that I can give
>right away, because it caused me trouble when I started trying to use TIA, is
>to give up on ping - TIA doesn't support ping. Once I was informed of this,
>I tried telnet anyway, and sure enough, it worked! Debugging network connections
>without ping - how depressing...

        Nope, no ping yet, but I heard the authors may be trying to
support this soon. The current beta release now supports X windows and
incoming telnet/ftp, although the latter is not without the usual
"gotchas" associated with a dialup SLIP line that is dynamically
addressed.
--
                        Irish
    "I'm not the shell answer man, I just know some things about Linux"

Sounds an awful lot like a situation I got myself into.  I fixed it by upgrading
my kernel.  I was running SLS 1.03.  I had been upgrading my kernels as they
approached 1.0, until I was finally running Linux 1.0.0.  Then I tried to
upgrade my network support and started seeing the situation you described.
SL/IP would start, route would show a route, ifconfig would say that the
device was active, but no responses were ever received.  BUT, if I used a second
modem to connect to the remote machine, ping said that my Linux machine was
alive.  I could telnet to it, even open X applications across the SL/IP line!
Eventually I got tired of this "one-sided" SL/IP connection, and upgraded
my kernel to 1.1.45 (I've since upgraded again to 1.1.52).  When I did,
the SL/IP connection started working again.  I had to upgrade major portions
of my network code (I'm now running net-3 instead of net-2d) in order to get
telnet/ftp/rlogin working right again, but the rest of the network software
utilities seemed OK.  You didn't mention what version of Linux you are running
on.  I suspect that the TIA you installed was developed for a later kernel
than you are currently running.

--
Kevin J. Cummings                       Peritus Software Services, Inc.

[mucho deletia]

Quote:>I suspect that the TIA you installed was developed for a later kernel
>than you are currently running.

        1. TIA is not a Linux app/util, and is not dependent on kernel
versions, networking versions, phases of the moon or pb&j sandwiches.
TIA is a daemon run on a host that simulates a SLIP connection to a
dialup client. Virtually ANY software that will make a successful SLIP
connection or is a working SLIP client will work with TIA.  
        2. An Exception: Unfortunately, TIA currently does *not* support  
ping. Future versions are supposed to correct this.
        Any questions?
--
       Irish                                    __________________________

 Linux and TIA help  |  Reusable at many major |   FREE LINUX SOFTWARE!   |
Available on request |   FTP sites near you!   |__________________________|

:       2. An Exception: Unfortunately, TIA currently does *not* support  
: ping. Future versions are supposed to correct this.
:       Any questions?

TIA will never be able to support ping. Ping uses ICMP packets, which only
root can send. I suppose it it was suid this would be possible, but...

  Scott.