Path: utzoo!attcan!uunet!cs.utexas.edu!rice!sun-spots-request
From: jch@risci.tn.cornell.edu (Jeffrey C Honig)
Newsgroups: comp.sys.sun
Subject: Re: Problem with bind system call over slip link
Keywords: Networks
Message-ID: <4247@brazos.Rice.edu>
Date: 4 Jan 90 03:17:53 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 26
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n2, Replies: v9n2
X-Sun-Spots-Digest: Volume 9, Issue 6, message 1 of 9

On Tue, 26 Dec 89 14:59:16 PST wrs@niagara.tymnet.com (Bill Soley) writes:
| I don't use cisco SLIP, but I can say this about Sun SLIP: Sun thinks of
| the SLIP line as a network unto itself, not as an interface to a remote
| network.  This means the SLIP line needs its own (unique) network (or
| subnet) number and the interface at each end needs a host number on that
| network (one for cisco and a different one for Sun).  This is the same
| model 4.3 BSD uses.
| 
| Try changing
| 	sc->sc_if.if_flags = IFF_POINTOPOINT;
| to
| 	sc->sc_if.if_flags = 0;		/* was IFF_POINTOPOINT */
| in if_sl.c and rebuilding your kernel.
| 
| Then specify the remote network (subnet) number as the destination in the
| slattach command.

SLIP links are host routes, they do not have a subnet or network
associated with them.  In 4.3 BSD and it's derivatives pointopoint
interfaces should be refered to by their destination address, and their
subnet masks should be ignored.  The local address is not necessarily
unique, multiple pointopoint interfaces can share the same local interface
address with each other and up to one non-pointopoint (Ethernet)
interface.

Jeff