From owner-freebsd-net@FreeBSD.ORG Fri Jun 15 16:45:17 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 530D716A46C for ; Fri, 15 Jun 2007 16:45:17 +0000 (UTC) (envelope-from fox@verio.net) Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41]) by mx1.freebsd.org (Postfix) with ESMTP id 089E513C468 for ; Fri, 15 Jun 2007 16:45:17 +0000 (UTC) (envelope-from fox@verio.net) Received: from [129.250.36.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout1.email.verio.net with esmtp id 1HzEeJ-0003f3-Ls for freebsd-net@freebsd.org; Fri, 15 Jun 2007 16:27:47 +0000 Received: from [129.250.40.241] (helo=limbo.int.dllstx01.us.it.verio.net) by dfw-mmp3.email.verio.net with esmtp id 1HzEeJ-0003qd-H5 for freebsd-net@freebsd.org; Fri, 15 Jun 2007 16:27:47 +0000 Received: by limbo.int.dllstx01.us.it.verio.net (Postfix, from userid 1000) id B7C1C8E296; Fri, 15 Jun 2007 11:27:38 -0500 (CDT) Date: Fri, 15 Jun 2007 11:27:38 -0500 From: David DeSimone To: freebsd-net@freebsd.org Message-ID: <20070615162738.GA21747@verio.net> Mail-Followup-To: freebsd-net@freebsd.org References: <20070615104329.GF1173@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20070615104329.GF1173@turion.vk2pj.dyndns.org> Precedence: bulk User-Agent: Mutt/1.5.9i Subject: Re: VLANs and routing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2007 16:45:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Jeremy wrote: > > > But the (somewhat weird) requirements are that the vlan interface on > > machine1 shouldn't have assigned IP address, but the second one > > should. > [...] > > Is this kind of setup even supported? > > I don't see how it could be if machine1 is an IP endpoint: In order > to transmit a packet, it needs to put a source IP address into the > packet - which virtually always comes from the interface. When originating a packet, that is the case. But a forwarded packet already has a source address, which can be left unchanged. As long as routing is working (ARP is not needed, destination is clear, etc), the intermediate interface need not have an IP. - -- David DeSimone == Network Admin == fox@verio.net "It took me fifteen years to discover that I had no talent for writing, but I couldn't give it up because by that time I was too famous. -- Robert Benchley -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGcr36FSrKRjX5eCoRAnnwAJ4l/TIJPiMsNULHhAoJi6q12Y/vygCggBEe k47dQu/ZHnKNEPTaE9aW4lQ= =pg4w -----END PGP SIGNATURE-----