[4516] in linux-net channel archive
Re: SLIP setup problems
daemon@ATHENA.MIT.EDU (Izauddin Mohd Isa)
Tue Sep 24 02:47:31 1996
Date: Tue, 24 Sep 1996 11:05:20 -0800 (GMT+8)
From: Izauddin Mohd Isa <izauddin@guru.polycyber.com.my>
To: "Michael W. Ressler" <mressler@kns.com>
cc: linux-net@vger.rutgers.edu
In-Reply-To: <9608208432.AA843248140@ccmail1.kns.com>
On Fri, 20 Sep 1996, Michael W. Ressler wrote:
> 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.
>
First make sure that your kernel support ip forwarding, than change the
default route to the remote address, not the local ip address, coz the
packet doesn't know where to go if you specify the local ip address.
Hope this help.
Regards
Din
