From dillon@backplane.com  Wed Dec 31 15:12:06 1997
Received: from apollo.backplane.com (apollo.backplane.com [207.33.240.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03899
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 31 Dec 1997 15:12:05 -0800 (PST)
          (envelope-from dillon@backplane.com)
Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id PAA02144; Wed, 31 Dec 1997 15:11:57 -0800 (PST)
Message-Id: <199712312311.PAA02144@apollo.backplane.com>
Date: Wed, 31 Dec 1997 15:11:57 -0800 (PST)
From: Matthew Dillon <dillon@backplane.com>
Reply-To: dillon@backplane.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: slXX slip interfaces always point to point
X-Send-Pr-Version: 3.2

>Number:         5404
>Category:       kern
>Synopsis:       slXX slip interfaces always point to point
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 31 15:20:01 PST 1997
>Closed-Date:    Tue Apr 14 11:59:59 PDT 1998
>Last-Modified:  Tue Apr 14 12:00:16 PDT 1998
>Originator:     Matthew Dillon
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

	FreeBSD-current / PPro200

>Description:

	I often want to use SLIP interfaces to connect into a remote
	network.  The easiest way to do this is to treat the SLIP interface
	as a network interface rather then a point to point interface.  I've
	never been able to route networks over point-to-point slip interfaces
	reliability... it really confuses the machine.  I find myself having 
	to hack the FreeBSD kernel to remove the POINTTOPOINT flag and to add 
	the BROADCAST flag for slXX to make this work.

>How-To-Repeat:

	

>Fix:
	
	What we need is the ability to ifconfig a slip (or other interface)
	either as point-to-point or as a normal network.  At the moment, there
	is no way (that I can see) to turn off the POINTTOPOINT flag and 
	turn on the BROADCAST flag for a slip interface short of hacking the
	kernel.  The default, of course, should still be point-to-point.


>Release-Note:
>Audit-Trail:

From: John-Mark Gurney <gurney_j@efn.org>
To: dillon@backplane.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/5404: slXX slip interfaces always point to point
Date: Wed, 31 Dec 1997 16:20:32 +875200

 Matthew Dillon scribbled this message on Dec 31:
 > 	I often want to use SLIP interfaces to connect into a remote
 > 	network.  The easiest way to do this is to treat the SLIP interface
 > 	as a network interface rather then a point to point interface.  I've
 > 	never been able to route networks over point-to-point slip interfaces
 > 	reliability... it really confuses the machine.  I find myself having 
 > 	to hack the FreeBSD kernel to remove the POINTTOPOINT flag and to add 
 > 	the BROADCAST flag for slXX to make this work.
 
 why doesn't simply giving the interface a remote address on the network,
 and adding a network route to that address work?
 ifconfig sl0 192.168.0.1 192.168.3.1
 route add -net 192.168.3.0 192.168.3.1
 
 I have a couple networks that work like this, but they use ppp instead
 of slip...
 
 > >Fix:
 > 	
 > 	What we need is the ability to ifconfig a slip (or other interface)
 > 	either as point-to-point or as a normal network.  At the moment, there
 > 	is no way (that I can see) to turn off the POINTTOPOINT flag and 
 > 	turn on the BROADCAST flag for a slip interface short of hacking the
 > 	kernel.  The default, of course, should still be point-to-point.
 
 -- 
   John-Mark Gurney                          Modem/FAX: +1 541 683 6954
   Cu Networking					  P.O. Box 5693, 97405
 
   Live in Peace, destroy Micro$oft, support free software, run FreeBSD

From: Matthew Dillon <dillon@backplane.com>
To: John-Mark Gurney <gurney_j@efn.org>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/5404: slXX slip interfaces always point to point
Date: Wed, 31 Dec 1997 16:28:29 -0800 (PST)

 :why doesn't simply giving the interface a remote address on the network,
 :and adding a network route to that address work?
 :ifconfig sl0 192.168.0.1 192.168.3.1
 :route add -net 192.168.3.0 192.168.3.1
 :
 :I have a couple networks that work like this, but they use ppp instead
 :of slip...
 
     It doesn't seem to work over slNN and, more importantly, broadcast
     (192.168.3.255) reception doesn't work either.  The slip interface
     is actually tied *into* the network directly.
 
 					-Matt
 
 :> >Fix:
 :> 	
 :> 	What we need is the ability to ifconfig a slip (or other interface)
 :> 	either as point-to-point or as a normal network.  At the moment, there
 :> 	is no way (that I can see) to turn off the POINTTOPOINT flag and 
 :> 	turn on the BROADCAST flag for a slip interface short of hacking the
 :> 	kernel.  The default, of course, should still be point-to-point.
 :
 :-- 
 :  John-Mark Gurney                          Modem/FAX: +1 541 683 6954
 :  Cu Networking					  P.O. Box 5693, 97405
 :
 :  Live in Peace, destroy Micro$oft, support free software, run FreeBSD
 :
 
     Matthew Dillon   Engineering, BEST Internet Communications, Inc.
 		     <dillon@apollo.backplane.com>
     [always include a portion of the original email in any response!]

From: John-Mark Gurney <gurney_j@efn.org>
To: Matthew Dillon <dillon@backplane.com>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/5404: slXX slip interfaces always point to point
Date: Wed, 31 Dec 1997 17:23:58 +875200

 Matthew Dillon scribbled this message on Dec 31:
 > 
 > :why doesn't simply giving the interface a remote address on the network,
 > :and adding a network route to that address work?
 > :ifconfig sl0 192.168.0.1 192.168.3.1
 > :route add -net 192.168.3.0 192.168.3.1
 > :
 > :I have a couple networks that work like this, but they use ppp instead
 > :of slip...
 > 
 >     It doesn't seem to work over slNN and, more importantly, broadcast
 >     (192.168.3.255) reception doesn't work either.  The slip interface
 >     is actually tied *into* the network directly.
 
 hmm... what do you want to do exactly... something like:
 
 	+-------------+       +-------------+
 	|  machine a  |-------|  machine b  |---- rest of 192.168.3.x
 	| 192.168.0.1 |       | 192.168.3.1 |
 	+-------------+       +-------------+
 
 or are you wanting to do something like:
 
 	+-------------+       +-------------+
 	|  machine a  |-------|  machine b  |---- rest of 192.168.3.x
 	| 192.168.3.2 |       | 192.168.3.1 |
 	+-------------+       +-------------+
 
 and trying to get machine a on the same network as machine b?
 
 if your going for the second one, you need proxyarp on machine b...
 I've actually done something similar to this before...  actually my
 terminal server is setup like that... the ethernet is 192.168.0.x.. and
 the ip's for the dialin's are 192.168.40-60 or so...
 
 > :> 	What we need is the ability to ifconfig a slip (or other interface)
 > :> 	either as point-to-point or as a normal network.  At the moment, there
 > :> 	is no way (that I can see) to turn off the POINTTOPOINT flag and 
 > :> 	turn on the BROADCAST flag for a slip interface short of hacking the
 > :> 	kernel.  The default, of course, should still be point-to-point.
 
 -- 
   John-Mark Gurney                          Modem/FAX: +1 541 683 6954
   Cu Networking					  P.O. Box 5693, 97405
 
   Live in Peace, destroy Micro$oft, support free software, run FreeBSD

From: Matthew Dillon <dillon@backplane.com>
To: John-Mark Gurney <gurney_j@efn.org>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/5404: slXX slip interfaces always point to point
Date: Thu, 1 Jan 1998 11:24:46 -0800 (PST)

 :hmm... what do you want to do exactly... something like:
 :
 :	+-------------+       +-------------+
 :	|  machine a  |-------|  machine b  |---- rest of 192.168.3.x
 :	| 192.168.3.2 |       | 192.168.3.1 |
 :	+-------------+       +-------------+
 
     Yes, but machine B is actually a transparent gateway.  From machine
     a's point of view, machine b is just a node on a larger network and
     NOT the gateway.
 
 :if your going for the second one, you need proxyarp on machine b...
 :I've actually done something similar to this before...  actually my
 :terminal server is setup like that... the ethernet is 192.168.0.x.. and
 :the ip's for the dialin's are 192.168.40-60 or so...
 
     You don't really need proxy arp.  In this case, the transparent gateway
     handles all of that.    It's like an ethernet without the MAC layer.
     In fact, the machine B -> rest of network is a radio network, with both
     machine a & machine b appearing as nodes on the network.  Amoung other
     things, this allows machine A to receive and transmit broadcast packets.
 
 						-Matt
 
     Matthew Dillon   Engineering, BEST Internet Communications, Inc.
 		     <dillon@apollo.backplane.com>
     [always include a portion of the original email in any response!]
 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Tue Apr 14 11:59:59 PDT 1998 
State-Changed-Why:  
timed out 
>Unformatted:
