Xref: utzoo comp.protocols.tcp-ip:10380 alt.sys.sun:564 comp.dcom.lans:4447
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!helios.ee.lbl.gov!ace.ee.lbl.gov!leres
From: leres@ace.ee.lbl.gov (Craig Leres)
Newsgroups: comp.protocols.tcp-ip,alt.sys.sun,comp.dcom.lans
Subject: Re: How to SLIP without subnets (was SLIP on unix-systems)
Message-ID: <4954@helios.ee.lbl.gov>
Date: 26 Feb 90 03:05:22 GMT
References: <3015@draken.nada.kth.se> <1274@shelby.Stanford.EDU>
Sender: usenet@helios.ee.lbl.gov
Reply-To: leres@helios.ee.lbl.gov (ucbvax!leres for uucp weenies)
Followup-To: comp.protocols.tcp-ip
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 22
X-Local-Date: 25 Feb 90 19:05:22 PST

Followups to comp.protocols.tcp-ip.

Gee, perhaps I'm missing the point but I don't see why you need to use
subnets at all. Let's say the slip gateway machine's address is
126.0.128.30 (using a netmask of 0xffffff00). Pick any free address on
the subnet for the remote host, say 126.0.128.45.

Now on the remote side, ifconfig the slip line (which is a
point-to-point) using the ip address we've chosen for the local end
(126.0.128.45) and the address of the gateway for the far end
(126.0.128.30). Install a static default route via the gateway
(126.0.128.30).

On the slip gateway, ifconfig the slip line using the gateway and
remote addresses (reversed from above). This gives you an interface
route to the remote host. Publish an arp entry for the remote host
(126.0.128.45) using the ethernet address of the gateway. (Make
sure ipforwarding is enabled.)

We've been running two slip hosts this way for months now...

		Craig