From owner-freebsd-net@FreeBSD.ORG Tue May 16 15:08:26 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 0500916A5D9 for ; Tue, 16 May 2006 15:08:26 +0000 (UTC) (envelope-from lists@yazzy.org) Received: from mx1.yazzy.org (mx1.yazzy.org [84.247.145.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A5B843D77 for ; Tue, 16 May 2006 15:08:19 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.witelcom.com ([84.247.144.144] helo=marcin) by mx1.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1Fg19N-0001r0-OT; Tue, 16 May 2006 17:07:54 +0200 Date: Tue, 16 May 2006 17:08:17 +0200 From: Marcin Jessa To: "OxY" Message-Id: <20060516170817.8585ea6c.lists@yazzy.org> In-Reply-To: <001001c678f6$f17b37b0$0201a8c0@oxy> References: <000c01c67873$dc8a9680$0201a8c0@oxy> <1A527B5C-C505-46A7-BA90-C5329C667FE1@mac.com> <000601c678f0$22472590$0201a8c0@oxy> <20060516163104.4d33e2c1.lists@yazzy.org> <001001c678f6$f17b37b0$0201a8c0@oxy> Organization: YazzY.org X-Mailer: Sylpheed version 2.2.0 (GTK+ 2.8.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) Cc: freebsd-net@freebsd.org Subject: Re: changing default route X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 15:08:27 -0000 On Tue, 16 May 2006 16:42:23 +0200 "OxY" wrote: > but bridging needs ipfw (or pf) and with heavy traffic > it needs lots of cpu. No, bridging does not need any firewalling. Run something like: ifconfig bridge0 create ifconfig bridge0 addm em0 addm em1 ifconfig bridge0 inet 12.23.34.45 netmask 255.255.255.0 Or put to rc.conf: cloned_interfaces="bridge0" ifconfig_bridge0="inet 12.23.34.45 netmask 255.255.255.0 addm em0 addm em1 up" And please stop top posting. Marcin. > ----- Original Message ----- > From: "Marcin Jessa" > To: "OxY" > Cc: > Sent: Tuesday, May 16, 2006 4:31 PM > Subject: Re: changing default route > > > > On Tue, 16 May 2006 15:53:38 +0200 > > "OxY" wrote: > > > >> any other solution? > >> can i solve it with static routing? > > > > Create a bridge interface, assign both the nics as it's members and > > assign the IP to it. > > > > Marcin. > > > >> ----- Original Message ----- > >> From: "Charles Swiger" > >> To: "OxY" > >> Cc: > >> Sent: Tuesday, May 16, 2006 1:10 AM > >> Subject: Re: changing default route > >> > >> > >> > On May 15, 2006, at 7:04 PM, OxY wrote: > >> >> have two interfaces with the same ip, em0 connected to another > >> >> server with crosslink, em1 is the public, can be reached from > >> >> the internet connected to a switch. > >> > > >> > Don't do that. Use bridging instead, if appropriate. > >> > > >> > -- > >> > -Chuck > >> > > >> _______________________________________________ > >> freebsd-net@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> To unsubscribe, send any mail to > >> "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to > > "freebsd-net-unsubscribe@freebsd.org"