[4494] in linux-net channel archive
RE: SLIP setup problems
daemon@ATHENA.MIT.EDU (Roman Dolejsi)
Sat Sep 21 04:13:01 1996
Date: Sat, 21 Sep 1996 08:37:00 -0500 (CDT)
From: Roman Dolejsi <roman@sorry.vse.cz>
To: ATPlack <ATPlack@scj.com>
Cc: linux-net@vger.rutgers.edu, mressler@kns.com
In-Reply-To: <96Sep20.161923-0400_edt.112119-143+559@vger.rutgers.edu>
You should probably take care whether the client side uses the right COM
port. If you have more that two COM ports in your computer and you are using
COM3 for your slip, there can be collision with COM1's IRQ (COM1,3=IRQ4;
COM2,4=IRQ3). You may not use anything on your COM1 port to allow COM3 port
work properly... But that's only my opinion (and completely wrong when you
are using some multiport board in your client).
Anyway, good luck..
%%%% %%% % % %%% % % Roman Dolejsi
% % % % %% %% % % %% % Network Administrator at VSE/JM, Prague, CZE
%%%% % % % % % %%%%% % % %
% % % % % % % % % %% mail: roman@sorry.vse.cz
% % %%% % % % % % % http://sorry.vse.cz/~roman
> 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!
>
