From owner-freebsd-net@FreeBSD.ORG Wed Feb 16 05:48:31 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0621F16A4CE for ; Wed, 16 Feb 2005 05:48:31 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89D243D39 for ; Wed, 16 Feb 2005 05:48:30 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id 775E621D9 for ; Tue, 15 Feb 2005 21:48:30 -0800 (PST) Received: from mailhost.schluting.com ([127.0.0.1]) by localhost (schluting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93832-02 for ; Tue, 15 Feb 2005 21:48:26 -0800 (PST) Received: from [10.1.0.69] (c-24-20-163-50.client.comcast.net [24.20.163.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id 03FD821E1 for ; Tue, 15 Feb 2005 21:48:25 -0800 (PST) Message-ID: <4212DEA9.9010305@schluting.com> Date: Tue, 15 Feb 2005 21:48:25 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@FreeBSD.org References: <91621437.20050215235900@mail.ru> In-Reply-To: <91621437.20050215235900@mail.ru> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com Subject: Re: puzzled network scheme X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Feb 2005 05:48:31 -0000 hydros wrote: > The general question is how to combine the real IP addresses > and the private on the same physical interface. Well, if you have a switch capable of vlans (and 802.1q trunks) you can just run a trunk to the firewall, and have many interfaces. My setup has one real IP, and 5 internal IPs, each associated with a different vlan. In your diagram, you can do it.. but it won't be pretty. i.e. just assign an alias (secondary IP) to the internal interface. Of course, both ranges are in the same broadcast domain.. -Charlie