From owner-freebsd-hackers  Mon Apr 24 00:24:19 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id AAA24696
          for hackers-outgoing; Mon, 24 Apr 1995 00:24:19 -0700
Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA24673
          for <hackers@freebsd.org>; Mon, 24 Apr 1995 00:23:55 -0700
Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP
	(5.67b+/DEC-Ultrix/4.3) id AA04244; Mon, 24 Apr 1995 09:23:42 +0200
Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP
	id JAA13228 for hackers@freebsd.org; Mon, 24 Apr 1995 09:23:35 +0200
Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id JAA03585 for hackers@freebsd.org; Mon, 24 Apr 1995 09:14:39 +0200
From: J Wunsch <j@jette.heep.sax.de>
Message-Id: <199504240714.JAA03585@jette.heep.sax.de>
Subject: Re: Re(2): IP problem with 950412-SNAP (and earlier -SNAPs)
To: hackers@FreeBSD.org
Date: Mon, 24 Apr 1995 09:14:36 +0200 (MET DST)
Reply-To: hackers@FreeBSD.org
In-Reply-To: <199504240354.WAA20416@bonkers.taronga.com> from "Peter da Silva" at Apr 23, 95 10:54:57 pm
Reply-To: joerg_wunsch@uriah.heep.sax.de
X-Phone: +49-351-2012 669
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 951       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

[2 p-p-p interface with identical addresses]

> >   No it doesn't.  I've run a SLIP interface and an ethernet interface on 
> > a FreeBSD machine both having the same address.  I know that it is 
> > opinion of some that this shouldn't work, but .....
> 
> Well, I think it kinda violates TCP/IP requirements, yes. I guess it's
> workable, but then you lose the ability to route to each address.
> 
Use the remote address as routing distinction.  e.g.:

	192.168.1.1  <---- SLIP ---->  111.222.333.444 gate to world

	192.168.1.1  <-------------->  192.168.1.* local ether

route add default 111.222.333.444

will do the trick: all packets to 192.168.1.* will pass thru the ether
interface, packets for the wide world will be sent out of the SLIP i/f.
The host route to 111.222.333.444 is implicit in BSD as soon as the
interface is up (it is _not_ implicit in Linux, as i had to find now :).
You only have to deal with network routes yourself.

Jörg