[4488] in linux-net channel archive

home help back first fref pref prev next nref lref last post

RE: SLIP setup problems

daemon@ATHENA.MIT.EDU (ATPlack)
Fri Sep 20 17:42:25 1996

Date: 	Fri, 20 Sep 1996 14:21:20 -0500
From: ATPlack <ATPlack@scj.com>
To: linux-net@vger.rutgers.edu, mressler@kns.com

I would try running tcpdump on sl0 (both sides) to see if the packets are 
hitting the interface.  This will show you if your commands are working 
correctly to the sl0 interface.

HTH
 ----------
From: mressler@kns.com
To: linux-net@vger.rutgers.edu
Subject: SLIP  setup problems
Date: Friday, September 20, 1996 2:25PM

     I've gotten a little help from this list, however I'm still not
     SLIP'ing. Anybody else care to help? Please.....I need this for a
     Villanova Graduate School project.

     Here is what I did.

     On the Linux SLIP Server (192.9.202.9) using COM1:
        1) Commented out the getty line in /etc/inittab for ttyS0
        2) Commented out Ethernet stuff in /etc/rc.d/rc.inet1
        3) Rebooted to make the above take effect.
        4) Logged in as root and typed:

                slattach -s 9600 -p slip /dev/ttyS0
                ifconfig sl0 192.9.202.9 pointopoint 192.9.202.8 up
                route add default sl0
        5) ping localhost      -> works OK

     On the Linux client (192.9.202.8) using COM3:
        1) Logged in as root and typed:

                slattach -s 9600 -p slip /dev/ttyS2
                ifconfig sl0 192.9.202.8 pointopoint 192.9.202.9 up
                route add default sl0

        2) ping localhost      -> works OK

     If I do a 'ps' on both systems it shows slattach running on the
     appropriate tty.

     On the Linux client (192.9.202.8) I type:

        ping 192.9.202.9

        All I get is the starting banner message then 'ping' hangs until I
     hit a ^C which then reports 100% data loss.

     My null modem cable should be fine. I have used it with "LapLink" (a
     PC file tranfer program).  I also logged in to the Server (when there
     was a getty running on it) from Microsoft Windows Terminal Emulator on
     the client side.  I did have a problem using other VT100 terminal
     emulators (Kermit and PC-VT) which transmitted to the Server OK but no
     login/password prompts where displayed.

     QUESTIONS:
     1) Any idea how to debug my slip problems?
        I tried the -d option for slattach but it only printed out the
initial
        communication settings.
     2) If I run a serial data analyzer, what should I see from ping?
        (Anybody have the 'ping' source code handy?)
     3) Do I run slattach on the Server? The Network Administrator's Guide
(NAG)
        only mentions to run it on the client.

     Thanks!


home help back first fref pref prev next nref lref last post