From owner-freebsd-isp@FreeBSD.ORG Mon Sep 12 16:48:08 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5974716A423 for ; Mon, 12 Sep 2005 16:48:08 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED8C943D46 for ; Mon, 12 Sep 2005 16:48:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout09/MantshX 4.0) with ESMTP id j8CGm7WS011012; Mon, 12 Sep 2005 09:48:07 -0700 (PDT) Received: from [10.1.1.209] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id j8CGm5Fk008082; Mon, 12 Sep 2005 09:48:06 -0700 (PDT) In-Reply-To: <4325A383.2030404@wm-access.no> References: <4322FDC4.8010609@mac.com> <18f601940509110230242e8bfc@mail.gmail.com> <43243677.6020707@mac.com> <43254F76.4000505@wm-access.no> <432579F1.4010807@mac.com> <4325A383.2030404@wm-access.no> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <8A38568B-D5B4-4EE7-AFB5-FF6C0D1285C6@mac.com> Content-Transfer-Encoding: quoted-printable From: Charles Swiger Date: Mon, 12 Sep 2005 12:47:52 -0400 To: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= X-Mailer: Apple Mail (2.734) Cc: freebsd-isp@freebsd.org, aaron.glenn@gmail.com Subject: Re: VLAN interfaces on FreeBSD; performance issues X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2005 16:48:08 -0000 On Sep 12, 2005, at 11:49 AM, Sten Daniel S=F8rsdal wrote: >> The essence of multihoming is having two (or more) distinct NICs. > > so if i had two vlan's with an ip on both. wouldnt this qualify it as > multihoming? would i somehow no longer need to configure the =20 > computer as > though it was a multihomed? I don't fully understand the question you are asking. If you have =20 one physical connection (one NIC, one Cat5 cable), you can only =20 connect to a single collision domain, even if you use VLANs (or set =20 up IP aliases on different subnets, etc). --=20 -Chuck=