From owner-freebsd-hackers Mon Feb 24 02:42:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA13056 for hackers-outgoing; Mon, 24 Feb 1997 02:42:48 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA13050 for ; Mon, 24 Feb 1997 02:42:43 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id VAA02383; Mon, 24 Feb 1997 21:47:02 +1100 (EST) Date: Mon, 24 Feb 1997 21:47:00 +1100 (EST) From: "Daniel O'Callaghan" To: Alexis Yushin cc: freebsd-hackers@freebsd.org Subject: Re: "black" interfaces list In-Reply-To: <199702240956.MAA12893@dawn.ww.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Feb 1997, Alexis Yushin wrote: > Greetings, > > Imagine we have FreeBSD based ip router. There is a number > of interfaces with different addresses, from different networks with > different routing policy. (The boldest example is p2p interface with > reserved addresses assigned for its ends) Why are you using reserved IP addresses for the ends? PPP interfaces can use an ethernet interface IP address quite happily, unless you are talking to a box which does not support this, but even NT does (although NT can't use the same IP *subnet* on ethernet and PPP.) Alternatively, use very small subnets (255.255.255.252 netmask) and use real IP addresses. As a last resort you can re-ifconfig a PPP interface with a 'real' IP address after it has been brought up. Danny